超出 -900 的错误代码

-903 Licensed GBase 8s SQL server not accessible.

This statement refers to another host computer system, and that system is active and accessible. However, the sqlexecd network daemon has not been started on it, so no database services can be gotten from it.

Contact the DBA of the other system. Check that the GBase 8s STAR or GBase 8s NET software is correctly installed.

该语句涉及另一台主机系统，并且该系统处于活动状态且可访问。但是，sqlexecd 网络守护进程尚未启动，因此无法从中获取数据库服务。联系该系统的 DBA。检查 GBase 8s STAR 或 GBase 8s NET 软件是否安装正确。

-904 Authorization file not on licensed GBase 8s SQL server.

This message indicates that the installation of the GBase 8s networking software was not completed correctly. Review the installation steps on the workstation and on the network server to make sure that it was completed without error.

此消息表明 GBase 联网软件的安装未正确完成。查看工作站和网络服务器上的安装步骤，确保完成没有错误。

-905 Cannot locate sqlexec service /tcp service in /etc/services.

The GBase 8s STAR or GBase 8s NET software has not been properly installed on this system. In particular, entries in the system-configuration file /etc/services (UNIX) or \etc\services (DOS)have not been made. Contact the person who installs your GBase 8s software.

GBase 8s STAR 或 GBase 8s NET 软件未在此系统上正确安装。特别是系统配置文件/etc/services（UNIX）或 \etc\services（DOS）中的条目尚未建立。请联系安装GBase 8s 软件的人员。

-906 Cannot locate remote system (check DBPATH).

NET is searching for the database that is requested in the current statement. It is using the entries in the DBPATH environment variable and is trying one that, by use of //sitename, specifies a directory on another computer system. That system cannot be accessed.

.NET 正在搜索当前语句中请求的数据库。它正在使用 DBPATH 环境变量中的条目，并尝试使用 //sitename 指定另一台计算机系统上的目录。该系统无法访问。

Review the setting of the DBPATH environment variable. Check that any other systems it specifies have STAR or NET installed and active.

查看 DBPATH 环境变量的设置。检查它指定的任何其他系统是否已安装并激活 STAR 或 .NET。

-907 Cannot create socket on current database server.

GBase STAR or .NET is trying to access another computer system but is unable to create a connection. Contact your system administrator, and ask for a check that TCP/IP is correctly installed and functioning.

GBase STAR 或 .NET 正试图访问另一台计算机系统，但无法创建连接。请联系您的系统管理员，并要求检查 TCP/IP 是否已正确安装并正常工作。

-908 Attempt to connect to database server (servername) failed.

The program or application is trying to access another database server but has failed. Note the server name in the current statement.

程序或应用程序试图访问另一台数据库服务器但失败。请注意当前语句中的服务器名称。

The desired database server is unavailable, or the network is down or is congested. Ask your DBA and system administrator to verify that the server and network are operational. If the network is congested, use the environment variables GBase 8sCONTIME and GBase 8sCONRETRY to tune connection timing. For information on setting these environment variables,see the GBase 8s Guide to SQL: Reference.

所需的数据库服务器不可用，或者网络关闭或拥塞。请 DBA 和系统管理员确认服务器和网络是否可用。如果网络拥塞，请使用环境变量 GBase 8s CONTIME 和 GBase 8s CONRETRY 调整连接时间。有关设置这些环境变量的信息，请参阅“GBase 8s SQL 指南：参考”。

-909 Invalid database name format.

This statement seems to refer to a database from another database server, but the database name, site name, server name, or punctuation is incorrect. Review the statement, and check that all identifiers start with a letter and contain only letters, digits, and underscores,and that the reference is in the form dbname@sitename or //sitename/dbname or dbname@servername or //servername/dbname . If you are using OnLine for NetWare,check that you provided the remote database name in one of the forms that is explained in the product manual.

此语句似乎是指来自另一个数据库服务器的数据库，但数据库名称、站点名称、服务器名称或标点符号不正确。请查看语句，检查所有标识符是否以字母开头，并且只包含字母、数字和下划线，并且引用格式为 dbname@sitename 或 //sitename/dbname 或 dbname@servername 或//servername/dbname。如果您正在使用 OnLine for NetWare，请检查是否以产品手册中介绍的某种形式提供了远程数据库名称。

-910 Cannot create an GBase 8s Dynamic Server database from an GBase 8s SE client.

This CREATE DATABASE statement cannot be carried out because the database server on your workstation and the one on the other computer system are different products: one is GBase 8s SE and the other is another GBase 8s database server. You can manipulate databases in this configuration, but you cannot create one.

由于工作站上的数据库服务器和其他计算机系统上的数据库服务器是不同的产品，因此无法执行此 CREATE DATABASE 语句。它们一个是 GBase 8s SE，一个是另一个 GBase 8s数据库。您可在此配置中操作数据库，但不能创建。

To create a database, either start the same product in both locations,or run this statement locally on the other computer system.

要创建数据库，可以在这两个位置启动同一产品，也可以在其他计算机系统上本地运行此语句。

-911 System error - Cannot read from pipe.

This internal error reflects a failure in communication between your application and the GBase 8s STAR or .NET software. Look for operating-system error messages that might give more information.

Restart the application. If the problem recurs, note all circumstances and contact GBase Technical Support.

此内部错误反映了应用程序与 GBase 8s STAR 或 .NET 软件之间的通信失败。查找可能提供更多信息的操作系统错误消息。重新启动应用程序。如果问题再次出现，请记下所有情况并联系 GBase 技术支持。

-912 Network error - Could not write to database server.

A network failure occurred. Look for operating-system error messages that might give more information. Restart the application. If the problem recurs, contact your system administrator, and ask for network diagnostics to be run.

发生网络故障。查找可能提供更多信息的操作系统错误消息。重新启动应用程序。如果问题再次出现，请联系您的系统管理员，要求运行网络诊断程序。

-913 Network error - Could not read from database server.

-914 System error - Cannot write to pipe.

This internal error reflects a failure in communication between your application and the GBase 8s STAR or .NET software. Look for operating-system error messages that might give more information.

Restart the application. If the problem recurs, note all circumstances and contact Technical Support .

此内部错误反映了应用程序与 GBase 8s STAR 或 .NET 软件之间的通信失败。查找可能提供更多信息的操作系统错误消息。重新启动应用程序。如果问题再次出现，请记下所有情况，并联系技术支持。

-915 Cannot create an GBase 8s SE database from an GBase 8s Dynamic Server client.

This CREATE DATABASE statement cannot be carried out because the database server on your workstation and the one in the other computer system are different products: one is GBase 8s SE and the other is another GBase 8s database server. You can manipulate databases in this configuration, but you cannot create one.

此 CREATE DATABASE 语句无法执行，因为工作站上的数据库服务器和其他计算机系统上的数据库服务器是不同的产品：一个是 GBase 8s SE，一个是另一个 GBase 8s 数据库服务器。您可以在此配置中操作数据库，但不能创建。

To create a database, either start the same product in both locations,or run this statement locally on the other computer system.

要创建数据库，可以在这两个位置启动同一产品，也可以在其他计算机系统上本地运行此语句。

-916 NFS mount table error.

The database server that you tried to access or a path that was specified in your DBPATH environment variable is located on an NFS-mounted file system. However, the database server or client application encountered an error accessing the NFS-mounted table file/etc/mtab (or, on some operating systems, /etc/mnttab). This condition probably occurred because your account does not have read permission for the file. Contact your system administrator, and have the file made readable to public.

您试图访问的数据库服务器或 DBPATH 环境变量中指定的路径位于 NFS 挂载的文件系统上。但是，数据库服务器或客户端应用程序在访问 NFS 挂载的表文件 /etc/mtab（或者 /etc/mnttab，在某些操作系统上）时遇到错误。这种情况可能是因为您的账户没有文件的读取权限。请联系您的系统管理员，并将该文件设置为公共权限。

-917 Must close current database before using a new database.

This statement (DATABASE or CREATE DATABASE) requires you to open a different database. However, the current database is located on another computer system, so you must explicitly close it with the CLOSE DATABASE statement. (When you work with databases located on the same computer as your application program, the database server will close the current database for you automatically.) If a program receives this error, review the program logic, and check that it executes a CLOSE DATABASE statement before a [CREATE] DATABASE statement. This solution will work in all situations, networked or local.

此语句（DATABASE 或 CREATE DATABASE）要求打开一个不同的数据库。但是，当前数据库位于另一台计算机系统上，因此您必须使用 CLOSE DATABASE 语句明确地关闭它。（当您使用与应用程序位于同一台计算机上的数据库时，数据库服务器将自动关闭当前数据库。）如果程序收到此错误，请查看程序逻辑并检查它是否在 [CREATE] DATABASE 语句之前执行CLOSE DATABASE 语句。此解决方案可以在所有情况下起作用，包括联网或本地。

-918 Unexpected data received from another database server.

This internal error reflects a failure in communication between your application and the GBase 8s STAR or .NET software at another site.

Restart your application. If the problem recurs, ask your system administrator to run network diagnostics. If the error recurs,note all circumstances and contact GBase Technical Support.

此内部错误反映了应用程序与另一个站点上的 GBase 8s STAR 或 .NET 软件之间的通信失败。重新调整你的应用程序,如果问题再次出现，请询问您的系统管理员运行网络诊断程序。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-919 System error. Wrong number of arguments to database server process.

This internal error reflects a failure in communication between your application, GBase 8s STAR or .NET software, and the database server on the other computer system. Check that all three of these software components are at compatible software levels. .Recompile and relink your application program if necessary. If the problem recurs, note all circumstances and contact GBase Technical Support.

此内部错误反映了您的应用程序，GBase 8s STAR 或 .NET 软件与另一台计算机系统上的数据库服务器之间的通信失败。检查所有这三个软件组件是否处于兼容软件级别。如有必要，请重新编译并重新链接您的应用程序。如果问题再次出现，请记下所有情况并联系 GBase 技术支持。

-921 System error. Illegal or wrong number of arguments to sqlexec server.

This internal error reflects a failure in communications between your application and the database server on the other computer system. Check that all software components are at compatible software levels. Recompile and relink your application program if necessary. If the problem recurs,note all circumstances and contact GBase Technical Support.

此内部错误反映了您的应用程序与其他计算机系统上的数据库服务器之间的通信失败。检查所有软件组件是否处于兼容软件级别。重新编译并重新链接您的应用程序（如有必要）。如果问题再次出现，请记下所有情况并联系 GBase 技术支持。

For a Windows system, check your Client Installation and Configuration Guide for information about using Setnet32 to set the environment variables that affect client-server communications.

对于 Windows 系统，请查看您的客户端安装和配置指南，以获取有关使用 Setnet32 设置影响客户端 - 服务器通信的环境变量的信息。

-922 Cannot get name of current working directory.

A problem exists with the current working directory on this system or on another computer system that your application is using. Possibly your account does not have read access to the directory, or possibly the file system that contains it is improperly mounted. Exit your application, and retry. If the problem persists, see your system administrator for assistance.

本系统上的当前工作目录存在问题或应用程序正在使用的其他计算机系统上存在问题。可能您的账户没有对该目录的读取权限，或者包含该文件的文件系统可能未正确安装。退出应用程序，然后重试。如果问题仍然存在，请查联系系统管理员寻求帮助。

-923 GBase is licensed to access the current database server only.

This version of the GBase 8s product is not licensed for network use.Locate the version of the software that is licensed for use with GBase 8s STAR or .NET,and reset your GBS_HOME environment variable and the SQLEXEC environment variable to point to it.

此版本的 GBase 8s 产品未获得网络使用许可。找到可以与 GBase 8s STAR 或 .NET 共同使用的软件版本，并重置 GBS_HOME 环境变量和 SQLEXEC 环境变量而指向它。

-924 GBase is not licensed to access the specified database server.

If you have installed an .NET station package only on your client computer,you cannot access locally resident databases. If the database that you are attempting to access is not locally resident, enter the command again and specify a site name with the database name, or set your DBPATH environment variable to indicate searches only in specific sites. If you want to use your GBase 8s product to access both local and remote databases, contact your GBase representative for details on purchasing the appropriate GBase 8s product.

如果您仅在客户端计算机上安装了.NET 工作站软件包，则无法访问本地驻留的数据库。如果您尝试访问不是本地驻留的数据库，请再次输入该命令，并使用数据库名称指定站点名称，或设置 DBPATH 环境变量以指示仅在特定站点中执行搜索。如果您想使用 GBase 8s 产品访问本地和远程数据库，请联系您的 GBase 代表以了解购买相应的 GBase 8s 产品的详细信息。

-925 The protocol type should be tcp.

The protocol type that is shown in the $GBS_DATA/conf/sqlhosts file(or in \GBASEDBT\etc\sqlhosts on OnLine for NetWare) should be tcp.

$GBS_DATA/conf/sqlhosts文件（或 OnLine for NetWare 中的 \GBASEDBT\etc\sqlhosts）中显示的协议类型应为 tcp。

-926 The database server is not licensed for distributed data access.

This statement refers to a database in a different database server (for example, by qualifying the name of a table with dbname@sitename:table).

However, this version is not licensed for such use. With this version,you can refer only to tables in databases that are all on the same database server.

此语句引用不同数据库服务器中的数据库（例如，通过使用 dbname@sitename：table 限定表的名称）。但是，此版本未获得此类使用许可。使用此版本，只能引用全部位于同一数据库服务器上的数据库中的表。

Contact your GBase representative about upgrading this database server to full GBase 8s STAR status. If you believe that you have GBase 8s STAR installed, check the contents of the GBS_HOME environment variable. If you are using OnLine for NetWare, you cannot access tables or databases on remote systems unless you have.NET PC.

请联系您的 GBase 代表，将此数据库服务器升级到完整的 GBase 8s STAR 状态。如果您确信已安装 GBase 8s STAR，请检查 GBS_HOME 环境变量的内容。如果您使用 OnLine for NetWare，则除非拥有 .NET PC，否则无法访问远程系统上的表或数据库。

-927 Exceeded limit on maximum number of servers you can reference.

This statement contains references to more sites than the database server can handle. Review the statement, and check that only necessary sites are named. If so, revise the operation to use fewer sites (for example,by selecting some data into a local, temporary table).

此语句包含的站点引用超出了数据库服务器能够处理的站点。请查看该语句，检查是否只命名了必要的网站。如果是这样，请修改操作以使用较少的站点（例如，通过将一些数据选择到本地临时表中）。

-928 The database server is not licensed for distributed data access.

This statement refers to a database on a different computer system (for example, by qualifying the name of a table with dbname@sitename:table).

However, the database server that is active at the indicated site is not licensed for such use. This situation indicates an error in the setup of the remote computer system: it was configured for network access, but the wrong database server was started. Contact the network administrator, and ask for a check of the environment variables when starting the sqlexecd daemon. If you are using GBase 8s OnLine for NetWare, you tried to access a table on an database server that is not licensed for remote access; you can access only other GBase 8s NET PC systems.

此语句引用不同计算机系统上的数据库（例如，通过使用 dbname@sitename:table 限定表的名称）。但是，指定站点上处于活动状态的数据库服务器未获得许可。这种情况表明远程计算机系统的设置出现错误：它已配置为进行网络访问，但启动了错误的数据库服务器。

请联系网络管理员，并在启动 sqlexecd 守护进程时要求检查环境变量。如果您使用 GBase 8s OnLine for NetWare，则尝试访问未获得远程访问许可的数据库服务器上的表；您只能访问其他 GBase 8s NET PC 系统。

-930 Cannot connect to database server servername.

The application is trying to access another computer system but failed.

Note the server name in the current statement. Ask your network administrator and DBA to check that the network is operational and that the particular database server is active.

应用程序试图访问另一台计算机系统但失败。请注意当前语句中的服务器名称。请您的网络管理员和 DBA 检查网络是否正常工作，以及特定数据库服务器是否处于活动状态。

-929 SQLI Protocol Error. Session terminated.

The database server received a SQLI protocol request that could not be interpreted. Such messages are treated as attacks on the server and the session issuing such a request is unilaterally terminated immediately.

If you think you received this message erroneously, record all the details (including the version of CSDK or I-Connect in use) and contact GBase Support.

数据库服务器收到无法解释的 SQLI 协议请求。这些消息被视为对服务器的攻击，发出此类请求的会话将立即被单方面终止。如果您认为错误地收到了此消息，请记录所有详细信息（包括正在使用的 CSDK 或 I-Connect 的版本）并联系 GBase 支持。

-931 Cannot locate servicename service/tcp service in /etc/services.

The service servicename is not listed in the network configuration file/etc/services (UNIX) or \etc\services (DOS). Check the $GBS_DATA/conf/sqlhosts file, and check that the service name for the desired server is correct.

If so, contact your network administrator to find out why the service is not known.

If you are using GBase 8s OnLine for NetWare, check the \etc\services file on the client for the required entries.

服务 servicename 未列在网络配置文件 /etc/services（UNIX）或 \etc\services（DOS）中。检查 $GBS_DATA/conf/sqlhosts 文件，并检查所需服务器的服务名称是否正确。如果是这样，请联系您的网络管理员，了解服务未知的原因。如果使用 GBase 8s OnLine for NetWare，请检查客户端上的 \etc\services 文件以获取所需的条目。

-932 Error on network connection, function system call failed.

This internal error reflects a failure in communication between your application and the network software (GBase 8s STAR, GBase 8s NET,GBase 8s NET for Windows, and so on) at another site. Restart your application. Look for operating-system messages that might give more information.

此内部错误反映了应用程序与另一个站点上的网络软件（GBase 8s STAR、GBase 8s NET、GBase 8s NET for Windows 等）之间的通信失败。重新启动应用程序。查找可能提供更多信息的操作系统消息。

If you are using GBase 8s NET for Windows, a Windows Sockets problem might exist; check your Windows Sockets 1.1 documentation for more information. Check the sqlerrm field of the sqlca structure for the particular Windows Sockets message.

如果您使用的是GBase 8s .NET for Windows，则可能存在 Windows Sockets 问题；检查您的 Windows Sockets 1.1 文档以获取更多信息。检查特定 Windows Sockets 消息的 sqlca 结构的 sqlerrm 字段。

In the ASCL context, this error might also indicate problems in your GBase 8s.ini file. Verify that the SERVICE, HOST, and PASSWD entries are correct.

在 ASCL 上下文中，此错误也可能表示 GBase 8s.ini 文件中存在问题。请验证 SERVICE、HOST 和 PASSWD 条目是否正确。

If the problem recurs, ask your network administrator to run network diagnostics. If the error recurs, note all circumstances and contact GBase Technical Support.

如果问题再次出现，请让您的网络管理员运行网络诊断程序。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-933 Unknown network type specified in DBNETTYPE.

The DBNETTYPE environment variable is used on certain machines to distinguish which network protocol to use when two protocols are available. The value that is currently set in it is not supported.

Display the variable, and check that it is set correctly. If you are using GBase 8s OnLine for NetWare, set DBNETTYPE to starlan, tcp/ip,or some other supported network.

在某些机器上使用 DBNETTYPE 环境变量来区分使用两种协议时要使用的网络协议。目前在其中设置的值不受支持。显示该变量，并检查它是否设置正确。如果您使用GBase 8s OnLine for NetWare，请将 DBNETTYPE 设置为 starlan、tcp/ip 或其他支持的网络。

-934 Connection to remote site no longer valid.

This statement uses data from another computer system, but the connection has been lost. Roll back the transaction, and try again after you reestablish the connection.

该语句使用来自其他计算机系统的数据，但连接已丢失。回滚事务，并在重新建立连接后重试。

-935 Cannot obtain IPX address for service name servicename.

You are trying to connect to a database server with the indicated service name via the IPX/SPX network protocol on a system with portable GBase 8s OnLine for NetWare. The client application, GBase 8s NET or GBase 8s STAR, is not able to determine the IPX address that is associated with the specified service name. Possibly the service name is misspelled in your sqlhosts file; the sqlexecd daemon or the database server is not running; or the portable GBase 8s OnLine for NetWare software is not operating properly. Verify the service name in your sqlhosts file. Ask your DBA or system administrator to verify that the sqlexecd daemon, the database server,and the portable GBase 8s OnLine for NetWare software are operational.

您正试图通过带有便携式 GBase 8s OnLine for NetWare 的系统上的 IPX/SPX 网络协议使用指定的服务名称连接到数据库服务器。客户端应用程序 GBase 8s NET 或 GBase 8s STAR 无法确定与指定的服务名称关联的 IPX 地址。可能是因为 sqlhosts 文件中的服务名称拼写错误；可能是 sqlexecd 守护进程或数据库服务器未运行；或 etWare 软件的 GBase 8s OnLine 无法正常运行。请验证 sqlhosts 文件中的服务名称。请您的 DBA 或系统管理员验证 sqlexecd 守护程序，数据库服务器和移植的 GBase 8s OnLine for NetWare 软件是否可用。

-936 Error on remote connection connection-name.

An attempted connection to a remote host failed. Check the name of the connection that is specified in your particular connection statement(CONNECT, DATABASE, and so on) to make sure that you correctly specified the name or path of the connection. Check for incorrect spelling. Check for the wrong connection name.

尝试连接到远程主机失败。检查在特定连接语句（CONNECT、DATABASE 等）中指定的连接的名称，以确保正确指定了连接的名称或路径。检查是否存在拼写错误。检查连接名称是否错误。

-937 User Defined Routine error.

mi_db_error_raise() has been called from within a user-defined routine and set a fatal error. For an explanation, look at the SQLSTATE that the user-defined routine set.

从用户定义的例程中调用 mi_db_error_raise() 并设置致命错误。有关说明，请查看用户定义的例程设置的 SQLSTATE。

-938 VALUES clause may not have expressions if a cursor is declared on an INSERT.

The INSERT statement to be associated with the INSERT cursor includes a VALUES clause that has one or more expressions.

与 INSERT 游标关联的 INSERT 语句包含具有一个或多个表达式的 VALUES 子句。

Change the application so that expressions are not used in the VALUES clause.

请更改应用程序，在 VALUES 子句中不要使用表达式。

-939 Too many messages to display; some are not shown.

This message appears if a single error in the server results in a large number of messages being returned. For example, if there is a nested set of calls in which a user-defined routine (UDR) executes an SQL statement that calls another UDR, and so on, when an error occurs, each UDR returns a message for that error corresponding to its own context. When the number of messages exceeds an internal limit, the remaining messages are replaced by this message. You do not need to take any special action.

如果服务器中的一个错误导致返回大量消息，则会显示此消息。例如，如果存在一组嵌套的调用，其中用户定义的例程（UDR）执行调用另一个 UDR 的 SQL 语句等等，则当发生错误时，每个 UDR 都会返回对应自身上下文的一条错误消息。当消息数量超过内部限制时，其余消息将被此消息替换。不需要采取任何特殊。

-940 The statement failed, becuase the WITH CHECK OPTION keywords are not supported in Union, Intersect, or Minus views.

You tried to define a union/intersect/minus view with a check options.

Redefine the union/intersect/minus view without the check options clause.

您尝试定义带有检查选项的 union/intersect/minus 视图。请重新定义没有检查选项子句的union/intersect/minus 视图。

-941 String processing error while evaluating function (function_name).

An error occurred during evaluation of the case conversion function on the input string.

This error could be due to an invalid character (single-or multi-byte) in the string.

You need to execute the query again after verifying that the characters in the input string are valid.

大小写转换函数的输入字符串发生错误。此错误可能是因为字符串中有无效字符（单字节或多字节）。验证输入字符串中的字符是否有效后，再次执行此查询。

-942 Transaction commit failed - transaction will be rolled back.

This error can occur at transaction-commit time if an error is raised when a DataBlade routine calls a UDR-registered end-of-transaction(MI_EVENT_END_XACT) callback. You have registered a callback for the MI_EVENT_END_XACT (or MI_Xact_State_Change) event in the context of a server routine. When the end-of-transaction (MI_EVENT_END_XACT) event occurred to commit the transaction, an error was raised.

如果在 DataBlade 例程调用 UDR 注册的事务结束（MI_EVENT_END_XACT）回调时发生错误，则可能会在事务提交时发生此错误。您已经在服务器例程的上下文中注册了 MI_EVENT_END_XACT（或 MI_Xact_State_Change）事件的回调。当发出事务结（MI_EVENT_END_XACT）事件提交事务时，会产生错误。

Within a DataBlade routine, you can use the mi_error_desc_next()function to obtain the next error, which should explain the cause of the failure. Currently, the end-of-transaction (MI_EVENT_END_XACT) event occurs only within the context of a DataBlade server routine. It does not occur within the context of a DataBlade client application.

在 DataBlade 例程中，可以使用 mi_error_desc_next() 函数来获取下一个错误，它解释失败的原因。目前，事务结束（MI_EVENT_END_XACT）事件仅发生在 DataBlade服务器例程的上下文中。它不会在 DataBlad e客户端应用程序的上下文中发生。

-943 Found a non-terminated comment ("/*" with no matching "*/").

DB-Access does not currently support comments without terminators. You might see this message when you run .sql scripts through DB-Access.

DB-Access 当前不支持没有终止符的注释。通过 DB-Access 运行 .sql 脚本时，您可能会看到此消息。

-944 Cannot use "first", "limit" or "skip" in this context.

This statement uses FIRST N , LIMIT N or SKIP M inside a subquery. This action is not supported.

此语句在子查询中使用 FIRST N、LIMIT N 或 SKIP M。不支持该操作。

Review the use of FIRST N and check that it is applied only to the outer main query SELECT clause.

查看 FIRST N 的用法并检查它是否只在外部主查询 SELECT 子句中应用。

-945 Invalid parameter given to dbinfo(version).

You entered a value for a version that this command does not support.

The arguments to dbinfo() are invalid or NULL. The first argument was the string constant version.

您对该命令不支持的版本输入了一个值。 dbinfo() 的参数无效或为 NULL。第一个参数是字符串常量版本。

Check that the second argument is also a quoted string constant that corresponds to one of the following values: 'major', 'minor', 'level','os', 'server-type', or 'full'.

检查第二个参数是否也是一个引用的字符串常量，它对应于以下值之一：'major'、'minor'、'level'、'os'、'server-type' 或 'full'。

-946 Source string for UPPER, LOWER, and INITCAP must be of string type.

The source string passed as input to a case conversion function must have a character data type.

作为大小写转换函数的源字符串，输入的字符串必须具有字符数据类型。

-947 Declaration of an SPL variable named 'null' conflicts with SQL NULL value.

Users may not define an SPL routine variable whose spelling is 'null'. This is an error because allowing such definition would restrict the global scope of the NULL constant.

用户不能定义拼写为 'null' 的SPL例程变量。这是一个错误，因为允许这样的定义会限制NULL 常量的全局范围。

-948 Cannot rename constraint index.

User tried to rename a system-generated constraint index.

用户尝试重命名系统生成的约束索引。

You do not need to take any action because you are not allowed to rename a system-generated constraint index.

不需要执行任何操作，因为不允许重命名系统生成的约束索引。

-949 Unable to alter fragmentation scheme when indexes disabled.

An attempt has been made to alter the fragmentation scheme on a table that has disabled indexes. This is not allowed. The action is aborted.

该操作试图改变已禁用索引的表上的分片模式。这是不允许的。该操作被中止。

-950 User username is not known on the database server.

This statement refers to a database on another computer system, but the other database server does not accept your account name. You must have a valid trusted login identity on any database server you access remotely.

See your database administrator about putting your login ID in 'sysuser:sysauth'on the remote server. This message appears on PAM enabled servers.

该语句引用另一台计算机系统上的数据库，但此数据库服务器不接受您的账户名称。您必须在远程访问的所有数据库服务器上拥有有效的信任登录标识。请咨询数据库管理员，将您的登录 ID 放到远程服务器上的 'sysuser：sysauth' 中。此消息出现在启用 PAM 的服务器上。

-951 User username is not known on the database server.

The database server that you tried to access does not accept either your user ID, the login name that is specified for the desired server host in your ~/.netrc file, or the user name that is specified in the USER clause of a CONNECT statement. If you are explicitly specifying your user name in the ~/.netrc file or in a CONNECT statement, check that the name is correct. If you do not have a valid user ID on the server computer, see your system administrator.

您尝试访问的数据库服务器不接受您的用户标识，在 ~/.netrc 文件中为所需的服务器主机指定的登录名，或者在 CONNECT 语句的 USER 子句中指定的用户名。如果在 ~/.netrc文件或 CONNECT 语句中明确指定用户名，请检查名称是否正确。如果服务器计算机上没有有效的用户标识，请联系系统管理员。

-952 User's password is not correct for the database server.

The password that is specified for the server computer in your ~/.netrc file or in the USER clause of a CONNECT statement is incorrect. The database server does not accept (or cannot find) your account password.

Check that your password is specified correctly, and try again.

~/.netrc 文件或 CONNECT 语句的 USER 子句中为服务器计算机指定的密码不正确。数据库服务器不接受（或无法找到）您的账户密码。检查您的密码是否正确，然后重试。

-952 User ()'s password is not correct for the database server.

Check that your password is specified correctly, and try again.

在 ~/.netrc 文件或 CONNECT 语句的 USER 子句中为服务器计算机指定的密码不正确。数据库服务器不接受（或找不到）您的账户密码。请检查您的密码是否已正确指定，然后重试。

-953 Network server could not exec sqlexec program.

The network server was unable to start the database server thread. The most common cause for this error is a failure to define the GBS_HOME environment variable, by root, at the time the database server process was started. Contact your network administrator, and ask that the database server process on the remote system be restarted with a valid path to the GBase 8s software.

网络服务器无法启动数据库服务器线程。导致此错误的最常见原因是未能在数据库服务器进程启动时以 root 身份定义 GBS_HOME 环境变量。请联系网络管理员，并使用有效的 GBase 8s 软件路径重启远程系统上的数据库服务器进程。

-954 Client is not known to remote host.

The computer on which your application is running is not known to the computer you are trying to access. Contact your network administrator,and ask that your computer be made known. The usual way of making a computer known is through the configuration file /etc/hosts.equiv on the other system. Refer to the GBase 8s NET/GBase 8s STAR Installation and Configuration Guide.

运行应用程序的计算机无法识别您尝试访问的计算机。请联网络管理员，要求让您的计算机可以识别。识别计算机的常用方法是通过设置另一个系统上的配置文件 /etc/hosts.equiv。请参阅“GBase 8s .NET/GBase 8s STAR 安装和配置指南”。

-955 Remote host could not receive data from client.

This internal error reflects a failure in communication between your application and the GBase 8s STAR or GBase 8s NET software at another site. Restart your application. Look for operating-system messages that might give more information. If the problem recurs, ask your network administrator to run network diagnostics. If the error recurs,note all circumstances and contact GBase Technical Support.

该内部错误反映了应用程序与另一个站点上的 GBase 8s STAR 或 GBase 8s NET 软件之间的通信失败。请重新启动应用程序。查找可能提供更多信息的操作系统消息。如果问题再次出现，请让网络管理员运行网络诊断程序。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-955 Database server could not receive data from client.

This internal error reflects a failure in communication between your client application and the database server software at another site.

Restart your application. Look for operating-system messages that might give more information. If the problem recurs, ask your DBA to run network diagnostics. If the error recurs, note all circumstances and contact GBase Technical Support.

该内部错误反映您的客户端应用程序无法与另一个站点上的数据库服务器软件进行通信。

请重新启动您的应用程序。查找可能提供更多信息的操作系统消息。如果问题再次出现，请让 DBA 运行网络诊断程序。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-956 Client client-name or user is not trusted by the database server.

The desired database server does not consider the client computer or your user ID trusted. Ask the system administrator to include the client computer as a trusted host and/or your user id as a trusted user in the /etc/hosts.equiv file on the server computer or in the .rhosts file in your home directory on the server computer. See the UNIX manual pages on HOSTS.EQUIV(5) for more information.

需要的数据库服务器不会考虑客户端计算机或您的用户 ID 的信任。请系统管理员将服务器计算机上的 /etc/hosts.equiv 文件或服务器计算机主目录中的 .rhosts 文件中的可信主机和/或您的用户标识作为可信用户。有关更多信息，请参阅 HOSTS.EQUIV(5) 中的 UNIX 手册页。

Alternatively, you can explicitly specify your user name and password in the USER clause of a CONNECT statement or in the .netrc file in your home directory on the client computer. See the GBase 8s Guide to SQL:Syntax for information on the CONNECT statement, and the UNIX manual pages regarding NETRC(5) for information on the .netrc file.

或者，可以 CONNECT 语句的 USER 子句中或客户端计算机的主目录上的 .netrc 文件中明确指定用户名和密码。有关 CONNECT 语句的信息，请参阅 “GBase 8s SQL指南：语法”。

有关 .netrc 文件上的信息，请参阅有关 NETRC（5）的 UNIX 手册页。

-957 Cannot create/access database on NFS mount.

Note the specifics of your system when this internal error occurred, and contact GBase Technical Support.

请注意发生该内部错误时系统的具体情况，并联系 GBase 技术支持。

-958 Temp table already exists in session.

This statement tries to create a table with the name that is shown, but a temporary table with that name already exists. Only one temporary table with a given name can exist in a session.

该语句尝试创建一个可以显示其名称的表，但具有该名称的临时表已存在。该名称的临时表在会话中只能出现一次。

Check the spelling of the name. If the name is spelled as you intended,check that a temporary table with the given name does not exist in the session.

检查名称的拼写。如果名称按照您的意图拼写，请检查会话中是否存在具有给定名称的临时表。

To review the names of temporary tables, query the systabnames table as follows:要检查临时表的名称，可以按照下列语句查询 systabnames 表：SELECT dbsname, tabname FROM sysmaster:systabnames WHERE tabname = If the name exists, review this name by querying the systables table in :如果名称存在，请检查中的 systables 表：SELECT tabname FROM :systables WHERE tabname = If the name does not exist in systables (" No rows found "), this table is a temporary table.

如果该名称在 systables 中不存在（“找不到行”），则该表是临时表。

-959 The current transaction has been rolled back due to an internal error.

A server thread associated with your session has been suspended, most likely because of a serious internal error. Evidence about the problem has been gathered and written to an Assertion Failure file,and your online log should contain more information. Contact GBase Technical Support and provide them with your Assertion Failure file.

已经暂停与会话相关联的服务器线程，很可能是因为严重的内部错误。有关该问题的证据已收集并写入断言失败文件，并且您的联机日志会包含更多的信息。联系 GBase 技术支持部门并为他们提供 Assertion Failure 文件。

Before suspending the session thread, the server attempted to roll back all work performed by the current transaction. Your connection to the server may also have been broken, depending on the type of thread that was suspended. At a minimum you will have to begin a new transaction.

在挂起会话线程之前，服务器试图回滚当前事务执行的所有工作。根据挂起的线程类型，您与服务器的连接可能也已中断。此时您将不得不开始新的事务。

-960 The connection failed because the user failed the security check set by the SECURITY_LOCALCONNECTION configuration parameter.

The ID of the local user running the client program is not the same ID of the user trying to access the database. The server checks the user IDs when the SECURITY_LOCALCONNECTION configuration parameter is set to a nonzero value.

运行客户端程序的本地用户的 ID 与尝试访问数据库的用户的 ID 不同。服务器在SECURITY_LOCALCONNECTION 配置参数设置为非零值时检查用户 ID。

See the GBase 8s Administrator's Reference manual for more information.

有关更多信息，请参阅 GBase 8s 管理员参考手册。

-971 Integrity violations detected.

The user has attempted to change the object mode of a disabled constraint or disabled unique index to the enabled or filtering mode,but the SET statement fails because the table contains data that violates the constraint or the unique-index requirement. If a violations table has been started for the table that contains the inconsistent data, this message is returned to the user. The message is returned whether or not the SET statement included the WITH ERROR option.

用户试图将禁用的约束或禁用的唯一索引的对象模式更改为启用或过滤模式，但 SET 语句失败，因为该表包含违反约束或唯一索引要求的数据。如果包含不一致数据的表已启动违例表，则将此消息返回给用户。无论 SET 语句是否包含 WITH ERROR 选项，都会返回消息。

Similarly, when an INSERT, DELETE, or UPDATE statement causes some records to be added to the violations table because the statement violates a filtering-mode object, this message is returned to the user if the following two conditions are true:同样，如果 INSERT、DELETE 或 UPDATE 语句导致某些记录添加到违例表中，因为该语句违反了筛选模式对象，如果满足以下两个条件，则会将此消息返回给用户：* The SET statement or CREATE statement that specified the filtering-object mode for the object included the WITH ERROR option.

指定对象的过滤对象模式的 SET语句或 CREATE 语句包含 WITH ERROR 选项。

* No other errors have been encountered during the execution of the INSERT, DELETE, or UPDATE statement.

在执行 INSERT、DELETE 或 UPDATE 语句期间没有遇到其他错误。

-972 Unable to alter table table-name.

The in-place alter table operation cannot be performed. See the accompanying ISAM error for more information.

无法执行定点更改表操作。有关更多信息，请参阅随附的 ISAM 错误。

-973 Cannot insert from the violations table to the target table.

The user issued a statement that attempts to insert rows from the violations table into the target table. For example, the user enters the following statement:用户发出了一条语句，它试图将来自违例表的行插入到目标表中。例如，用户输入以下语句：INSERT INTO mytable SELECT * FROM mytable_vio If the target table has some filtering-mode objects, this error is returned to the user. The user can recover in any of the following ways:如果目标表有一些过滤模式对象，则会将此错误返回给用户。用户可以通过以下任何方式进行恢复：* Set the object mode of the filtering objects to some other mode.

* 将过滤对象的对象模式设置为其他模式。

* Stop the violations table.

* 停止违例表。

* Insert rows from the violations table into a temporary table,and then insert rows from the temporary table into the target table.

将违例表中的行插入临时表中，然后将临时表中的行插入目标表中。

-974 Cannot drop not null constraint on the serial column.

The user issued a statement to drop a NOT NULL constraint on a column that has a SERIAL or SERIAL8 or BIGSERIAL data type. Such constraints can be disabled, but they cannot be dropped before the column is dropped.

用户发布了语句，它删除 SERIAL 或 SERIAL8 或 BIGSERIAL 数据类型的列上的 NOT NULL约束。禁用这些约束，但是在删除列之前不能删除这些约束。

-975 Invalid object and object mode combination.

The user tried to create a new object in an object mode that does not apply to that object type, or the user set the object mode of an existing object to a mode that does not apply to that type of object.

For example, if the user tries to create a trigger in the filtering mode or set an existing trigger to the filtering mode, the user receives this error.

用户试图以不适用于该对象类型的对象模式创建新对象，或者用户将现有对象的对象模式设置为不适用于该类型对象的模式。例如，如果用户尝试在过滤模式下创建触发器或将现有触发器设置为过滤模式，则会收到此错误。

-976 Table must be fragmented by expression to grant fragment authority.

The user attempted to grant fragment-level privileges on an unfragmented table or on a table that is not fragmented by expression.

用户尝试对未分片表或未按表达式分片的表授予分片级权限。

-977 No permission on fragment (dbspace-name/partition-name).

The user does not have the required fragment-level privilege on the table fragment. This message is always followed by another message that identifies the privilege that the user lacks. If an INSERT statement fails, the second message is -271. If an UPDATE statement fails, the second message is -346. If a DELETE statement fails, the second message is -240.

用户没有对表分片的分片级特权。该消息后面总是跟随一个用户缺少的特权标识的消息。如果INSERT 语句失败，则第二条消息是 -271。如果 UPDATE 语句失败，则第二条消息是 -346。如果 DELETE 语句失败，则第二条消息是 -240。

-978 No insert permission on the violations/diagnostics tables.

The user issued an INSERT, DELETE, or UPDATE statement on a table with filtering-mode objects. The user receives this message because the user lacks the INSERT privilege on the violations or diagnostics tables that are associated with this table. The user must have the INSERT privilege on the violations and diagnostics tables before the database server can write rows into the violations and diagnostics tables for that user.

用户在具有过滤模式对象的表上发出 INSERT、DELETE 或 UPDATE 语句。用户收到此消息是因为用户缺少与此表关联的违例或诊断表的 INSERT 权限。在数据库服务器可以将行写入该用户的违例和诊断表之前，用户必须具有对违规和诊断表的 INSERT 特权。

Similarly, if the user issued a SET statement to change the object mode of a disabled constraint or a disabled unique index to the enabled or filtering mode, and if a violations table has been started for the target table, the user receives this message if the user lacks the INSERT privilege on the violations or diagnostics table associated with the target table.

同样，如果用户发出 SET 语句将禁用约束或禁用唯一索引的对象模式更改为启用或过滤模式，并且已经为目标表启动了违例表，则用户会收到此消息：用户缺少对与目标表关联的违例或诊断表的 INSERT 权限。

-979 The current transaction has been rolled back due to an internal error.

与会话相关联的服务器线程已被暂停，很可能是因为内部错误严重。有关该问题的证据已收集并写入断言失败文件，并且您的联机日志会包含更多信息。

Before suspending the session thread, the server attempted to roll back all work performed by the current transaction. Your connection to the server might also have been broken, depending on the type of thread that was suspended. At a minimum, you will have to begin a new transaction.

在挂起会话线程之前，服务器试图回滚当前事务执行的所有工作。根据挂起的线程类型，会终止您对服务器的连接。在此刻，您将不得不开始新的事务。

Contact GBase Technical Support and provide them with your Assertion Failure file.

联系 GBase 技术支持，并提供断言失败的文件。

-999 Not implemented yet.

This error means the functionality being exercised is not currently implemented. Check the documentation and release notes that describe this current restriction in this particular release for this product. If this condition is not described in the regular documentation or the release notes and recurs, note all circumstances and contact GBase Technical Support.

该错误意味着正在执行的性能目前尚未实施。查看描述当前限制的特定版本产品的文档和发行说明。如果在常规文档或发行说明中没有描述这种情况，但仍重复出现，请记下所有情况并联系 GBase 技术支持。

-1003 Invalid ACCEPTKEY set in the environment.

The key that the ACCEPTKEY environment variable specifies is not decipherable; either it does not start with F, or it has an invalid number. Specify a different key.

ACCEPTKEY 环境变量指定的密钥不可破译；该密钥要么没有以 F 开头，要么是无效的数字。请指定一个不同的密钥。

-1004 The selected ACCEPTKEY has been preassigned for ISQL.

The key that the ACCEPTKEY environment variable specifies is one that GBase 8s SQL always uses. Set a different value in the environment variable.

ACCEPTKEY 环境变量指定的密钥是 GBase 8s SQL 始终使用的密钥。请在环境变量中设置一个不同的值。

-1005 Your specified termcap file cannot be read.

The TERMCAP environment variable specifies a file that cannot be opened. Either it does not exist, or your account does not have operating-system permissions to read it. Check the environment variableand the file that it names.

TERMCAP 环境变量指定了一个无法打开的文件。要么该文件不存在，要么您的账户不具有读取它的操作系统权限。请检查环境变量和它命名的文件。

-1006 Error number.

The error code that is shown was returned, but the program could not display the message text for that number, probably because one of the.iem message files is missing from the directory that the GBS_HOME environment variable specifies. Look up the number in the finderr utility.

Also consult with the person who installed the GBase 8s software to find out why the message files are not available.

已返回了错误代码，但程序无法显示该编号的消息文本，可能是因为在 GBS_HOME 环境变量指定的目录中缺少 .iem 消息文件。使用 finderr 实用程序中查询该编号。也请咨询安装 GBase 8s 软件的人员，以了解消息文件不可用的原因。

-1007 Invalid value for the GBASEDBTTERM environment variable.

The only valid settings for the GBASEDBTTERM environment variables are termcap and terminfo. Setting the variable to termcap (or leaving it undefined) directs 4GL to use the TERMCAP facility for terminal control.

Setting it to terminfo causes 4GL to use the TERMINFO facility. Other settings, including variations of the words termcap and terminfo with capital letters in them, cause this error.

GBASEDBTTERM 环境变量唯一有效的设置是 termcap 和 terminfo。将变量设置为termcap（或将其保留为未定义）是指示 4GL 使用 TERMCAP 工具进行终端控制。将其设置为 terminfo 会导致 4GL 使用 TERMINFO 工具。其它设置也会导致此错误，例如 termcap 和 terminfo 中包含大写字符。

-1008 Termcap entry too long.

The contents of the TERMCAP environment variable, or of the termcap entry from the termcap database, are read into storage when the application is initializing. However, the memory buffer that is allocated to hold the termcap entry is 1,024 bytes, and the entry inuse is longer than that. Use a simpler termcap.

当应用程序初始化时，TERMCA P环境变量或 termcap 数据库中的 termcap 条目的内容被读入存储器。但是，分配给存放 termcap 条目的内存缓冲区为 1,024 字节，而正在使用的条目比此条目更长。请使用更简单的 termcap。

-1009 Bad termcap entry.

The contents of the TERMCAP environment variable, or of the termcap entry from the termcap database, are read into storage when the application is initializing. While the program was doing this, it found improper punctuation in the termcap entry. A colon separator did not appear where one was expected. Review the specified termcap, and choose a different one or correct the one that is in use.

当应用程序初始化时，TERMCAP 环境变量或 termcap 数据库中的 termcap 条目的内容被读入存储器。当程序这样做时，它在 termcap 条目中发现了不正确的标点符号。没有出现预期的冒号分隔符。请查看指定的 termcap，然后选择另一个条目或更正正在使用的条目。

-1010 Too many tc= indirections.

In a termcap definition for a terminal, the entry tc= causes the use of a definition for default values for a different terminal. That terminal might also have a tc= entry, and so on. However, 4GL cannot follow more than four tc= commands. The termcap definition in use at this time (as the TERM or TERMCAP environment variable specifies) exceeds the limit.

Write or find a termcap definition that is more self contained.

在终端的 termcap 定义中，条目 tc= 会将定义用于不同终端的默认值。该终端可能还有一个 tc= 条目等等。但是，4GL 不能??遵循四个以上的 tc= 命令。此时使用的 termcap 定义（如 TERM或TERMCAP 环境变量指定的）超出限制。请编写或查找更独立的 termcap 定义。

-1101 Variable address is NULL.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果该内部错误再次出现，请记下所有情况并联系 GBase 技术支持。

-1102 Field name not found in form.

A field name listed in an INPUT, INPUT ARRAY, CONSTRUCT, SCROLL or DISPLAY statement does not appear in the form specification of the screen form that is currently displayed. Review the program logic to ensure that the intended window is current, the intended form is displayed in it, and all the field names in the statement are spelled correctly.

在 INPUT、INPUT ARRAY、CONSTRUCT、SCROLL 或 DISPLAY 语句中列出的字段名称不会出现在当前屏幕显示的表单的表单规范中。请检查程序逻辑以确保预期的窗口是最新的，并显示了预期的表单，以及语句中的所有字段名的拼写都正确。

A common problem is the attempted use of field tags instead of field names. The field tag is the name that is written in the screen picture and that appears at the left side of the ATTRIBUTES statement for that field. It is not the name of the field for input or display purposes.

The field name is the column name with which it is associated. This name appears to the right of the equal sign in the ATTRIBUTES section.

常见的问题是试图使用字段标签而不是字段名称。字段标签是写在屏幕图片上的名称，它出现在该字段的 ATTRIBUTES 语句的左侧。它不能用于输入或显示目的。字段名是与其关联的列名。此名称在 ATTRIBUTES 部分里等号的右侧显示。

ATTRIBUTES f000 = customer.customer_num,color=red;The name of the field in the preceding example is customer_num. Use of the tag f000 in an INPUT statement will produce an error.

该示例中字段名是 customer_num。在 INPUT 语句中使用 f000 标签会产生错误。

-1103 This value is not among the valid possibilities.

A list or range of acceptable values has been established for this column (via an INCLUDE attribute in the form-specification file). You must enter a value within the acceptable range.

已经为该列建立了可接受值的列表或范围（通过表单规范文件中的 NCLUDE 属性）。必须输入一个在阈值范围内的值。

For 4GL programs, -1301 replaces this error.

对于 4GL 程序，其错误代码是 -1301。

-1104 The two entries were not the same. Try again.

To guard against typographical errors, this field has been designated VERIFY (in the form specification file). The value in this field must be entered twice, identically. Carefully reenter the data.

Alternatively, you can cancel the form entry with the Interrupt key(usually CTRL-C, but see the operating instructions that the program author supplied).

为防止排版错误，将该字段设计为 VERIFY（在表单规范文件中）。该字段中的值必须以相同的方式输入两次。注意再次输入数据。或者，您可以使用中止键（通常是 CTRL-C，但请参阅程序员提供的操作说明）取消表单条目。

For 4GL programs, -1302 replaces this error.

对于 4GL 程序，其错误代码是 -1302。

-1105 You cannot use this editing feature because a picture exists.

This field is defined (in the form specification file) with a PICTURE attribute to specify its format. You cannot use certain editing keys(for example, CTRL-A, CTRL-D, and CTRL-X) while you are editing such a field. Use only printable characters and the backspace to enter the value.

这个字段使用 PICTURE 属性定义它的格式（在表单规范文件中）。编辑这样的字段时，您不能使用某些编辑键（例如，CTRL-A、CTRL-D 和 CTRL-X）。只能使用可打印的字符和退格键输入值。

For 4GL programs, -1303 replaces this error.

对于 4GL 程序，其错误代码是 -1303。

-1106 Error in field.

You entered a value in this field that cannot be stored in the program variable that is meant to receive it. For example, possibly you entered a decimal number when the application provided only an integer variable, or you entered a character string that is longer than the application expected. Note all the circumstances and then discuss the problem with the person who wrote the application program.

您在此字段中输入的值不能存储在要接收它的程序变量中。例如，当应用程序只提供一个整型变量时但您输入了一个十进制数，或者输入的字符串比应用程序定义的长度长。注意所有情况，然后与编写应用程序的人讨论有关的问题。

For 4GL programs, -1304 replaces this error.

对于 4GL 程序，其错误代码是 -1304。

-1107 Field subscript out of bounds.

The subscript of a screen array in an INPUT, DISPLAY, or CONSTRUCT statement is either less than 1 or greater than the number of fields in the array. Review the program source in conjunction with the form specification to see where the error lies.

屏幕上 INPUT、DISPLAY 或 CONSTRUCT 语句中数组的下标小于 1 或大于数组中的字段数。

结合表单规范查看程序源以查找错误的位置。

-1108 Record not in form.

The screen record that is named in an INPUT ARRAY or DISPLAY ARRAY statement does not appear in the screen form that is now displayed.

Review the program source in conjunction with the form specification to see if the screen record names match.

在 INPUT ARRAY 或 DISPLAY ARRAY 语句中命名的记录没有出现在现在显示的屏幕表单中。

请结合表单规范和程序源查看屏幕记录名称是否匹配。

-1109 List and record field counts differ.

The number of program variables does not agree with the number of screen fields in a CONSTRUCT, INPUT, INPUT ARRAY, DISPLAY, or DISPLAY ARRAY statement. Review the statement in conjunction with the form specification to see where the error lies. Common problems include a change in the definition of a screen record that is not reflected in every statement that uses the record, and a change in a program record that is not reflected in the form design.

程序变量的数量与屏幕上 CONSTRUCT、INPUT、INPUT ARRAY、DISPLAY 或 DISPLAY ARRAY语句中的字段数目不一致。请结合表单规范查看语句来查找错误的位置。常见的问题包括在使用该记录的每个语句中没有反映屏幕上记录定义的修改，以及在程序记录中的更改没有反映在表单设计中。

-1110 Form file not found.

The form file that is specified in an OPEN FORM statement was not found. Inspect the "form-file" parameter of the statement. It should not include the file suffix.frm. However, if the form is not in the current directory, it should include a complete path to the file.

找不到 OPEN FORM 语句中指定的表单文件。请检查语句的“form-file”参数。它不应该包含文件 suffix.frm。但是，如果表单不在当前目录中，它应该包含文件的完整路径。

-1111 Field table offset out of bounds.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次出现，请记录所有情况并联系 GBase 技术支持。

-1112 A form is incompatible with the current 4GL version. Rebuild your form.

The form file that is specified in an OPEN FORM statement is not acceptable. Possibly it was corrupted in some way, or it was compiled with a version of the Form Compiler that is not compatible with the version of the 4GL compiler that compiled this program. Use a current version of the Form Compiler to recompile the form specification.

不接受 OPEN FORM 语句中指定的表单文件。可能是因为它已经被破坏，或者它是用与编译此程序的 4GL 编译器版本不兼容的 Form Compiler 的版本编译的。请使用用当前版本的 Form Compiler 重新编译表单规范。

-1113 Memory allocation error.

A BYTE or TEXT variable has been located in memory, and a value has been assigned to the variable. However, not enough data memory is available to hold the variable. Review the program, and locate the large value in a file instead.

一个 BYTE 或 TEXT 变量已位于内存中, 并且已为该变量分配了一个值。但是, 没有足够的数据内存可保存该变量。请复查该程序, 然后在文件中查找较大的值。

For 4GL programs, -1319 replaces this error.

对于 4GL 程序，其错误代码是 -1319。

-1114 No form has been displayed.

The current statement requires the use of a screen form. For example,DISPLAY...TO or an INPUT statement must use the fields of a form.

However, the DISPLAY FORM statement has not been executed since the current window was opened. Review the program logic to ensure that it opens and displays a form before it tries to use a form.

当前语句要求使用屏幕窗体。例如,DISPLAY...TO 或 INPUT 语句必须使用表单的字段。

但是, 自当前窗口打开后, DISPLAY FORM 语句尚未执行。检查程序逻辑确保它在尝试使用表单之前，表单已被打开并显示。

-1115 Numeric value too long for field.

4GL tried to format a numeric value for display in a form field, but the resulting string was too long for the field. Review the program logic to find out what large numeric value is being assigned.

4GL 试图格式化数值以在表单字段中显示，但结果字符串超出了字段长度。查看程序逻辑，找出正在分配的大数值。

For 4GL programs that were compiled at Version 5.0 and later or that are running under 4GL/GX, this error cannot occur.

对于在 V5.0 及更高版本中编译的 4GL 程序或在 4GL/GX 下运行的 4GL 程序，不会发生此错误。

-1116 Default value from form field cannot be converted to input variable type.

This statement takes input from a form field whose default value (which the ATTRIBUTES keyword DEFAULT specifies in the form) is not compatible with the program variable that receives it. Review all the program variables that are named in this statement, and compare them to the definitions of the fields in the form specification. Check that each variable corresponds to the intended field and has a compatible data type.

该语句从表单字段获取输入值，该表单字段的默认值（在表单中指定 ATTRIBUTES 的关键字 DEFAULT）与接收它的程序变量不兼容。查看在此语句中所有命名的程序变量，并将它们与表单规范中字段的定义进行比较。检查每个变量是否与预期的字段相对应并且具有兼容的数据类型。

-1117 Cannot convert date value to string.

This message is not believed to be in use in any current product. If the error recurs, note all circumstances and contact GBase Technical Support.

在任何当前产品中应该不会出现此消息。如果错误再次出现，请记录所有情况并联系 GBase 技术支持。

-1119 NEXT FIELD name not found in form.

This statement (INPUT or INPUT ARRAY) contains a NEXT FIELD clause that names a field that is not defined in the form. Perhaps the form has been changed, but the program has not. Also see the note for error message -1102.

该语句（INPUT 或 INPUT ARRAY）包含一个 NEXT FIELD 子句，用于命名未在表单中定义的字段。也许表单已经改变，但程序没有。另请参阅错误消息 -1102 的注释。

For 4GL programs, -1371 replaces this error.

对于 4GL 程序，其错误代码是 -1371。

-1120 Message file not found.

The message file that is specified in the HELP FILE clause of the most recent OPTIONS statement does not exist. Find that OPTIONS statement in the program, and review the "help-file" parameter. It must contain the complete filename of the prepared message file. If the file is not in the current directory, it must have a full pathname. Message files are prepared with the mkmessage utility.

在最近执行 OPTIONS 语句的 HELP FILE 子句中不存在指定的消息文件。请于程序中找到OPTIONS 语句，查看“help-file”参数。它必须包含预备消息文件的完整文件名。如果该文件不在当前目录中，则它必须具有完整的路径名。消息文件是使用 mkmessage 实用程序准备的。

For 4GL programs, -1227 replaces this error.

对于 4GL 程序，其错误代码是 -1227。

-1121 Message number not found in message file.

A message number that is given in the HELP clause of an INPUT, PROMPT,or MENU statement cannot be found in the current message file. The most- recently executed OPTIONS HELP FILE statement establishes the message file. Find that statement in the program, and verify that the message file is the one that you intended. Then review the source of that message file, and ensure that it contains definitions for all the message numbers that are used in the program. Recompile the message file with the mkmessage utility, and try the program again.

在当前消息文件中找不到 INPUT、PROMPT 或 MENEN 语句的 HELP 子句中给出的消息号。

最近执行的 OPTIONS HELP FILE 语句建立了消息文件。于程序中找到该语句，并验证消息文件是否是您想要的。然后查看该消息文件的来源，并确保它包含所有在程序中使用的消息编号的定义。使用 mkmessage 实用程序重新编译消息文件，然后再次尝试该程序。

For 4GL programs, -1228 replaces this error.

对于 4GL 程序，其错误代码是 -1228。

-1122 Incompatible message file.

The message file that is named in the most-recently executed OPTIONS HELP FILE statement was not acceptable. Possibly it has been corrupted in some way. Possibly the OPTIONS statement named the message source file instead of the compiled message file (the output of mkmessage).

Possibly the file was compiled with an outdated version of the mkmessage utility. Recompile the message file with the current version of the utility, and review the program source to make sure that it names the correct file.

最近执行的 OPTIONS HELP FILE 语句中的命名的消息文件是不可接受的。可能是因为它已经以某种方式损坏了。可能因为 OPTIONS 语句命名了消息源文件，而不是命名了编译的消息文件（ mkmessage 的输出）。可能是因为该文件是用旧版本的 mkmessage 实用程序编译的。请使用当前版本的实用程序重新编译消息文件，并查看程序源以确保它命名了正确的文件。

For 4GL programs, -1229 replaces this error.

对于 4GL 程序，其错误代码是 -1229。

-1123 No help file specified.

This INPUT, PROMPT, or MENU statement contains a HELP help-number clause; however, no message file has been established. The OPTIONS HELP FILE statement establishes the message file, but none has yet been executed. Review the program logic, and modify it to execute an OPTIONS statement with a HELP FILE clause before it is needed.

INPUT、PROMPT 或 MENU 语句包含一个 HELP help-number 子句；但是，没有建立消息文件。OPTIONS HELP FILE 语句建立了该消息文件，但是还没有执行。请检查程序逻辑，修改该程序以在需要之前执行具有 HELP FILE 子句的OPTIONS 语句。

For 4GL programs, -1343 replaces this error.

-1124 This field requires an entered value.

The cursor is in a form field that has been designated REQUIRED. You must enter some value before the cursor can move on to another field.

However, to enter a null value, type any printable character and then backspace. Alternatively, you can cancel the form entry with the Interrupt key (usually CTRL-C, but see the operating instructions that the program author supplied).

光标位于已被指定为 REQUIRED 的表单域中。在光标移动到另一个字段之前，您必须输入一些值。但是，要输入空值，请键入任何可打印的字符，然后退格。或者，您可以使用中断键（通常是 CTRL-C，但请参阅程序作者提供的操作说明）取消表单条目。

For 4GL programs, -1305 replaces this error.

对于 4GL 程序，其错误代码是 -1305。

-1125 Type again for verification.

The cursor is in a form field that has been designated VERIFY. You must enter the value twice, identically, before the cursor can move on to another field. This requirement helps to ensure that no typographical errors occur during data entry. Alternatively, you can cancel form entry with the Interrupt key (usually CTRL-C, but see the operating instructions that the program author supplied).

光标位于已被指定为 VERIFY 的表单域中。在光标移动到另一个字段之前，必须输入两次相同值。这一要求有助于确保在数据输入过程中不会发生排版错误。或者，您可以使用中断键取消表单输入（通常是 CTRL-C，但请参阅程序作者提供的操作说明）。

For 4GL programs, -1306 replaces this error.

对于 4GL 程序，其错误代码是 -1306。

-1126 Cannot insert another row - the input array is full.

You are entering data into an array of records that is represented in the program by an array of program variables. That array is now full;no place is available to store another record. Press the ACCEPT key(usually ESCAPE, but see the operating instructions that the program author supplied) to process the records that you have entered.

您正在将数据输入到由程序变量数组表示的记录数组中。该数组现在已满；没有地方存储另一条记录。请按 ACCEPT 键（通常是ESCAPE，但请参阅程序作者提供的操作说明）处理输入的记录。

For 4GL programs, -1307 replaces this error.

对于 4GL 程序，其错误代码是 -1307。

-1127 Cannot delete row - it has no data.

You pressed the Delete Row function key (usually F2, but see the operating instructions that the program author supplied) in an empty row. Nothing was deleted.

您在空行中按下了删除行功能键（通常为 F2，但请参阅程序作者提供的操作说明）。但没有删除任何数据。

For 4GL programs, -1308 replaces this error.

对于 4GL 程序，其错误代码是 -1308。

-1128 There are no more rows in the direction you are going.

You are attempting to scroll an array of records farther than it can go, either scrolling up at the top or scrolling down at the bottom of the array. Further attempts will have the same result.

您正在尝试将一组记录滚动到超出该数组范围的位置。无论是从顶部滚动还是从数组底部向下滚动。都会得到相同的结果。

For 4GL programs, -1309 replaces this error.

对于 4GL 程序，其错误代码是 -1309。

-1129 Field in BEFORE/AFTER clause not found in form.

This statement includes a BEFORE FIELD clause or an AFTER FIELD clause that names a field that is not defined in the form that is currently displayed. Review the program to ensure that the intended form was displayed, and review this statement against the form specification to ensure that existing fields are named. Also see the note on field names for error message -1102.

该语句包含一个 BEFORE FIELD 子句或一个 AFTER FIELD 子句，用于命名未在当前显示的表单中定义的字段。请查看该程序，以确保显示预期的表单，并根据表单规范检查此语句，以确保现有字段已经命名。有关错误消息 -1102，请参阅字段名称注释。

-1130 You cannot have multiple BEFORE clauses for the same field.

This statement includes at least two BEFORE FIELD clauses that name the same form field. Only one is supported. Find all the BEFORE FIELD clauses relate to one field, and combine them into a single clause.

该语句至少包含两个具有相同表单字段名称的 BEFORE FIELD 子句。但只支持其中一个。

请查找与字段相关的所有 BEFORE FIELD 子句，并将它们合并为一个子句。

-1131 You cannot have multiple AFTER clauses for the same field.

This statement includes at least two AFTER FIELD clauses that name the same form field. Only one is supported. Find all the AFTER FIELD clauses that relate to one field, and combine them into a single clause.

该语句至少包含两个具有相同表单字段名称的 AFTER FIELD 子句。但只支持其中一个。

请查找与字段相关的所有 AFTER FIELD 子句，并将它们合并为一个子句。

-1132 The destination string of the CONSTRUCT statement is not large enough.

The outcome of a CONSTRUCT statement is a character string that contains all the conditions that the user entered. This string is in a form suitable for use as the WHERE clause of a SELECT statement. In this CONSTRUCT statement, the result string is longer than the program variable that is specified to receive it. As a general rule, the length of the variable must allow enough room for the names of all the screen fields that are used in the statement, plus room for the field contents and for punctuation and relational operators. Review the statement,and revise the definition of the receiving variable accordingly.

CONSTRUCT 语句的结果是一个字符串，它包含用户输入的所有条件。该字符串的格式适合用作 SELECT 语句的 WHERE 子句。在此 CONSTRUCT 语句中，结果字符串的长度超出指定接收它的程序变量。通常情况下，变量的长度必须为语句中使用的所有屏幕字段名称留出足够的空间，并为字段内容以及标点符号和关系运算符留出空间。请检查该语句，并适当修改接收变量的定义。

-1133 The NEXT OPTION name is not in the menu.

This MENU statement contains a NEXT OPTION clause that names a menu-option that is not defined in the statement. The string that follows NEXT OPTION must be identical to one that follows a COMMAND clause in the same MENU statement. Review the statement to ensure that these clauses agree with each other.

此 MENU 语句包含一个 NEXT OPTION 子句，用于命名未在语句中定义的菜单选项。 NEXT OPTION 后面的字符串必须与同一个 MENU 语句中的 COMMAND 子句后面的字符串相同。请审查该语句以确保这些子句一致。

-1134 There is no termcap entry for this function key.

The key that is specified in one clause of this OPTIONS statement is not defined in the termcap file (or the terminfo file if you are using it instead). Review the HELP KEY, INSERT KEY, NEXT KEY, PREVIOUS KEY,and DELETE KEY clauses. Compare the function keys that they specify to the current termcap definition.

OPTIONS 语句的一个子句中指定的键未在 termcap 文件中定义（或者是 terminfo 文件，如果您正在使用它）。请查看 HELP KEY、INSERT KEY、NEXT KEY、PREVIOUS KEY 和DELETE KEY 子句。将它们指定的功能键与当前的 termcap 定义进行比较。

-1135 The row or column number in DISPLAY AT exceeds the limits of your terminal.

Review the DISPLAY...AT statement. Make sure that the position numbers are in the correct order (row number first, then column) and that they make sense for the current terminal or window. The dimensions of the terminal for UNIX systems are determined when the program starts by reading termcap information (or terminfo information, depending on the value of the GBASEDBTTERM environment variable). A screen location that is correct for one user of the program might not be correct for all. On DOS systems, the window size is always 24 lines by 80 characters.

检查 DISPLAY ... AT 语句。确保位置编号的顺序是正确的（行编号，然后是列编号），并且它们对当前终端或窗口是有意义的。UNIX 系统的终端尺寸是在程序开始时通过读取termcap 信息（或 terminfo 信息，取决于 GBASEDBTTERM 环境变量的值）确定的。

对于程序的一个用户而言，正确的屏幕位置可能对所有用户都不正确。在 DOS 系统上，窗口大小始终为 24 行× 80个字符。

-1136 Window is too large to fit on the screen.

The window dimensions that are specified in the WITH clause of this OPEN WINDOW statement conflict with the size of the screen. The entire window cannot be displayed, so the statement is not executed. If the WITH clause specifies dimensions, you can use smaller ones; if it specifies a form, the SCREEN statement in the form specification sets the dimensions. Alternatively, you might be able to get the window into the screen by changing the origin that is provided in the AT clause. The dimensions of the terminal for UNIX systems are determined when the program starts by reading termcap information (or terminfo information, depending on the value of the GBASEDBTTERM environment variable). Screen dimensions that are correct for one user of the program might not be correct for all. On DOS systems, the window size is always 24 lines by 80 characters.

在此 OPEN WINDOW 语句的 WITH 子句中指定的窗口尺寸与屏幕尺寸冲突。整个窗口无法显示，所以语句不会被执行。如果 WITH 子句指定维度，则可以使用较小的维度；如果它指定了表单，则使用表单规范中的 SCREEN 语句设置维度。或者，您可能可以通过更改 AT 子句中提供的原点将窗口置于屏幕中。UNIX 系统的终端尺寸是在程序开始时通过读取 termcap 信息（或 terminfo 信息，取决于 GBASEDBTTERM 环境变量的值）确定的。对于程序的一个用户来说正确的屏幕尺寸可能并不正确。在 DOS 系统上，窗口大小始终为 24 行 × 80 个字符。

-1137 Cannot open window.

The cause of the problem is a lack of data memory. Change the logic of the program to keep fewer windows open concurrently, or use fewer global variables.

问题的原因是缺少数据存储器。请修改程序逻辑，减少同时打开的窗口数，或使用较少的全局变量。

For 4GL programs, -1319 replaces this error.

对于 4GL 程序，其错误代码是 -1319。

-1138 Border does not fit on screen. Window is too large.

The window that this OPEN WINDOW statement describes cannot be opened because its border does not fit on the screen. Despite the wording of the message, the window is not necessarily too large for the screen.

However, one or more of its borders (top, bottom, left, or right)cannot be drawn. The position of the window is set in the OPEN WINDOWS statement; check that it starts no higher than row 2 and no farther left than column 2 (or else remove the BORDER attribute). The OPEN WINDOW statement or the form that it names sets the size of the window.

此 OPEN WINDOW 语句描述的窗口无法打开，因为其边框不适合屏幕。尽管消息的内容如此，但窗口不一定是太大。但是，它的一个或多个边界（顶部、底部、左侧或右侧）不能绘制。

在 OPEN WINDOWS 语句中设置窗口的位置；请检查它是否开始不高于第 2 行并且不比第 2列更远（否则删除 BORDER 属性）。OPEN WINDOW 语句或其命名的表单可以设置窗口的大小。

The dimensions of the terminal for UNIX systems are determined when the program starts by reading termcap information (or terminfo information,depending on the value of the GBASEDBTTERM environment variable). If the termcap entry includes sg#1 (terminfo: xmc#1), 4GL reserves an additional column to the left and right of a bordered window. On DOS systems, the window size is always 24 lines by 80 characters.

UNIX 系统的终端尺寸是在程序开始时通过读取 termcap 信息（或 terminfo 信息，取决于 GBASEDBTTERM 环境变量的值）确定的。如果 termcap 条目包含 sg＃1（terminfo：xmc＃1），则 4GL 会在有边框的窗口的左侧和右侧预留一个附加列。在 DOS 系统中，窗口大小始终为 24 行 × 80 个字符。

-1139 Form line cannot be set using LAST keyword.

This OPTIONS statement includes a FORM LINE clause that uses LAST. You can specify an absolute form line or one relative to FIRST, but you cannot specify it relative to LAST.

此 OPTIONS 语句包含使用 LAST 的 FORM LINE 子句。您可以指定独立表单行或与 FIRST相对的表单行，但不能将其指定为相对于 LAST。

-1140 NEXT OPTION is a hidden option.

The option that is named in this NEXT OPTION statement has previously been hidden with the HIDE OPTION statement. Because it is not visible to the user, it cannot be highlighted as the next choice.

该 NEXT OPTION 语句中命名选项在之前已经使用 HIDE OPTION 语句隐藏。因为它对用户不可见，所以它不能作为下一个选择突出显示。

-1141 Cannot close window with active INPUT, DISPLAY ARRAY, or MENU statement.

This CLOSE WINDOW statement cannot be executed because an input operation is still active in that window. The CLOSE WINDOW statement must have been contained in, or called from within, the input statement itself. Review the program logic, and revise it so that the statement completes before the window is closed.

由于输入操作在该窗口中仍处于活动状态，因此无法执行此 CLOSE WINDOW 语句。CLOSE WINDOW 语句必须包含在输入语句中或从其中调用。检查程序逻辑，修改程序以便在窗口关闭之前完成语句。

-1142 Window is too small to display this form.

The window dimensions of the current window are too small to contain the form that is to be displayed. Review the window dimensions, and compare them to all forms that will be displayed in that window. The dimensions of the form are established in the form-specification file with the SCREEN statement. The dimensions of the window are set during the OPEN WINDOW statement, either directly or by opening the window WITH a particular form.

当前窗口的窗口尺寸太小，不能包含要显示的表单。查看窗口尺寸，并将它与将在该窗口中显示的所有表单进行比较。使用 SCREEN 语句在窗体规范文件中建立表单的尺寸。在 OPEN WINDOW 语句中设置窗口的尺寸，可以直接或通过用特定表单打开窗口。

-1143 Window is already open.

This OPEN WINDOW statement names a window that is already open. Review the program logic, and see whether it should contain a CLOSE WINDOW statement, or whether it should simply use a CURRENT WINDOW statement to bring the open window to the top.

OPEN WINDOW 语句命名了一个已经打开的窗口。请检查程序逻辑，差看它是否应该包含一个 CLOSE WINDOW 语句，或者它是否能简单地使用 CURRENT WINDOW 语句将打开的窗口置于顶部。

-1144 Cannot open window. Window origin is not on the screen.

The row and column position in the AT clause of this OPEN WINDOW statement points off the physical screen. The statement is not executed. Review the program, and check that the numbers are in the correct order (first row, then column). The dimensions of the terminal are determined when the program starts by reading termcap information(or terminfo information, depending on the value of the GBase 8sTERM environment variable), so a window origin that is correct for some users might not be correct for all.

该 OPEN WINDOW 语句的 AT 子句中的行和列位置指向物理屏幕。没有执行该语句。

检查程序，并检查数字的顺序是否正确（第一行，然后是列）。当程序读取 termcap信息（或 terminfo 信息，取决于 GBASEDBTTERM 环境变量的值）时，终端的尺寸才被确定，因此对于某些用户来说正确的窗口原点可能对所有用户都不正确。

-1145 Cannot open ERROR window.

4GL attempted to open a one-line, 80-column window in which to display an error message but was not able to do so. Possible causes include a shortage of data memory and internal errors.

4GL 试图打开一个单行、80 列的窗口以显示错误消息，但不能这样做。可能的原因包括数据内存不足和内部错误。

For 4GL programs, -1319 replaces this error.

对于 4GL 程序，其错误代码是 -1319。

-1146 PROMPT message is too long to fit in the window.

Although 4GL truncates the output of MESSAGE and COMMENT to fit the window dimensions, it does not do so for PROMPT and the user's response. Reduce the length of the prompt string, or make the window larger. You could display most of the prompting text with DISPLAY and then prompt with a single space or colon.

尽管 4GL 截断了 MESSAGE 和 COMMENT 的输出以适合窗口尺寸，但它并不适用于 PROMPT和用户的响应。请缩短提示字符串的长度，或变大窗口。您可以使用 DISPLAY 显示大部分提示文字，然后用一个空格或冒号提示。

-1147 You cannot CLOSE, CLEAR or make CURRENT an unopened window.

This CLOSE WINDOW, CLEAR WINDOW, or CURRENT WINDOW statement names a window that has not been opened or has been closed. Review the program logic to ensure that it does not refer to an unopened window except to open it.

该 CLOSE WINDOW、CLEAR WINDOW 或 CURRENT WINDOW 语句指定可一个尚未打开或已关闭的窗口。检查程序逻辑以确保它不会引用未打开的窗口来打开它。

-1148 Size of a window may not be negative.

The AT clause of this OPEN WINDOW statement uses a negative number. The row and column sizes must be positive integers. Revise the statement.

该 OPEN WINDOW 语句的 AT 子句使用负数。行和列的大小必须是正整数。请修改该语句。

-1149 An unknown code has been detected in the form.

The screen form that is currently displayed is unacceptable in some way. Possibly it has been corrupted; possibly it was compiled by an obsolete version of form4gl. Recompile the form. If the problem recurs,note all circumstances and contact GBase Technical Support.

当前显示的屏幕格式在某些方面是不可接受的。可能是因为它已经被损坏；可能是因为它是由旧版本的 form4gl 编译的。请重新编译表单。如果问题再次出现，请记下所有情况并联系 GBase 技术支持。

-1150 Window is too small to display this menu.

Review the OPEN WINDOW statement for the current window in conjunction with this MENU statement. The window must be at least two rows tall,and it must be wide enough to display the menu title, the longest option name, two sets of three-dot ellipses, and six spaces. Revise the program to make the window larger or to give the menu a shorter name and shorter options.

结合该 MENU 语句查看当前窗口的 OPEN WINDOW 语句。该窗口必须至少有两排高度，并且必须足够宽以显示菜单标题、最长选项名称、两组三点椭圆和六个空格。请修改程序使窗口变大或缩短菜单名称和选项。

-1151 GBase 8s 4GL Run Time Facility.

This message is not believed to be in use in any current product. If the error recurs, note all circumstances and contact GBase Technical Support.

此消息已经不在任何当前产品中都在使用。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-1152 Enter value in range.

This error message is a version of message -1103/-1301, which is used by GBase 8s 4GL/RF with handheld terminals that have very small screens. See message -1103.

此错误消息是消息 -1103/-1301，GBase 8s 4GL/RF 使用具有非常小屏幕的手持终端。请参阅消息 -1103。

-1153 Bad verify -- reenter.

This message is a version of message -1104/-1302, which is used by GBase 8s 4GL/RF with handheld terminals that have very small screens.

See message -1104.

此消息是消息 -1104/-1302 的另一个版本，GBase 8s 4GL/RF 使用带有非常小屏幕的手持终端的消息。请参见消息 -1104。

-1154 Cannot use edit key.

This message is a version of message -1105/-1303, which is used by GBase 8s 4GL/RF with handheld terminals that have very small screens.

See message -1105.

此消息是消息 -1105/-1303 的另一个版本，GBase 8s 4GL/RF 使用带有非常小屏幕的手持终端的消息。

请参见消息 -1105。

-1155 Enter value in field.

This message is a version of message -1124/-1305, which is used by GBase 8s 4GL/RF with handheld terminals that have very small screens.

See message -1124.

此消息是消息 -1124/-1305 的另一个版本，GBase 8s 4GL/RF 使用带有非常小屏幕的手持终端的消息。

请参见消息 -1124。

-1156 Enter value again.

This message is a version of message -1125/-1306, which is used by GBase 8s 4GL/RF with handheld terminals that have very small screens.

See message -1125.

此消息是消息 -1125/-1306 的另一个版本，GBase 8s 4GL/RF 使用带有非常小屏幕的手持终端的消息。

请参见消息 -1125。

-1157 No more rows.

This message is a version of message -1127/-1309, which is used by GBase 8s 4GL/RF with handheld terminals that have very small screens.

See message -1127.

此消息是消息 -1127/-1309 的另一个版本，GBase 8s 4GL/RF 使用带有非常小屏幕的手持终端的消息。

请参见消息 -1127。

-1158 FMP has run out of memory.

FMP refers to GBase 8s 4GL/RF. See the installation documentation for your system.

FMP 是指 GBase 8s 4GL/RF。请参阅系统的安装文档。

-1159 FMP has exceeded its number of concurrent INPUT statements.

FMP refers to GBase 8s 4GL/RF. See the installation documentation for your system.

FMP 是指 GBase 8s 4GL/RF。请参阅系统的安装文档。

-1160 FMP has exceeded its number of concurrent DISPLAY ARRAY statements.

FMP refers to GBase 8s 4GL/RF. See the installation documentation for your system.

FMP 是指 GBase 8s 4GL/RF。请参阅系统的安装文档。

-1161 FMP currently is not in the midst of an INPUT statement.

FMP refers to GBase 8s 4GL/RF. See the installation documentation for your system.

FMP 是指 GBase 8s 4GL/RF。请参阅系统的安装文档。

-1162 FMP has exceeded the number of concurrently open forms.

FMP refers to GBase 8s 4GL/RF. See the installation documentation for your system.

FMP 是指 GBase 8s 4GL/RF。请参阅系统的安装文档。

-1163 The FMP version number is incompatible with the 4GL program. Relink the 4GL program and run again.

FMP refers to GBase 8s 4GL/RF. See the installation documentation for your system.

FMP 是指 GBase 8s 4GL/RF。请参阅系统的安装文档。

-1164 A NEXT FIELD specified in the instructions section of the form is not used within the current input statement.

The current form field has a NEXT FIELD specification (in the INSTRUCTIONS section of the form). However, the specified next field is not named in the current INPUT statement, so the cursor cannot move to that field.

当前表单字段具有 NEXT FIELD 规范（在表单的 INSTRUCTIONS 部分中）。但是，指定的下一个字段未在当前的 INPUT 语句中命名，因此光标无法移至该字段。

-1165 This statement is not allowed for the FMP.

FMP refers to GBase 8s 4GL/RF. See the installation documentation for your system.

FMP 是指 GBase 8s 4GL/RF。请参阅系统的安装文档。

-1166 An illegal code has been received from the FMP.

FMP refers to GBase 8s 4GL/RF. See the installation documentation for your system.

FMP 是指 GBase 8s 4GL/RF。请参阅系统的安装文档。

-1167 An unknown form name has been received by the FMP.

FMP refers to GBase 8s 4GL/RF. See the installation documentation for your system.

FMP 是指 GBase 8s 4GL/RF。请参阅系统的安装文档。

-1168 Command does not appear in the menu.

The SHOW OPTION, HIDE OPTION, or NEXT OPTION statement cannot refer to an option (command) that does not exist. Check the spelling of the name of the option.

SHOW OPTION、HIDE OPTION 或 NEXT OPTION 语句不能引用不存在的选项（命令）。

请检查选项名称的拼写。

-1170 The type of your terminal is unknown to the system.

Check the setting of your TERM environment variable and the setting of your TERMCAP or TERMINFO environment variable. Check with your system administrator if you need help with this action.

检查 TERM 环境变量的设置以及 TERMCAP 或 TERMINFO 环境变量的设置。

如果需要此操作的帮助，请咨询您的系统管理员。

-1171 A disallowed data type has been encountered by the FMP.

FMP refers to GBase 8s 4GL/RF. See the installation documentation for your system.

FMP 是指 GBase 8s 4GL/RF。请参阅系统的安装文档。

-1176 A COMMAND KEY value occurs elsewhere in the current menu.

In the indicated MENU statement, you defined a key value in more than one COMMAND KEY keylist or both in a COMMAND KEY keylist and as the default activation key for one or more nonhidden COMMAND clauses (for example, that key value is also the first character of one or more menu-option strings). This condition is illegal because MENU has no way to resolve what to do if the given keystroke occurs.

在指定的 MENU 语句中，在 COMMND KEY 键列表或 COMMAND KEY 键列表中定义了多个键值以及一个或多个非隐式 COMMAND 子句的缺省激活键（例如，该键值也是第一个字符一个或多个菜单选项字符串）。这种情况是非法的，因为如果发生给定的键，MENU 无法解决该怎么做。

A given key might appear as the default activation key for more than one COMMAND (without the KEY clause) because the user will be prompted for subsequent keystrokes until a unique string is obtained. This action is not possible with COMMAND KEY because only one keystroke is compared.

对于多个 COMMAND（没有 KEY 子句），给定的键可能会显示为默认激活键，因为会提示输入后续按键，直到获得唯一字符串。对于 COMMAND KEY，此操作不可行，因为只比较一个按键。

If a COMMAND is currently hidden (by using the HIDE OPTION keywords),its default activation key is ignored and does not trigger this particular error condition.

如果当前 COMMAND 被隐藏（通过使用 HIDE OPTION 关键字），则会忽略默认激活密钥，并且不会触发此特定错误情况。

-1200 Number is too large for a DECIMAL data type.

The float DECIMAL data type accommodates numbers greater than or equal to 1.000E-130 and less than 1.000E+126 in absolute value. The precision (number of significant digits) varies from 1 to 32; however, the source of this error is not the length of the number but its magnitude.

float DECIMAL数据类型可容纳大于或等于 1.000E-130 且绝对值小于 1.000E + 126 的数字。精度（有效位数）从 1 到 32 不等；然而，这个错误的来源不是数字的长度，而是数的大小。

-1201 Number is too small for a DECIMAL data type.

The DECIMAL data type accommodates numbers greater than or equal to 1.000E-130 and less than 1.000E+126 in absolute value. The precision (number of significant digits) varies from 1 to 32; however, the source of this error is not the length of the number but its magnitude.

DECIMAL数据类型可容纳大于或等于 1.000E-130 且绝对值小于 1.000E + 126 的数字。

精度（有效位数）从 1 到 32 不等；然而，这个错误的来源不是数字的长度，而是数的大小。

-1202 An attempt was made to divide by zero.

Zero cannot be a divisor. In some cases, this error arises because the divisor is a character value that does not convert properly to numeric.

零不能为除数。在某些情况下，会出现此错误，因为除数是不能正确转换为数字的字符值。

-1203 Values used in a MATCH must both be type CHARACTER.

The MATCHES relationship applies only to character data; both of its operands must be CHAR or VARCHAR columns or variables, or literal character strings.

If you need to apply a regular-expression pattern match to a numeric value,you can do so in 4GL. Assign the numeric value to a CHAR variable, and test that variable.

MATCHES 关系仅适用于字符数据；它的两个操作数必须是 CHAR 或 VARCHAR 列或变量或文字字符串。

如果您需要将正则表达式模式应用于数值，则可以在 4GL 中执行此操作。将数值分配给 CHAR 变量，然后测试该变量。

-1204 Invalid year in date.

The year in a DATE value or literal is invalid. For example, the number 0000 is not acceptable as the year.

DATE 值或文字中的年份无效。例如，0000 年的数字是不可接受的。

-1205 Invalid month in date.

The month in a DATE value or literal must be a one- or two-digit number from 1 to 12.

DATE 值或文字中的月份必须是从 1 到 12 的一位或两位数字。

-1206 Invalid day in date.

The day number in a DATE value or literal must a one- or two-digit number from 1 to 28 (or 29 in a leap year), 30, or 31, depending on the month that accompanies it.

DATE 值或文字中的日期数字必须是 1 到 28（或闰年中的 29），30 或 31 中的一位或两位数字，具体取决于随附的月份。

-1207 Converted value does not fit into the allotted space.

A noncharacter value, after conversion to a character string, is too long to fit in the buffer that was provided.

转换为字符串后的非字符值太长，无法放入提供的缓冲区中。

If the conversion was automatic, change the program to provide a larger host variable to receive the string.

如果转换是自动的，请更改程序以提供更大的主机变量来接收字符串。

If this action was an explicit call to conversion function, pass a larger buffer.

如果此操作是对转换函数的显式调用，则传递更大的缓冲区。

-1209 Without any delimiters, this date must contain exactly 6 or 8 digits.

When a literal date value is entered in numeric form, not enclosed in quotes to make it a character string, it must be entered as a number of precisely 6 digits (representing mmddyy) or 8 digits (representing mmddyyyy). Because no punctuation is present, a date with any other number of digits is ambiguous; it cannot be divided into month, day,and year with certainty.

如果以数字形式输入文字日期值，而不是用引号括起来使其成为字符串，则必须输入正好 6 位数字（代表 mmddyy）或8位数字（代表 mmddyyyy）的数字。由于没有标点符号，因此具有任何其他数字位数的日期是不明确；它不能确定地分为月、日、年。

-1210 Date could not be converted to month/day/year format.

The DATE type is compatible with the INTEGER type, but not all integer values are valid dates. This error arises in attempts to convert to character from a date whose numeric value is less than -693,594 or greater than 2,958,464.

Numbers that are outside this range have no representation as dates.

DATE 类型与 INTEGER 类型兼容，但并非所有整数值都是有效的日期。尝试从数字值小于 -693,594 或大于 2,958,464 的日期转换为字符时出现此错误。超出此范围的数字不能表示为日期。

You may also see this message if you try to use the VARIANCE() or STDEV()functions on an inappropriate data type, such as DATE.

如果尝试在不适当的数据类型（如 DATE）上使用 VARIANCE()或 STDEV()函数，也可能会看到此消息。

-1211 Out of memory.

4GL cannot allocate memory for a small, temporary work area that is used for processing an expression. To avoid this error, simplify the program in almost any way to release enough space不能为用于处理表达式的小型临时工作区域分配内存。为了避免这个错误，请通过任何方式简化程序以释放足够的空间。

-1212 Date conversion format must contain a month, day, and year component.

When a date value is converted between internal binary format and display or entry format, a pattern directs the conversion. When conversion is done a utomatically, the pattern comes from the environment variable DBDATE. When it is done with an explicit call to the rfmtdate(), rdefmtdate(), or USING functions, a pattern string is passed as a parameter. In any case, the pattern string (the format of the message) must include letters that show the location of the three parts of the date: 2 or 3 letters d; 2 or 3 letters m; and either 2 or 4 letters y.

当日期值在内部二进制格式和显示或输入格式之间转换时，模式会指示转换。转换自动完成时，模式来自环境变量 DBDATE。当完成对 rfmtdate()、rdefmtdate()或 USING 函数的显式调用时，模式字符串将作为参数传递。在任何情况下，模式字符串（消息格式）必须包含显示三部分日期位置的字母：2 或 3 个字母 d； 2 或 3 个字母 m；2 或 4 个字母 y。

-1213 A character to numeric conversion process failed.

A character value is being converted to numeric form for storage in a numeric column or variable. However, the character string cannot be interpreted as a number. It contains some characters other than white space, digits, a sign, a decimal, or the letter e; or the parts are in the wrong order, so the number cannot be deciphered.

字符值正在转换为数字形式以存储在数字列或变量中。但是，字符串不能被解释为数字。

它包含除空格、数字、符号、小数或字母 e 以外的一些字符；或者部分顺序错误，所以编号无法被破译。

If you are using NLS, the decimal character or thousands separator might be wrong for your locale.

如果您使用的是 NLS ，则语言环境可能会出现小数字符或千位分隔符错误。

-1214 Value too large to fit in a SMALLINT.

The SMALLINT data type can accept numbers with absolute values from 0 through 32,767 (plus or minus (2 to the 15th power) - 1). To store numbers that are outside this range, redefine the column or variable to use INTEGER or DECIMAL type. (The value -32,768 is a 16-bit value but is not acceptable; it indicates a null value in 4GL.)SMALLINT 数据类型可以接受绝对值从 0 到 32,767（加号或减号（2 的 15 次方）-1）的数字。要存储超出此范围的数字，请重新定义列或变量以使用 INTEGER 或 DECIMAL 类型。（值 -32,768 是 16 位值，但不可接受；它表示 4GL 中的空值。）-1215 Value too large to fit in an INTEGER.

The INTEGER or SERIAL data type can accept numbers with absolute values from 0 through 2,147,483,647 (plus or minus (2 to the 31st power) - 1).

INTEGER 或 SERIAL 数据类型可以接受绝对值从 0 到 2,147,483,647（加号或减号（2 的 31 次方） - 1）的数字。

To store numbers that are outside this range, redefine the column or variable to use the BIGINT or BIGSERIAL or INT8 or SERIAL8 data type or the DECIMAL data type. For more information on valid ranges of data types, see the GBase 8s Guide to SQL: Reference.

要存储超出此范围的数字，请重新定义列或变量，使用 BIGINT 或 BIGSERIAL 或 INT8或 SERIAL8 数据类型或 DECIMAL 数据类型。有关数据类型的有效范围的更多信息，请参阅 GBase 8s SQL 指南：参考。

-1216 Illegal exponent.

The exponent of a numeric literal cannot exceed 32,767. In fact, none of the available data types can accommodate an exponent that large.

However, the exponent itself triggers this message before checking the destination of the number. Check the statement for missing or misplaced punctuation that might have caused two numbers to run together.

数字的指数不能超过 32,767。事实上，没有一种可用的数据类型可以容纳一个很大的指数。

但是，指数它本身在检查数的目标之前触发此消息。检查语句是否有可能导致两个数字一起运行的缺失或错位的标点符号。

-1217 The format string is too large.

The pattern string that is used to format a date (either the DBDATE environment variable or the pattern that is passed to rfmtdate() or the USING function) is too long. The limit is 80 bytes.

用于格式化日期的模式字符串（DBDATE 环境变量或传递给 rfmtdate()或 USING 函数的模式）太长。限制是 80 字节。

-1218 String to date conversion error.

The input to the rstrdate() function does not properly represent a date: either it has nondigits where digits are expected, an unexpected delimiter, or numbers that are too large or are inconsistent.

rstrdate（）函数的输入不能正确表示一个日期：要么有非数字，其中数字是预期的，例外的分隔符，或者数字太大或不一致。

-1219 Numeric value from database is too large for COBOL data item.

This message is not believed to be in use in any current product.

If the error recurs, note all circumstances and contact GBase Technical Support.

此消息任何当前产品中都不再使用。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-1220 Numeric value from database is too small for COBOL data item.

This message is not believed to be in use in any current product.

If the error recurs, note all circumstances and contact GBase Technical Support.

此消息任何当前产品中都不再使用。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-1221 Cannot convert null data types.

This message is not believed to be in use in any current product.

If the error recurs, note all circumstances and contact GBase Technical Support.

此消息任何当前产品中都不再使用。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-1222 Value will not fit in a SMALLFLOAT.

The SMALLFLOAT data type can accept numbers within a certain range of exponents.

The maximum and minimum exponent values are different depending on the host operating system (the range is the same as that supported by the C compiler for float values in this system). In the current statement, a constant number is being converted for storage in a FLOAT variable or column, and the exponent is too large or too small.

SMALLFLOAT 数据类型可以接受指定范围内的数字。最大和最小指数值根据主机操作系统而不同（范围与 C 编译器针对此系统中的浮点值所支持的范围相同）。在当前的语句中，一个常数被转换为 FLOAT 变量或列中的存储值，并且指数太大或太小。

-1223 Value will not fit in a FLOAT.

The FLOAT data type can accept numbers within a certain range of exponents.

The maximum and minimum exponent values are different depending on the host operating system (the range is the same as that supported by the C compiler for double values in this host system). In the current statement, a constant number is being converted for storage in a FLOAT variable or column, and the exponent is too large or too small.

FLOAT 数据类型可以接受指定范围内的数字。最大和最小指数值根据主机操作系统而不同（该范围与 C 编译器在此主机系统中为 double 值所支持的范围相同）。在当前的语句中，一个常数被转换为 FLOAT 变量或列中的存储值，并且指数太大或太小。

-1224 Invalid decimal number.

This message is not believed to be in use in any current product.

If the error recurs, note all circumstances and contact GBase Technical Support.

此消息任何当前产品中都不再使用。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-1225 Column does not admit a NULL value.

This statement attempted to store a null value in a column that has been defined as not allowing nulls. Review the definition of the table, and revise the statement so that it supplies values for all required columns.

该语句试图在已经被定义为不允许空值的列中存储空值。检查表的定义，并修改该语句，以便为所有需要的列提供值。

-1226 Decimal or money value exceeds maximum precision.

The client is attempting to convert a number into a DECIMAL or MONEY variable.

However, the number has more digits to the left of the decimal point than the declaration of the variable allows. Revise the program to assign the converted number to a variable with an appropriate precision.

客户端正试图将数字转换为 DECIMAL 或 MONEY 变量。但是，该数字在小数点左侧的位数比变量声明允许的位数多。修改程序将转换后的数字以适当的精度分配给变量。

-1227 Message file not found.

4GL cannot locate a file of message texts. The file should have a suffix of .iem and be in the product directory, $GBS_HOME/msg. Reinstall such files from the distribution materials. If you have started to modify the user-message file, 4glusr.msg,check that its compiled form has been replaced in the correct directory.

4GL 无法找到消息文本的文件。该文件的后缀应为 .iem，并位于产品目录 $GBS_HOME/msg 中。

从发布材料中重新安装这些文件。如果您已经开始修改用户消息文件 4gl usr.msg，请检查其编译后的表单是否已被替换为正确的目录。

-1228 Message number not found in message file.

4GL cannot find a message number that should appear in a message file that was installed with the product. Reinstall all files of type .iem from the distribution materials. If you have modified the contents of the file, 4glusr.msg, review all deletions that you might have made,and recompile that file.

4GL 找不到应该出现在与产品一起安装的消息文件中的消息编号。从发布材料中重新安装所有类型为 .iem 的文件。如果您修改了文件 4glusr.msg 的内容，请检查您所做的所有删除操作，然后重新编译该文件。

-1229 Incompatible message file.

4GL is trying to look up a message text in a message file, but the file contents do not match the current version of the product. Possibly the file is corrupt; possibly a message file from a prior version is present.

The file has a suffix of .iem and exists in the etc subdirectory of the path that the GBS_HOME environment variable identifies. Reinstall such files from the distribution materials. If you have started to modify the user-message file, 4glusr.msg, make sure that you are recompiling it with a current version of the mkmessage utility.

4GL 试图在消息文件中查找消息文本，但文件内容与当前版本的产品不匹配。可能文件已损坏;可能存在来自先前版本的消息文件。该文件的后缀为 .iem，并存在于 GBS_HOME 环境变量标识的路径的 etc 子目录中。从发布材料中重新安装这些文件。如果已开始修改用户消息文件 4glusr.msg，请确保使用当前版本的 mkmessage 实用程序重新编译它。

-1230 Bad message file name formulation.

An invalid filename has been supplied for the message file that is usedfor displaying error messages such as the ones in this book, so thefile cannot be opened. Check the value of the DBLANG environment variable, if one is specified.

为用于显示错误消息的消息文件提供了无效的文件名，例如本书中的错误消息，因此文件无法打开。请检查 DBLANG环境变量的值（如果指定）。

-1231 Cannot seek within message file.

The application is trying to look up a message text in a message file but receives an error code when it tries to position within the file.

This situation indicates some problem with the file itself; possibly it has been corrupted or truncated. Reinstall all files of type .iem from the distribution materials. If you have modified the user-message file,4glusr.msg, recompile it as well.

应用程序试图在消息文件中查找消息文本，但在尝试定位文件时收到错误代码。这种情况表明文件本身存在一些问题；可能它已被损坏或截断。从发布材料中重新安装所有类型为.iem 的文件。如果已修改用户消息文件 4glusr.msg，请重新编译它。

-1232 Message buffer too small.

4GL is reading a message text from a compiled message file but cannot resize the buffer to be large enough to hold the complete message. This situation might indicate a critical shortage of data space, but more probably it indicates a corrupted or invalid message file. Reinstall all files of type .iem from the distribution materials. If you have modified the user-message file, 4glusr.msg, recompile it as well.

4GL 正在从编译的消息文件中读取消息文本，但无法调整缓冲区的大小以容纳完整的消息。

这种情况可能表明数据空间严重不足，但更可能表明损坏或无效的消息文件。从发布材料中重新安装所有类型为 .iem 的文件。如果已修改用户消息文件 4glusr.msg，请重新编译它。

-1233 Invalid hour, minute, or second.

This message is not believed to be in use in any current product. If the error recurs, note all circumstances and contact GBase Technical Support.

此消息已不再在任何当前产品中使用。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-1234 Function may be applied only to datetime data types.

This message is not believed to be in use in any current product. If the error recurs, note all circumstances and contact GBase Technical Support.

此消息已不再在任何当前产品中使用。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-1235 Character host variable is too short for the data.

In an ESQL/C program, the program has attempted to fetch a column value into a host variable that is not large enough. Use the DESCRIBE command to find out the sizes of column values.

在 ESQL/C 程序中，程序试图将列值访存一个不够大的主变量。使用 DESCRIBE 命令找出列值的大小。

If this error arises in a 4GL program, note all circumstances and contact GBase Technical Support.

如果在 4GL 程序中出现此错误，请注意所有情况并联系 GBase 技术支持。

-1236 Bad era date.

The era name or the era offset that is given in the input string is invalid or has not been entered in the required format. Check that the era name and offset are valid and in the proper order in the input string. Check the format against the value of DBTIME, DBDATE, or the format string passed to the SQL API function, whichever is appropriate.

输入字符串中给出的时代名称或时代偏移量无效或未按所需格式输入。检查时代名称和偏移量是否有效，并按照输入字符串中的正确顺序。根据 DBTIME、DBDATE 的值或传递给 SQL API 函数的格式字符串。

-1237 Bad era name.

The date format requires an era name, but no name that matches the era names in the GLS locale could be found in the input string. Check that you are using the correct locale and that you entered the era name correctly.

日期格式需要年代名称，但在输入字符串中可找不到与 GLS 语言环境中的时代名称匹配的名称。检查您是否使用了正确的语言环境，并且输入了正确的时代名称。

-1238 Bad era initialization.

Contact GBase Technical Support regarding this internal error.

有关此内部错误，请联系 GBase 技术支持。

-1239 Era year overflow.

The era offset that is given is not within the range for the era that is specified. Check that the era offset is within the valid range for the era that is specified.

给出的时代偏差不在所指定时代的范围内。请检查时代偏移量是否在指定时代的有效范围内。

-1250 Unable to create pipes.

Your application is using an operating-system facility called a pipe to initialize its communication with the database server. The operating system returned an unexpected error. Look for operating-system error messages that might give more information.

您的应用程序使用称为管道的操作系统工具来初始化与数据库服务器的通信。操作系统返回了意外错误。

查找可能提供更多信息的操作系统错误消息。

-1251 Unable to create shared memory. semget failed.

Your application is initializing its communication with the database server, which is a version that uses shared memory for communications.

An unexpected error has occurred with an operating-system function,semget. Look for operating-system messages that might give more information. Consult with the person who installed the GBase 8s shared-memory product.

您的应用程序正在初始化与数据库服务器的通信，该数据库服务器是使用共享内存进行通信的版本。操作系统函数 semget 发生意外错误。查找可能提供更多信息的操作系统消息。

请咨询安装 GBase 8s 共享内存产品的人员。

-1252 Unable to create shared memory. shmget failed.

Your application is initializing its communication with the database server, which is a version that uses shared memory for communications.

An unexpected error has occurred with an operating-system function,shmget. Look for operating-system messages that might give more information. Consult with the person who installed the GBase 8s shared-memory product.

请咨询安装 GBase 8s 共享内存产品的人员。

-1254 Unable to connect to remote host.

The program is attempting to open a database that a database server in another system manages, but it could not open a network connection to the other system. Check the site name that the DATABASE or CREATE DATABASE statement specifies. If it is as you intended, look for other error messages from the networking component or the operating system.

Contact the operator of the other system to verify that it is active and accepting network connections.

该程序正试图打开另一个系统中的数据库服务器管理的数据库，但它无法打开到另一个系统的网络连接。

检查 DATABASE 或 CREATE DATABASE 语句指定的站点名称。如果它符合您的要求，请查找网络组件或操作系统中的其他错误消息。联系另一个系统的操作员以验证它是否处于活动状态并接受网络连接。

-1257 Operating system cannot fork process for back end.

Back end refers to the database server. If this is an internal error, look for operating-system messages that might give more detail. In DOS systems, you probably are out of memory; exit to the operating-system command line, and resubmit your program. After you verify that no system limit or local problem exists, note all circumstances and contact GBase Software Support.

后台指的是数据库服务器。如果这是内部错误，请查找可能提供更多详细信息的操作系统消息。在 DOS 系统中，可能是因为内存不足；请退出到操作系统命令行，然后重新提交程序。在确认没有系统限制或本地问题存在之后，请记下所有情况并联系 GBase 软件支持。

-1258 Cannot attach to shared memory used to communicate with back end.

Back end refers to the database server. In this internal error, look for operating-system messages that might give more detail. After you verify that no system limit or local problem exists, note all circumstances and contact GBase Technical Support.

后台指的是数据库服务器。在这个内部错误中，查找可能提供更多细节的操作系统消息。在确认没有系统限制或本地问题后，请记下所有情况并联系 GBase 技术支持。

-1260 It is not possible to convert between the specified types.

The database server attempts any data conversion that makes sense. Some conversions, however, are not supported, such as INTERVAL to DATE, DATETIME to MONEY, CHAR to LIST, or CHAR to SET. Possibly you referenced the wrong variable or column. Check that you have specified the data types that you intended and that literal representations of data values are correctly formatted.

数据库服务器尝试进行数据转换。但是，某些转换是不支持的。例如：从 INTERVAL 到 DATE、DATETIME 到 MONEY、CHAR 到 LIST 、CHAR 到 SET 的转换。可能是因为您引用了错误的变量和列。

请检查您想要指定的数据类型和数据值的文字表达式是否正确。

-1261 Too many digits in the first field of datetime or interval.

The first field of a DATETIME literal must contain either 1 or 2 digits(if it is not a YEAR) or else 2 or 4 digits (if it is a YEAR). The first field of an INTERVAL literal represents a count of units and can have up to 9 digits, depending on the precision that is specified in its qualifier. Review the DATETIME and INTERVAL literals in this statement, and correct them.

DATETIME 文字的第一个字段必须包含 1 或 2 个数字（如果不是 YEAR）或 2 或 4 个数字（如果它是 YEAR）。INTERVAL 文字的第一个字段表示单位的计数，最多可以有 9 位数字，具体取决于其限定符中指定的精度。请检查该语句中的 DATETIME 和 INTERVAL 文字，并纠正它们。

-1262 Non-numeric character in datetime or interval.

The form of a DATETIME or INTERVAL literal is very limited. One can contain only decimal digits and the allowed delimiters: the hyphen between year, month, and day numbers; the space between day and hour;the colon between hour, minute, and second; and the decimal point between second and fraction. Any other characters, or these characters in the wrong order, produce an error.

DATETIME 或 INTERVAL 文字的格式非常有限。一个只能包含十进制数字和允许的分隔符：年、月、日之间的连字符；日和小时之间的空格；小时、分钟和秒之间的冒号；以及秒和分数之间的小数点。任何其他字符或错误顺序的这些字符都会产生错误。

-1263 A field in a datetime or interval is out of range, incorrect, or missing.

Inspect the DATE, DATETIME, and INTERVAL literals in this statement;at least one of them contains at least one incorrect field or is missingat least one field.

检查该语句中的 DATE、DATETIME 和I NTERVAL 文字；其中至少有一个文字至少包含一个不正确的字段或缺少至少一个字段。

In a DATE or DATETIME literal, the year might be zero, the month might be other than 1 to 12, or the day might be other than 1 to 31 or inappropriate for the month. Also in a DATETIME literal,the hour might be other than 0 to 23, the minute or second might be other than 0 to 59, or the fraction might have too many digits for the specified precision.

在 DATE 或 DATETIME 文字中，年份可能为零，月份可能不是 1 至 12 ，或者该日期可能不是 1 至 31 或月份不合适。同样在 DATETIME 文字中，小时可能不是0 到 23，分钟或秒可能不是 0 到 59，或者小数可能具有指定精度的数字太多。

In an INTERVAL literal, the constraints are the same except that thefirst field is a count and can have as many digits as the qualifier specifies.

在 INTERVAL 文字中，约束条件相同，只是第一个字段是一个计数并且可以具有与限定符指定的数量一样多的数字。

-1264 Extra characters at the end of a datetime or interval.

Only spaces can follow a DATETIME or INTERVAL literal. Inspect this statement for missing or incorrect punctuation.

只有空格可以遵循 DATETIME 或 INTERVAL 文字。请检查这个语句是否缺少或是否包含不正确的标点符号。

-1265 Overflow occurred on a datetime or interval operation.

Both DATETIME and INTERVAL values are stored internally as DECIMAL values. In this statement, an arithmetic operation that uses DATETIME and/or INTERVAL values has caused an arithmetic overflow. This situation should not occur. Check the precision that is specified for an INTERVAL value. If the INTERVAL value that you want to enter is greater than the default number of digits that are allowed for that field, you must explicitly identify the number of significant digits in your definition. If the error recurs, note all circumstances and contact GBase Technical Support.

DATETIME 和 INTERVAL 值均作为 DECIMAL 值存储在内部。在此语句中，使用 DATETIME和/或 INTERVAL 值的算术运算会导致算术溢出。这种情况不应该发生。检查为 INTERVAL值指定的精度。如果您想要输入的 INTERVAL 值大于默认允许的位数字段，则必须明确标识定义中有效数字的数量。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-1266 Intervals or Datetimes are incompatible for the operation.

Some arithmetic combinations of DATETIME, INTERVAL, and numeric values are meaningless and are not allowed. Review the arithmetic expressions in this statement. Possibly one of them is using a DATETIME or INTERVAL column or variable by mistake. If not, see your SQL reference material for the valid use of these data types.

DATETIME、INTERVAL 和数值的某些算术组合是没有意义的，也是不允许的。请查看本语句中的算术表达式。可能是错误地使用了 DATETIME 或 INTERVAL 列或变量。如果没有，请参阅您的 SQL 参考资料以了解这些数据类型的有效用法。

-1267 The result of a datetime computation is out of range.

In this statement, a DATETIME computation produced a value that cannot be stored. This situation can occur, for example, if a large interval is added to a DATETIME value. This error can also occur if the resultant date does not exist, such as Feb 29, 1999.

在此语句中，DATETIME 计算产生了一个无法存储的值。例如，如果将一个大的 interval 值加 DATETIME 值，则会发生这种情况。如果生成的日期不存在，例如 1999 年 2 月 29日，也可能出现此错误。

Review the expressions in the statement and see if you can change the sequence of operations to avoid the overflow.

请检查语句中的表达式并查看是否可以更改操作序列以避免溢出。

-1268 Invalid datetime or interval qualifier.

This statement contains a DATETIME or INTERVAL qualifier that is not acceptable. These qualifiers can contain only the words YEAR, MONTH,DAY, HOUR, MINUTE, SECOND, FRACTION, and TO. A number from 1 to 5 in parentheses can follow FRACTION. Inspect the statement for missing punctuation and misspelled words. A common error is adding an s, as in MINUTES.

此语句包含不可接受的 DATETIME 或 INTERVAL 限定符。这些限定词只能包含YEAR、MONTH、DAY、HOUR、MINUTE、SECOND、FRACTION 和 TO 等词。括号中的数字 1 到 5 可以跟在分数之后。请检查是否缺少标点，单词的拼写是否错误。

常见的错误是多添加了一个 s，如在 MINUTES 中。

-1269 Locator conversion error.

This message was issued because a function that requires an argument that is a locator (a reference to a BYTE or TEXT value) received something other than a valid locator (such as a NULL parameter, or an argument of any other data type).

发出此消息是因为需要参数为定位符的函数（引用 BYTE 或 TEXT 值）接收到除有效定位符（例如 NULL 参数或任何其他数据类型的参数）之外的其他数据。

Review the program logic to make sure the arguments are correct.

请检查程序逻辑，确保参数是正确的。

-1270 Interval literal may not have embedded minus sign.

You can use a minus sign as an arithmetic operator between an INTERVAL literal and other values, and you can use a minus sign as a prefix to an INTERVAL literal to indicate it is a negative quantity. However, you cannot embed a minus sign among the fields of the literal. If you did not intend to do this, inspect the statement for missing or misplaced punctuation.

可以在 INTERVAL 文字和其他值之间使用减号作为算术运算符，并且可以使用减号作为 INTERVAL 文字的前缀以指示它是负数量。但是，不能在文字的字段中嵌入减号。如果您并没有这样做，请检查语句是否有错误或错位的标点符号。

-1271 Missing decimal point in datetime or interval fraction.

A decimal point is expected to appear in a DATETIME or INTERVAL literal when the qualifier of the literal contains the word FRACTION. This statement has such a literal, but no decimal point was found. Inspect the literal qualifiers for missing or misplaced punctuation.

当文字的限定符包含单词 FRACTION 时，预计小数点会出现在 DATETIME 或 INTERVAL文字中。该语句具有这样的文字值，但没有小数点。请检查文字修饰符是否丢失，或者包含了错位标点符号。

-1272 No input buffer has been specified.

You have not specified an input string for this function, so the conversion cannot proceed. Set the input-string argument, and call the function again. (This function might require that you define formatting directives with the DBTIME environment variable.)您尚未为此功能指定输入字符串，因此转换无法继续。设置输入字符串参数，然后再次调用该函数。（此函数可能需要使用 DBTIME 环境变量定义格式化指令。）-1273 Output buffer is NULL or too small to hold the result.

This error is returned when the function is called and the address space for the output buffer is null or smaller than the format-string length. Redefine the size of the address, and execute the function again. (This function might require that you define formatting directives with the DBTIME environment variable.)当调用函数并且输出缓冲区的地址空间为空或小于格式字符串长度时，将返回此错误。

请重新定义地址的大小，然后再次执行该函数。（此函数可能需要使用 DBTIME 环境变量定义格式化指令。）-1274 No output buffer has been specified.

The output buffer length is zero, or the buffer pointer is a null pointer.

输出缓冲区长度为零，或者缓冲区指针为空指针。

-1275 Invalid field width or precision in datetime or interval format string.

The field width or precision in DATETIME or INTERVAL format specification must make sense. The field width must be a decimal number, with a leading zero or minus ( - ) sign. If a precision specification is present, it must also be decimal, separated from the field-width specification by a period.

DATETIME 或 INTERVAL 格式规范中的字段宽度或精度必须有意义。字段宽度必须是十进制数字，并带有前导零或减号(-)。如果存在精度规格，则它也必须是十进制数，与字段宽度规格分隔一段时间。

-1276 Format conversion character not supported.

A format conversion character in the format string is not valid. Check the string against the table of format conversion directives for DATETIME and INTERVAL format conversion functions in the manual for your embedded language product. See also the discussion of the DBTIME environment variable in the GBase 8s Guide to SQL: Reference.

格式字符串中的格式转换字符无效。在嵌入式语言产品的手册中，根据格式转换指令表检查字符串是否适用于 DATETIME 和 INTERVAL 格式转换功能。另请参阅 “GBase 8s SQL 指南：参考” 中对 DBTIME 环境变量的讨论。

-1277 Input does not match format specification.

Check that the ASCII string that contains a DATETIME or INTERVAL value conforms to the format string. For example, a percent character in a DATETIME or INTERVAL ASCII string must have a matching "%%" sequence in the format string. See also the discussion of the DBTIME environment variable in the GBase 8s Guide to SQL: Reference.

检查包含 DATETIME 或 INTERVAL 值的 ASCII 字符串是否符合格式字符串。例如，DATETIME 或 INTERVAL ASCII 字符串中的百分号字符在格式字符串中必须具有匹配的“%%”序列。另请参阅“GBase 8s SQL 指南：参考”中对 DBTIME 环境变量的讨论。

If you are using the ROUND() or TRUNC() build-in functions on DATE or DATETIME data types, note that the list of supported values for the second parameter is "YEAR", "MONTH", "DAY", "DD", "HH" or "MI". Please refer to the discussion on "Algebraic Functions" in the GBase 8s Guide to SQL: Syntax for the details.

如果在 DATE 或 DATETIME 数据类型中使用 ROUND()或 TRUNC()内置函数，请注意第二个参数支持的值列表为“YEAR”、“MONTH”、“DAY”、“DD” 、“HH”或“MI”。有关详细信息，请参阅“GBase 8s SQL 指南：语法”中关于“代数函数”的讨论。

-1278 Invalid escape sequence.

Check the pattern-matching string that the LIKE or MATCHES clause of the statement specifies. In an ANSI database, the only valid characters that can be escaped are: %, _, and the escape character for the LIKE clause, and *, ?, [, ], and the escape character for the MATCHES clause.

检查语句中 LIKE 或 MATCHES 子句指定的模式匹配字符串。在 ANSI 数据库中，唯一可以转义的有效字符是：LIKE 子句的％、_和转义字符，以及 MATCHES 子句的 *、?、[，]和转义字符。

-1279 Value exceeds string column length.

This message applies only to ANSI databases. You attempted to insert into a CHAR, NCHAR, VARCHAR, NVARCHAR or LVARCHAR column using a string host variable, but the string is too long.

此消息仅适用于 ANSI 数据库。您试图使用字符串主变量插入 CHAR、NCHAR、VARCHAR、NVARCHAR 或 LVARCHAR 列，但该字符串太长。

-1280 Library API incompatibility found in libgen.so.

The libgen.so shared library compiled with your client application is incompatible with the version in the $GBS_HOME/lib directory.

Recompile your application with GBS_HOME set to the path of the new libgen.so shared library.

客户端应用程序使用编译的 libgen.so 共享库与 $GBS_HOME/lib 目录中的版本不兼容。

请将 GBS_HOME 设置为新的 libos.so 共享库的路径，重新编译您的应用程序。

-1281 Library API incompatibility found in libos.so.

The libos.so shared library compiled with your client application is incompatible with the version in the $GBS_HOME/lib directory.

Recompile your application with GBS_HOME set to the path of the new libos.so shared library.

客户端应用程序使用编译的 libos.so 共享库与 $GBS_HOME/lib 目录中的版本不兼容。

请将 GBS_HOME 设置为新的 libos.so 共享库的路径，重新编译您的应用程序。

-1282 Library API incompatibility found in libsql.so.

The libsql.so shared library compiled with your client application is incompatible with the version in the $GBS_HOME/lib directory.

Recompile your application with GBS_HOME set to the path of the new libsql.so shared library.

客户端应用程序使用编译的 libsql.so 共享库与 $GBS_HOME/lib 目录中的版本不兼容。

请将 GBS_HOME 设置为新的 libsql.so 共享库的路径，重新编译您的应用程序。

-1283 Library API incompatibility found in libgls.so.

The libgls.so shared library compiled with your client application is incompatible with the version in the $GBS_HOME/lib directory.

Recompile your application with GBS_HOME set to the path of the new libgls.so shared library.

客户端应用程序使用编译的 libgls.so 共享库与 $GBS_HOME/lib 目录中的版本不兼容。

请将 GBS_HOME 设置为新的 libgls.so 共享库的路径，重新编译您的应用程序。

-1284 Value will not fit in a BIGINT or an INT8.

The BIGINT or BIGSERIAL or INT8 or SERIAL8 data type can accept numbers with absolute values from 0 through 9,223,372,036,854,775,807 (plus or minus (2 to the 63rd power) - 1).

BIGINT 或 BIGSERIAL 或 INT 8或 SERIAL8 数据类型可接受绝对值从 0 到 9,223,372,036,854,775,807（加号或减号（2 的 63 次方）-1）的绝对值。

To store numbers that are outside this range, redefine the column or variable to use the DECIMAL data type. For more information on valid ranges of data types, see the GBase 8s Guide to SQL: Reference.

要存储超出此范围的数字，请重新定义列或变量以使用 DECIMAL 数据类型。

有关数据类型的有效范围的更多信息，请参阅“GBase 8s SQL 指南：参考”。

-1285 Internal error: data type unknown.

If this internal error recurs, please note all circumstances and contact GBase Technical Support.

如果此内部错误再次出现，请注意所有情况并联系 GBase 技术支持。

-1301 This value is not among the valid possibilities.

A list or range of acceptable values has been established for this column (via an INCLUDE attribute in the form-specification file). You must enter a value within the acceptable range.

已经为该列建立了可接受值的列表或范围（通过格式规范文件中的 INCLUDE 属性）。

您必须输入一个可接受的范围内的值。

-1302 The two entries were not the same. Try again.

To guard against typographical errors, this field has been designated VERIFY (in the form-specification file). You must enter the value in this field twice, identically. Carefully reenter the data.

Alternatively, you can cancel the form entry with the Interrupt key(usually CTRL-C, but see the operating instructions that the program author supplied).

为防止排版错误，该字段被指定为 VERIFY（在表格规范文件中）。您必须两次都使用相同的方式在此字段中输入值。小心重新输入数据。或者，可以使用中断键（通常是 CTRL-C ）取消表单条目，但请参阅开发者提供的该程序的操作说明）。

-1303 You cannot use this editing feature because a picture exists.

This field is defined (in the form-specification file) with a PICTURE attribute to specify its format. You cannot use certain editing keys(for example, CTRL-A, CTRL-D, and CTRL-X) while you are editing such a field. Use only printable characters and backspace to enter the value.

为这个字段定义了 PICTURE 属性（在 form-specification 文件中）来指定它的格式。

在编辑这样的字段时，您不能使用某些编辑键（例如，CTRL-A、CTRL-D 和 CTRL-X）。

只能使用可打印的字符和退格键输入值。

-1304 Error in field.

您在此字段中输入的值不能存储在要接收它的程序变量中。例如，应用程序提供整型变量，但是您输入了一个十进制数，或者输入的字符串超出了应用程序定义的长度。请注意所有情况，然后与编写该应用程序的人员讨论此问题。

-1305 This field requires an entered value.

The cursor is in a form field that has been designated REQUIRED. You must enter some value before the cursor can move to another field. To enter a null value, type any printable character and then backspace.

Alternatively, you can cancel the form entry with the Interrupt key(usually CTRL-C, but see the operating instructions that the program author supplied).

光标位于已被指定为 REQUIRED 的表单域中。在光标移动到另一个字段之前，必须输入值。

要输入空值，输入任何可打印的字符，然后退格。或者，您可以使用中断键（通常是 CTRL-C，但请参阅程序作者提供的操作说明）取消表单条目。

-1306 Type again for verification.

The cursor is in a form field that has been designated VERIFY. You must enter the value twice, identically, before the cursor can move to another field. This procedure helps to ensure that no typographical errors occur during data entry. Alternatively, you can cancel the form entry with the Interrupt key (usually CTRL-C, but see the operating instructions that the program author supplied).

光标位于已被指定为 VERIFY 的表单域中。在光标移动到另一个字段之前，必须以相同的方式输入两次值。此过程有助于确保在数据输入过程中不会发生印刷错误。或者，您可以使用中断键（通常是CTRL-C，但请参阅程序作者提供的操作说明）取消表单条目。

-1307 Cannot insert another row - the input array is full.

您正在将数据输入到程序中由程序变量数组表示的记录数组中。该数组现在已满;没有空间可以存储另一条记录。请按 ACCEPT 键（通常是 ESCAPE，但请参阅程序作者提供的操作说明）处理您输入的记录。

-1308 Cannot delete row - it has no data.

You pressed the Delete Row function key (usually F2, but see the operating instructions that the program author supplied) in an empty row. Nothing was deleted.

您按下了 Delete Row 功能键（通常为 F2，但请参阅程序作者提供的操作说明）。

但没有数据被删除。

-1309 There are no more rows in the direction you are going.

You are attempting to scroll an array of records farther than it can go, either scrolling up at the top or scrolling down at the bottom of the array. Further attempts will have the same result.

您正在尝试滚动到超出记录数组的位置。无论是在顶部滚动还是在数组底部向下滚动。进一步的尝试都会得到相同的结果。

-1310 Exiting the current function without executing a RETURN statement.

The current function does not return void but is about to exit without executing a RETURN statement.

当前函数不返回 void，但即将退出而不执行 RETURN 语句。

-1312 FORMS statement error number number.

A problem exists with a screen form. Look up error number in this document. Consider it in relation to the current statement.

屏幕表单存在问题。在本文档中查找错误编号。考虑它与当前语句的关系。

-1313 SQL statement error number number.

The current statement calls on the database server that detected an error and returned an error code number. Look up number in this document. Also look for other error messages.

数据库服务器调用的当前语句检测到一个错误，并返回一个错误代码号。

请在该文件中查找错误编号和其他错误消息。

-1314 Program stopped at statement, line number line.

At the indicated point in the program, an error was detected. Look for other error messages that give details of the error. Use the numbers in this message to locate the error in the program source file.

在程序的指定位置检测到错误。查找提供错误详细信息的其他错误消息。使用此消息中的错误编号在程序源文件中定位错误。

-1315 4GL run-time error number number.

The program stopped because an error was detected. Look up error code number in this document. Also look for other error messages for more details.

该程序因检测到错误而停止。在本文档中查找错误代码编号。有关更多详细信息，请查看其他错误消息。

-1316 ISAM error number number.

The current statement called on the database server, which detected an error (probably reported in a display of error -1313). This message contains additional detail on the cause of the error. Look up number in this document.

在数据库服务器上调用的当前语句检测到一个错误（可能在显示错误 -1313 时报告）。

此消息包含导致此错误的原因的详细信息。请在该文件中查找该错误代码编号。

-1317 A numeric conversion error has occurred due to incompatibility between a calling program and its function parameters or between a variable and its assigned expression.

4GL converts between one data type and another automatically whenever it can do so without losing information. In the current statement, it could not do so. Look first for function calls, and inspect the values that are passed as parameters. Check that the values that are passed agree in type with the parameters as they are defined in the function bodies. (An example of such an error would be calling a function fun("X") when within the function its parameter was defined as an integer.) If the statement is a LET statement, check that the value that is computed on the right can be accommodated in the variable that is named on the left.

4GL 会在一种数据类型和另一种数据类型之间自动转换，而不会丢失信息。但在当前语句中，它没有这样做。首先检查函数调用，检查作为参数传递的值。检查传入的值是否与函数体中定义的参数类型一致。（这种错误的可能是因为在函数内部调用一个函数 fun("X")，它的参数被定义为一个整数）。如果该语句是 LET 语句，请检查在右边计算的值是否可以存储在左侧命名的变量中。

-1318 A parameter count mismatch has occurred between the calling function and the called function.

Either too many or too few parameters were given in the call to the function. The call is probably in a different source module from the called functions. Inspect the definition of the function, and check all places where it is called to ensure that they use the number of parameters that it declares.

在调用函数时给出的参数太多或太少。该调用可能位于与被调用函数不同的源模块中。

检查函数的定义，并检查它所调用的所有地方，以确保它们使用了它声明的参数量。

-1319 The 4GL program has run out of runtime data space memory.

You must reduce the data space that the program requires. Review the size of large character variables and the dimensions of arrays. You might need to split the program into separate programs that load separately, if that is possible.

您必须减少程序所需的数据空间。请查看大字符变量的大小和数组的维数。

如果可能的话，可能需要将程序拆分为单独加载的独立程序。

-1320 A function has not returned the correct number of values expected by the calling function.

If the function was invoked as part of an expression, then it returned more than one value. If a CALL invoked it, the number of expressions that follow the RETURN statement (in the function) was different from the number of variables that are listed in the RETURNING clause (in the CALL statement).

如果函数作为表达式的一部分被调用，那么它返回多个值。如果 CALL 调用它，则 RETURN 语句（在该函数中）后面的表达式数与 RETURNING 子句（在 CALL 语句中）中列出的变量数不同。

Check that the correct function was called. Review the logic of the function, especially its RETURN statements, to ensure that it always returns the expected number of values.

请检查是否调用了正确的函数。查看函数的逻辑，特别是 RETURN 语句，以确保它始终返回预期的值数。

-1321 A validation error has occurred as a result of the VALIDATE command.

The VALIDATE statement tests the current value of variables against rules that are stored in the syscolval table. It has detected a mismatch. Ordinarily, the program would use the WHENEVER statement to trap this error and display or correct the erroneous values. Inspect the VALIDATE statement to see which variables were being tested and find out why they were wrong.

VALIDATE 语句根据存储在 syscolval 表中的规则测试变量的当前值。它检测到不匹配。

通常，程序使用 WHENEVER 语句捕获该错误并显示或纠正错误的值。请检查 VALIDATE语句，查看哪些变量正在进行测试，并找出它们错误的原因。

-1322 A report output file cannot be opened.

The file that the REPORT TO statement specifies cannot be opened. Check that your account has permission to write such a file, that the disk is not full, and that you have not exceeded some limit on the number of open files.

REPORT TO 语句指定的文件无法打开。检查您的账户是否具有对该文件的写入权限，磁盘是否已满，并且打开文件的数量没有超出限制。

-1323 A report output pipe cannot be opened.

The pipe that the REPORT TO PIPE statement specifies could not be started. Check that all programs that are named in it exist and are accessible from your execution path. Also look for operating-system messages that might give more specific errors.

REPORT TO PIPE 语句指定的管道无法启动。检查所有在其中命名的程序是否存在并可从执行路径访问。同时请查找可能会导致更具体错误的操作系统消息。

-1324 A report output file cannot be written to.

The file that the REPORT TO statement specifies was opened, but an error occurred while writing to it. Possibly the disk is full. Look for operating- system messages that might give more information.

REPORT TO 语句指定的文件已打开，但写入该文件时发生错误。可能是因为磁盘已满。

请查看可能提供更多信息的操作系统消息。

-1326 An array variable has been referenced outside of its specified dimensions.

The subscript expression for an array has produced a number that is either less than one or greater than the number of elements in the array. Review the program logic that leads up to this statement to determine how the error was made.

数组的下标表达式产生的数字要么小于 1，要么大于数组中元素的数量。请查看程序逻辑，确定错误是如何发生的。

-1327 An insert statement could not be prepared for inserting rows into a temporary table used for a report.

Within the report function, 4GL generated an SQL statement to save rows into a temporary table. The dynamic preparation of the statement (see the reference material on the PREPARE statement) produced an error.

Probably the database tables are not defined now, at execution time, as they were when the program was compiled. Either the database has been changed, or the program has selected a different database than the one that was current during compilation. Possibly the database administrator has revoked SELECT privilege from you for one or more of the tables that the report uses. Look for other error messages that might give more details.

在报告功能中，4GL 生成一条 SQL 语句将行保存到临时表中。该语句的动态准备（请参阅 PREPARE 语句中的参考资料）会产生错误。现在，在执行时数据库表可能不会像编译程序时那样定义。数据库已被更改，或者程序选择了与编译期间当前数据库不同的数据库。可能数据库管理员已经撤销了您对该报告使用的一个或多个表的 SELECT 权限。请查看可能提供更多详细信息的其他错误消息。

-1328 A temporary table needed for a report could not be created in the selected database. The user must have permission to create tables in the selected database.

Within the report definition, 4GL generated an SQL statement to save rows into a temporary table, but the temporary table could not be created. Probably no disk space is left in the database, or you already have a table in your current database with the same name as the temporary table that the report definition is attempting to create as a sorting table.

在报告定义中，4GL 生成一条 SQL 语句将行保存到临时表中，但临时表无法创建。数据库中可能没有多余磁盘空间，或者当前的数据库中已经有一个表，其名称与报表定义尝试创建作为排序表的临时表相同。

Another possible cause is that the report name is too long. It should be 16 characters or fewer if your database server allows only table names up to 18 characters long, to leave room for the "t_" prefix.

另一个可能的原因是报告名称太长。如果数据库服务器只允许长达 18 个字符的表名，则应为 16 个字符或更少，为“t_”前缀留出空间。

The sorting table is named "t_reportname". For example, a report named"order_rpt" would name its sorting table "t_order_rpt". Users should avoid beginning table names with "t_".

排序表被命名为“t_reportname”。例如，名为“order_rpt”的报告会将其排序表命名为“t_order_rpt”。

用户应避免使用“t_”开始表名。

Another possible cause of this error with some database servers is that you have exceeded an operating-system limit on open files.

某些数据库服务器出现此错误的另一个可能原因是，您已超出操作系统对打开文件的限制。

Look for other error messages that might give more details.

请查看可能提供更多详细信息的其他错误消息。

-1329 A database index could not be created for a temporary database table needed for a report.

Within the report definition, 4GL generated SQL statements to save rows into a temporary table. However, an index could not be created on the temporary table. Probably an index with the same name already exists in the database. (The sorting index is named "i_reportname"; for example,"i_order_rpt".) Possibly no disk space is available in the file system or dbspace. Another possibility with some database servers is that you have exceeded an operating-system limit on open files. Look for other error messages that might give more details.

在报告定义中，4GL 会生成 SQL 语句来将行保存到临时表中。但是，无法在临时表上创建索引。数据库中可能已经存在一个同名的索引。（排序索引名为“i_reportname”；例如，“i_order_rpt”。）文件系统或 dbspace 中可能没有可用的磁盘空间。某些数据库服务器出现此错误的另一个可能原因是，您已超出操作系统对打开文件的限制。请查找可能提供更多详细信息的其他错误消息。

-1330 A row could not be inserted into a temporary report table.

Within the report definition, 4GL generated SQL statements that would save rows into a temporary table. However, an error occurred while rows were being inserted. Probably no disk space is left in the database.

Look for other error messages that might give more details.

在报告定义中，4GL 会生成的 SQL 语句将行保存到临时表中。但是，插入行时发生错误。

数据库中可能没有磁盘空间。请查找可能提供更多详细信息的其他错误消息。

-1331 A row could not be fetched from a temporary report table.

Within the report definition, 4GL generated SQL statements to select rows from a temporary table. The table was built successfully but now an error occurred while rows were being retrieved from it. Almost the only possible cause is a hardware failure or an error in the database server. Check for operating-system messages that might give more details.

在报告定义中，4GL 生成了用于从临时表中选择行的 SQL 语句。该表已创建成功，但现在从中检索行时发生错误。唯一可能的原因是数据库服务器中的硬件故障或错误。请检查可能提供更多信息的操作系统消息。

-1332 A character variable has referenced subscripts that are out of range.

In the current statement, a variable that is used in taking a substring of a character value contains a number less than one or a number greater than the size of the variable, or the first substring expression is larger than the second. Review the program logic that leads up to this statement to find the cause of the error.

在当前语句中，用于获取字符值子字符串的变量包含小于 1 的数字或大于变量大小的数字，或者第一个子字符串表达式大于第二个。请查看程序逻辑，找出错误的原因。

-1333 Strings of length > 512 cannot be returned from function calls.

The current RETURN statement contains an expression that evaluates to a character string longer than 512 characters. This situation is not supported. Review the logic of the function, and modify it so that it does not return such a long character value. You can assign a longer string to a global variable.

当前 RETURN 语句包含一个表达式，其计算结果为长度超过 512 个字符的字符串。这种情况是不支持的。请检查函数的逻辑，并对其进行修改，使其不会返回如此长的字符值。您可以将更长的字符串分配给全局变量。

-1334 The 4GL program cannot allocate any more space for temporary string storage.

You should not see this message from a program that is compiled at a version later than Version 4.1; however, programs that are compiled by 4GL Version 4.1 and earlier must deal with this issue.

您不会在高于 V4.1 的版本编译的程序看到此消息；但是，由 4GL V4.1 及更早版本编译的程序必须处理此问题。

Temporary string storage is used while evaluating a character expression. It is allocated by a simple algorithm from a fixed-size buffer. Space in this buffer is not reclaimed until the last pending character expression is finished. Because most expressions complete immediately, the string buffer is normally emptied as fast as it is used.

在评估字符表达式时使用临时字符串存储。它由一个简单的算法从固定大小的缓冲区中分配。直到上一个挂起的字符表达式完成后，才会回收此缓冲区中的空间。因为大多数表达式会立即完成，所以字符串缓冲区通常会尽可能快地被清空。

However, when expressions involve function calls, expression evaluation is suspended during the function call. The buffer is not cleared until the function returns. For example, temporary space is used for the literal "###" and the result of the USING operator in the following statement:但是，当表达式涉及函数调用时，表达式评估在函数调用期间暂停。在函数返回结果之前，缓冲区不会被清除。例如，临时空间用于以下语句中的文字“###”和 USING 运算符的结果：LET charvar = numvar USING '###', myfunc()These pending values remain in the string buffer for the duration of the call to myfunc(). If the aggregate total of all temporary character values that are used during the evaluation of myfunc() and its sub-functions exceeds the buffer size, this error occurs.

这些挂起的值在调用 myfunc()期间一直保留在字符串缓冲区中。如果在评估 myfunc()及其子函数期间使用的所有临时字符值的总计超过了缓冲区大小，则会发生此错误。

You can usually prevent the error by isolating function calls in separate statements, as in the following example:通常可以通过在单独的语句中分别调用这些函数来防止错误，如下例所示：LET charvar = myfunc()LET charvar = numvar USING '###', charvar clipped The string buffer is free during the call to myfunc() in the first statement and free again as soon as the second statement completes.

在第一条语句中调用 myfunc()期间，字符串缓冲区是空闲的，并在第二条语句完成后立即释放。

The short form of a WHEN clause in a CASE statement also creates a suspended character expression. In the following example, temporary string storage is tied up throughout the calls to func_A() and func_B().

CASE 语句中 WHEN 子句的简写形式也会创建一个暂停的字符表达式。在下面的例子中，在对 func_A()和 func_B()的调用中，临时字符串存储被绑定。

CASE charvar WHEN 'A' CALL func_A()WHEN 'B' CALL func_B()...

The longer form of the WHEN clause does not do this because evaluation of the character expression is completed before the function call begins.

长格式的 WHEN 子句则不会这样做，因为在函数调用开始之前它已经完成了对字符表达式的评估。

CASE WHEN charvar = 'A' CALL func_A()WHEN charvar = 'B' CALL func_B()Finally, a known error in some versions of 4GL Version 4.1 causes a spurious error of this type when the WORDWRAP clause appears in a PRINT statement. If the error recurs, note all circumstances and contact GBase Technical Support.

最后，当 WORDWRAP 子句出现在 PRINT 语句中时，某些版本的 4GL V4.1 中的已知错误会导致此类型的错误错误。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-1335 A report is accepting output or being finished before it has been started.

The program executed an OUTPUT TO REPORT or FINISH REPORT statement before it executed a START REPORT. Review the program logic that leads up to this statement to find the cause of the error.

该程序在执行 START REPORT 之前执行了 OUTPUT TO REPORT 或 FINISH REPORT 语句。

请查看导致本声明的程序逻辑，找出错误的原因。

-1336 Module name in the pcode file contains pcode version compile-version.

This program can run pcode version runner-version. Run the pcode compiler with the -V option to check the pcode version that it produces. Then recompile all modules of your program, and run it again.

The program runner or a customized runner must be the same software version as the program compiler. To check that the programs are at the same level, execute each with the -V option. That option displays their version numbers. When you determine that you are using compatible software, recompile your program.

程序的运行器或定制的运行程序必须与程序编译器具有相同的软件版本。请检查程序是否处于同一级别，请使用 -V 选项查询。该选项显示其版本号。当确定您正在使用兼容软件时，请重新编译程序。

-1337 The variable name has been redefined with a different type or length.

The variable that is shown is defined in the GLOBALS section of two or more modules, but it is defined differently in some modules than in others. Possibly modules were compiled at different times, with some change to the common GLOBALS file between. Possibly the variable is declared as a module variable in some module that does not include the GLOBALS file.

显示的变量在两个或多个模块的 GLOBALS 部分中定义，但在某些模块中定义的变量与其他模块中的不同。可能的模块是在不同的时间编译的，其间某些操作修改了 GLOBALS 文件。

可能在某些不包含 GLOBALS 文件的模块中声明该变量为模块变量。

-1338 The function name has not been defined in any module in the program.

The named function is called from at least one module of the program,but it is defined in none. If you are using the Programmer's Environment, possibly one module was not defined as part of a multimodule program. If you are working at the command line, possibly one or more compiled .4go modules were omitted when the program files were concatenated to form the .4gi file.

至少从程序的一个模块中调用了命名的函数，但它没有定义。如果您使用的是编程环境，可能有一个模块没有被定义为多模块程序的一部分。如果您在命令行中工作，当程序文件连接在一起形成 .4gi 文件时，可能会省略一个或多个已编译的 .4go 模块。

-1339 Global variable name cannot be found in the descriptor table.

This error indicates an internal problem in the runner. If the error recurs, note all circumstances and contact GBase Technical Support.

此错误表示运行程序内部存在问题。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-1340 The error log has not been started.

The program called the errorlog() function without first calling the startlog() function. Review the program logic to find out the cause of this error.

该程序在不调用 startlog() 函数的情况下调用 errorlog()函数。请检查程序逻辑，并找出此错误的原因。

-1343 No help file specified.

This INPUT, PROMPT, or MENU statement contains a HELP help-number clause; however, no message file has been established. The OPTIONS HELP FILE statement establishes the message file, but the statement has not yet been executed. Review the program logic, and modify it to execute an OPTIONS statement with a HELP FILE clause before it is needed.

该 INPUT、PROMPT 或 MENU 语句包含一个 HELP 帮助号子句；但是，没有建立消息文件。

选项帮助文件语句建立消息文件，但该语句尚未执行。请查看程序逻辑，修改它以在需要之前使用 HELP FILE 子句执行 OPTIONS 语句。

-1344 GBase 8s Run Time Facility.

No current GBase 8s product displays this message.

当前 GBase 8s 产品不会显示此消息。

-1345 Undefined opcode.

The p-code file for the program (whose file suffix is .4go) has become corrupted. Recompile the whole program, and run it again. If the same error occurs, check that you are running the identical version of both the p-code compiler and the p-code runner. If the error recurs,note all circumstances and contact GBase Technical Support.

该程序的 p-code 文件（其文件后缀为 .4go）已损坏。重新编译整个程序，然后重新运行它。如果发生相同的错误，请检查您是否运行了相同版本的 p-code 编译器和 p-code 运行器。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-1346 Number is too large for a DECIMAL data type.

The DECIMAL data type accommodates numbers from 10 to the -130th power through 10 to the 124th power in absolute value. The precision (number of significant digits) varies from 1 to 32; however, the source of this error is not the length of the number but its magnitude.

DECIMAL 数据类型可容纳从 10 的 -130 次方到 10 的 124次方的绝对值。精度（有效位数）从 1 到 32 不等；然而，这个错误的来源不是数字的长度，而是数的大小。

-1347 Number is too small for a DECIMAL data type.

-1348 An attempt was made to divide by zero.

Zero cannot be a divisor. In some cases, this error arises because the divisor is a character value that does not convert properly to numeric.

零不能成为除数。在某些情况下，会出现此错误，因为除数是不能正确转换为数字的字符值。

-1349 Character to numeric conversion error.

A character value is being converted to numeric form for storage in a numeric column or variable. However, the character string cannot be interpreted as a number. It contains some characters other than white space, digits, a sign, a decimal, or the letter e, or else the parts are in the wrong order so that the number cannot be deciphered.

字符值正在转换为数值值以存储在数值列或变量中。但是，字符串不能被解释为数值。它包含除空格、数字、符号、小数或字母 e 以外的一些字符，或者部分顺序错误，因此无法破译该数值。

-1350 It is not possible to convert between the specified types.

The system will attempt any data conversion that makes sense. However,some conversions, such as INTERVAL to DATE, or DATETIME to MONEY, are not supported. Possibly you referenced the wrong variable or column.

Check that you have specified the data types that you intended and that you formatted literal representations of data values correctly.

系统将尝试任何有意义的数据转换。但是，不支持某些转换，例如 INTERVAL 到 DATE或 DATETIME 到 MONEY。可能您引用了错误的变量或列。请检查您是否指定了想要的数据类型，以及是否正确格式化了数据值的文字表示。

-1351 The function (or report) name has already been defined. Function and report cannot both have the same name.

Each function (or report, which is similar to a function) must have a unique name within the program. You must change either this use or the prior one.

每个函数（或与函数类似的报告）在程序中必须具有唯一的名称。您必须更改该用法或之前的用法。

-1352 name may not be used as both a function (or report) name and a variable name.

The name that is shown has been defined at least two ways. Names at the global or module level (function names, report names, and names of global or module variables) must be unique. Locate all the definitions of this name, and change all but one of them.

显示的名称至少有两种定义。全局或模块级别的名称（函数名称、报告名称和全局变量或模块变量的名称）必须是唯一的。找到这个名称的所有定义，并且改变除了其中一个以外的所有定义。

-1353 Use '!' to edit TEXT and BYTE fields.

The built-in form editor cannot deal with TEXT or BYTE columns.

However, you can designate an external program that can display or edit a value from a TEXT or BYTE column. To call the external program for any field, put the cursor in that field, and key the exclamation mark(!) character. If an external program has been defined (with the PROGRAM attribute in the form specification), it will be started. In a TEXT field, if no external program is specified in the form, the program that the DBEDIT environment variable names will be started.

内置的表单编辑器无法处理 TEXT 或 BYTE 列。但是，您可以设计一个可以显示或编辑TEXT 或 BYTE 列中的值的外部程序。要为任何字段调用外部程序，请将光标放在该字段中，然后键入感叹号(!)字符。如果已经定义了外部程序（在表格说明中使用 PROGRAM 熟悉），则会启动该程序。在 TEXT 字段中，如果在表单中没有指定外部程序，则会启动 DBEDIT 环境变量名称的程序。

-1355 Cannot build temporary file.

A TEXT or BYTE variable has been located in a temporary file using the LOCATE statement. The current statement assigns a value into that variable, so 4GL attempted to create the temporary file, but an error occurred. Possibly no disk space is available, or your account does not have permission to create a temporary file. 4GL creates a temporary file in the directory that the DBTEMP environment variable specifies.

Look for operating-system error messages that might give more information. Check the value of DBTEMP.

已使用 LOCATE 语句将 TEXT 或 BYTE 变量定位在临时文件中。当前语句为该变量赋值，因此 4GL 试图创建临时文件，但发生错误。可能没有可用的磁盘空间，或者您的账户没有创建临时文件的权限。4GL 在 DBTEMP 环境变量指定的目录中创建一个临时文件。查找可能提供更多信息的操作系统错误消息。检查 DBTEMP 的值。

-1356 Write error on temporary file filename.

The operating system signalled an error during output to a temporary file in which a TEXT or BYTE variable was being saved. Possibly the disk is full, or a hardware failure occurred. For more information,look for operating-system messages.

操作系统在输出到临时文件时发出错误信号，其中保存了 TEXT 或 BYTE 变量。

磁盘可能已满，或发生硬件故障。有关更多信息，请查看操作系统消息。

-1357 Read error on temporary file filename.

The operating system signalled an error during input from a temporary file in which a TEXT or BYTE variable was saved. Possibly a hardware failure occurred. For more information, look for operating-system messages.

从保存 TEXT 或 BYTE 变量的临时文件输入时，操作系统发出错误信号。可能发生了硬件故障。

有关更多信息，请查看操作系统消息。

-1358 Write error on TEXT or BYTE file filename.

操作系统在输出到临时文件时发出错误信号，其中保存了 TEXT 或 BYTE 变量。

磁盘可能已满，或发生硬件故障。有关更多信息，请查看操作系统消息。

-1359 Read error on TEXT or BYTE file filename.

操作系统在输出到临时文件时发出错误信号，其中保存了 TEXT 或 BYTE 变量。

磁盘可能已满，或发生硬件故障。有关更多信息，请查看操作系统消息。

-1360 No PROGRAM= clause for this field.

You pressed the exclamation-mark key (!) while the cursor was in a TEXT or BYTE field. However, no external program has been designated for this field (with the PROGRAM attribute in the form-specification file).

If this field is a TEXT field, you can set the DBEDIT environment variable before you start the program to specify a text editor.

当光标位于 TEXT 或 BYTE 字段时，您按了感叹号键（！）。但是，没有为此字段（在表格规范文件中具有 PROGRAM 属性）指定外部程序。如果此字段是 TEXT 字段，则可以在启动程序指定文本编辑器之前设置 DBEDIT 环境变量。

-1361 Illegal TEXT or BYTE file name. Null names are not permitted.

The BYTE or TEXT variable has been located in a file using the 4GL statement LOCATE. However, the filename that is given for the variable is a null string. Because the file does not exist, 4GL cannot do anything with it.

已经使用 4GL 语句 LOCATE 在文件中定位 BYTE 或 TEXT 变量。但是，变量的文件名是空字符串。由于该文件不存在，4GL无法对其执行任何操作。

-1362 4GL runtime stack violation.

The program attempted to access outside the boundaries of the stack. If the error recurs, note all circumstances and contact GBase Technical Support.

该程序试图访问堆栈的边界外的部分。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-1363 A fatal internal error has occurred - Application Terminating.

The program attempted to access outside the memory that belongs to the application. If the error recurs, note all circumstances and contact GBase Technical Support.

该程序试图访问属于该应用程序的内存之外的部分。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-1364 Error recovery setup failed - Application Terminating.

The mechanism that allows the application to catch and handle internal errors could not complete its actions. Return to DOS, and restart Windows.

允许应用程序捕获并处理内部错误的机制无法完成其操作。请返回到 DOS，并重新启动 Windows。

-1365 Application appname not found.

The Application Launcher, fglaunch, did not find the requested application.

应用程序启动器 fglaunch 没有找到请求的应用程序。

-1366 Unable to load application appname.

The Application Launcher, fglaunch, could not load the requested application. The DLL does not have the required NewEra entry points, so it must not be a NewEra DLL. Check to see if the NewEra DLL has the same name as an existing system DLL.

应用程序启动器 fglaunch 无法加载请求的应用程序。该 DLL 没有所需的 NewEra 入口点，因此它不能是 NewEra DLL。请检查 NewEra DLL 否与现有系统 DLL 具有相同的名称。

-1367 DLL dllname is not a resource DLL - Application Terminating.

The program options for the Application Launcher, fglaunch, specified that the DLL dllname included resources, but no resources were found,应用程序启动程序 fglaunch 的程序选项指定 DLL dllname 包含资源，但未找到资。

-1371 The field fieldname does not exist in the current form.

The indicated field name has been given to the NEXT FIELD statement or to the pf_nxfield() function, but it is not defined in the current form. A common error is to confuse the tag name, which is used in the screen layout and to the left of the equal sign in the ATTRIBUTES section, with the field name, which is the column name used to the right of the equal sign in the ATTRIBUTES section. Use the latter when you refer to fields.

指定的字段名称已被传递到 NEXT FIELD 语句或 pf_nxfield()函数，但未在当前表单中定义。一个常见的错误是将在屏幕布局中使用的标记名称和 ATTRIBUTES 部分中等号左侧的标记名称与字段名称混淆了，字段名称是在等号右边使用的列名称 ATTRIBUTES 部分。当您引用字段时请使用后者。

-1372 The number entered is too large to fit in the decimal or money variable.

Probably no current GBase 8s product returns this message. If it appears, refer to the explanation of error -1226. If the error recurs,note all circumstances and contact GBase Technical Support.

目前 GBase 8s 产品可能不会返回此消息。如果出现，请参阅错误 -1226的解释。

如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-1373 The field fieldname is not in the list of fields in the CONSTRUCT/INPUT statement.

The built-in function get_fldbuf() or field_touched() has been called with the field name shown. However, input from that field was not requested in this CONSTRUCT or INPUT statement. As a result, the function cannot return any useful value. Review all uses of these functions, and compare them to the list of fields at the beginning of the statement.

内置的函数 get_fldbuf()或 field_touched()已经被调用，并显示了字段名称。但是，在此 CONSTRUCT 或 INPUT 语句中未请求来自该字段的输入。因此，函数无法返回任何有用的值。查看这些函数的所有用法，并将它们与语句开头的字段列表进行比较。

-1374 SQL character truncation or transaction warning.

The program set WHENEVER WARNING STOP, and a warning condition arose.

If the statement involved is a DATABASE statement, the condition is that the database that was just opened uses a transaction log. On any other statement, the condition is that a character value from the database had to be truncated to fit in its destination.

程序设置 WHENEVER WARNING STOP，出现警告状况。如果涉及的语句是 DATABASE 语句，则条件是刚刚打开的数据库使用的事务日志。在任何其他语句中，条件是必须将数据库中的字符值截断以适合其目标。

-1375 SQL NULL value in aggregate or mode ANSI database warning.

The program set WHENEVER WARNING STOP, and a warning condition arose.

If the statement that is involved is a DATABASE statement, the condition is that the database that was just opened is ANSI compliant.

On any other statement, the condition is that a null value has been used in the computation of an aggregate value.

程序设置 WHENEVER WARNING STOP，并出现警告条件。如果涉及的语句是 DATABASE 语句，则条件是刚刚打开的数据库符合 ANSI 标准。在任何其他语句中，条件是在计算平均值时使用了空值。

-1376 SQL, database server, or program variable mismatch warning.

The program set WHENEVER WARNING STOP, and a warning condition arose.

If the statement that is involved is a DATABASE or CREATE DATABASE statement, the condition is that the database server opened the database. On any other statement, the condition is that a SELECT statement returned more values than there were program variables to contain them.

程序设置 WHENEVER WARNING STOP，并出现警告条件。如果涉及的语句是 DATABASE 或CREATE DATABASE 语句，则条件是数据库服务器已打开数据库。在任何其他语句中，条件是 SELECT 语句返回的值比程序包含的变量多。

-1377 SQL float-to-decimal conversion warning.

The program set WHENEVER WARNING STOP, and a warning condition arose.

The condition is that in the database that was just opened, the database server will use the DECIMAL data type for FLOAT values.

程序设置 WHENEVER WARNING STOP，并出现警告条件。条件是在刚打开的数据库中，数据库服务器将为 FLOAT 值使用 DECIMAL 数据类型。

-1378 SQL non-ANSI extension warning.

A database operation was performed that is not part of ANSI SQL,although the current database is ANSI compliant. This message is informational only.

虽然当前数据库符合 ANSI 标准，但是数据库操作不是 ANSI SQL 的一部分。此消息仅供参考。

-1379 Report functions may not be called directly. Use the OUTPUT TO REPORT statement.

A report function has been entered as a result of a CALL statement.

Report functions can only be executed using the START REPORT, FINISH REPORT, and OUTPUT TO REPORT statements. Review the program. Look for places where the report function name is called like a normal function,and change them. If you want to use some of the code in the report function as a subroutine, place it in a separate subroutine, and call it from the report function and other places.

报表函数已经作为 CALL 语句的结果输入。报表函数只能使用 START REPORT、FINISH REPORT 和 UTPUT TO REPORT 语句执行。查看该程序。查找报表函数名称同普通函数一样被调用的地方，并对其进行更改。如果要将报表函数中的某些代码用作子例程，请将其放置在单独的子例程中，并从报表函数和其他位置调用它。

-1380 Only character expressions may be CLIPPED.

You cannot CLIP a noncharacter expression.

不能 CLIP 一个非字符表达式。

-1381 Cannot execute another runner when debugging.

An instance of the 4GL runner is currently executing. While you are debugging, you cannot launch additional instances of the runner through a RUN command, the RUN accelerator button, or directly from Windows. To launch a new instance of the runner, first quit the currently running 4GL application.

正在执行一个 4GL 运行器的实例。在调试时，无法通过 RUN 命令、RUN 加速按钮或直接从 Windows 启动运行器的其他实例。要启动运行器的新实例，首先退出当前正在运行的 4GL 应用程序。

-1390 The class "class" has not been defined in any module in the program.

The named class has been declared, and it has been used, but it has never been defined. It must be defined at the definition of the first member function of that class.

已声明并使用该命名的类，但该类从未被定义。它必须在该类的第一个成员函数的定义中定义。

-1391 Invalid class specified in AS clause.

The class specified in an AS clause of a NEW or COPY operation must be derived from the stated class.

在 NEW 或 COPY 操作的 AS 子句中指定的类必须来自所声明的类。

-1392 Cannot use a NULL object.

In the p-code runner, an attempt was made to dereference a NULL object. Perhaps the program has defined an object, then tried to invoke a member function of the object before creating it through!copy() or !derive().

在 p-code 运行器中，试图取消引用 NULL 对象。也许程序定义了一个对象，然后在通过 !copy() 或 !derive() 创建它之前尝试调用对象的成员函数。

-1393 The class class has already been defined.

The program attempted to define a class for a second time.

该程序试图再次定义一个类。

-1394 Invalid ixRow object argument for built-in function.

An ixRow argument is expected as the first argument for the built-in functions UNPACKROW() and PACKROWINTO().

预计 ixRow 参数将作为内置函数 UNPACKROW()和 PACKROWINTO()的第一个参数。

-1396 A report PRINT FILE source file cannot be opened for reading.

The file that is named in a PRINT FILE statement cannot be opened.

Review the file name. If it is not in the current directory, you must specify a full path. If the file is specified correctly, check that it exists and that your account has file permissions to read it. Look for operating-system error messages that might give more details.

在 PRINT FILE 语句中命名的文件无法打开。请检查文件名。如果它不在当前目录中，则必须指定完整路径。如果文件指定正确，请检查它是否存在，并确保您的账户具有文件权限以便读取它。请查看可能提供更多详细信息的操作系统错误消息。

-1778 The security subsystem could not be initialized for this command.

Ensure that this account has sufficient privileges.

确保此账户具有足够的权限。

-1779 This command can be executed only by members of the Gbasedbt-admin group.

Log in with a user account that belongs to the Gbasedbt-admin group, or ask the Windows administrator to add your user account to the Gbasedbt-admin group. Then try the procedure again.

使用属于 Gbasedbt-admin 组的用户账户登录，或要求 Windows 管理员将您的用户账户添加到Gbasedbt-admin 组。然后再次尝试该程序。

-1780 The database server can be started only by user GBase 8s.

You must be a member of the Gbasedbt-admin group to start the database server. Log in with a user account that belongs to the Gbasedbt-admin group, or ask the Windows administrator to add your user account to the Gbasedbt-admin group.

您必须是 Gbasedbt-admin 组的成员才能启动数据库服务器。使用属于Gbasedbt-admin组的用户账户登录，或要求 Windows 管理员将您的用户账户添加到 Gbasedbt-admin 组。

-1781 The database server could not retrieve the account information for this user account.

The account information is missing or invalid. Run User Manager to check the validity of this account.

账户信息丢失或无效。运行用户管理器来检查此账户的有效性。

-1782 The database server cannot validate this user.

The user does not have a valid account or password on the computer where the database server is running. You must create a user account and password for this user.

用户在运行数据库服务器的计算机上没有有效的账户或密码。您必须为此用户创建一个用户账户和密码。

-1783 UnSetup will carry out these actions:UnSetup 将执行这些操作* Remove the groupname group and the username user accounts移除 groupname 组和 username 用户账户* Remove the servicename service移除 servicename 服务器* Remove the branch Software\branchname\keyname\ from the registry从注册表移除该分支 Software\branchname\keyname\Do you also want to remove all GBase 8s product files and directories?(Y,N,Q)您需要删除所有的 GBase 8s 产品文件和目录么？（Y、N、Q）-1784 The database server could not initialize the security subsystem.

The database server runs under the user GBase 8s account, which must have the following privileges:* Log on as a service* Create a token object* Act as part of the operating system* Belong to the Gbasedbt-admin group To verify that user GBase 8s has these rights, access the User Manager,and use the Policies/User Rights dialog box.

数据库服务器在用户 Infromix 账户下运行，该账户必须具有以下权限：*作为服务登录*创建一个令牌对象*作为操作系统的一部分*属于 Gbasedbt-admin 组要验证用户 Gbasedbt 是否具有这些权限，请访问用户管理器，然后使用“策略/用户权限”对话框。

-1785 pathname\buildsmi.ext This message refers to the output of buildsmi.bat. For Windows, look into the file %GBS_HOME%\etc\buildsmi.out if "Error building sysmaster" appears in the online.log file.

此消息引用了 buildsmi.bat 的输出。对于 Windows，如果在 online.log 文件中出现“Error building sysmaster”，请查看文件％GBS_HOME％\etc\buildsmi.out。

-1786 The command line option specified in the Control Panel/Services/Startup dialog was -i.

The parameter that was specified in the Control Panel/Services/Startup dialog box was -i, which causes the database server to initialize the root dbspace, destroying any information that it currently contains.

When the database server runs as a service under Windows, it does not prompt you to confirm the parameters that you have specified. If you are sure that you want to initialize the root dbspace, specify the parameters as -iy instead.

在控制面板/服务/启动对话框中指定参数的是 -i，这会导致数据库服务器初始化 root dbspace，销毁它当前包含的任何信息。当数据库服务器在 Windows 下作为服务运行时，它不会提示您确认已指定的参数。如果您确定要初始化 root dbspace,请指定参数为 -iy 。

-1787 The database server detected a mismatch in the configuration file.

Mirror chunk pathname = pathname, Offset = offset K, Size = size K.

Check the actual file size of the chunk against the size that is specified for the mirror chunk in the ONCONFIG file.

根据为 ONCONFIG 文件中镜像 chunk 指定的大小检查 chunk 的实际文件大小。

-1788 The audit configuration-file pathname is too long. Its pathname should contain at most maxnum characters.

The maximum number of characters, or maxnum, is 128.

最大字符数或 maxnum 为 128 。

-1789 The database server could not get account information for user username.

Check to see that the user account exists and is valid.

检查用户账户是否存在并且有效。

-1790 The database server could not be started.

Ensure that the account used to start the database server is a member of the Gbasedbt-admin group.

确保用于启动数据库服务器的账户是 Gbasedbt-admin 组的成员。

-1791 The database server encountered a fatal error while initializing shared memory.

Look for the cause of this error in %GBS_HOME%\online.log.

请在 %GBS_HOME%\online.log 中查找此错误的原因。

-1792 The database server cannot access %GBS_HOME%\dbssodir or%GBS_HOME%\aaodir.

Check access to the path segments that lead to %GBS_HOME%\dbssodir and %GBS_HOME%\aaodir. If %GBS_HOME% is on a network drive, make sure that the oninit process privileges are not altered. In addition,make sure that the AAO and DBSSO group names are valid in the registry.

检查到％GBS_HOME％\dbssodir 和％GBS_HOME％\aaodir 的路径段的访问权限。

如果％GBS_HOME％位于网络驱动器上，请确保 oninit 进程权限未被更改。另外，请确保 AAO 和 DBSSO 组名在注册表中有效。

-1793 The database server could not open the chunk chunkname. The system error value returned was errno.

Ensure that this chunk exists and has the correct permissions for access.

确保该 chunk 存在并具有正确的访问权限。

-1794 The primary chunk chunkname containing the root dbspace is invalid. It needs to be re-initialized.

The chunk that contains the root dbspace is corrupt or out of date. If you have backed up your database server, you can perform a full-system restore to restore the root dbspace. If you have not backed up your database server, you will need to reinitialize the root dbspace by using the -iy parameters when you start the database server.

包含 root dbspace 的 chunk 已损坏或已过时。如果已备份数据库服务器，则可以执行全系统还原来还原 root dbspace。如果尚未备份数据库服务器，则需要在启动数据库服务器时使用 -iy 参数重新初始化 root dbspace。

Warning: Starting the database server with the parameters -iy reinitializes the root dbspace and effectively destroys all existing data. You will no longer be able to access existing databases unless you subsequently perform a full system restore. Do not reinitialize the root dbspace unless you are certain that you want to do so.

警告：使用参数 -iy 启动数据库服务器重新初始化 root dbspace 并有效销毁所有现有数据。除非您随后执行完整的系统还原，否则将无法再访问现有的数据库。除非确定要这样做，否则不要重新初始化 root dbspace 。

-1795 The number of chunks specified in shared memory, num_chunks, is too large.

The maximum allowable number with the current configuration is num_chunks. Specify larger chunk sizes, and reduce the number of chunks.

当前配置的最大允许数量为 num_chunks。指定较大的 chunk 大小，减少 chunk 的数量。

-1796 The database server detected a mismatch in the registry subkey data for MIRRORPATH. The data retrieved for MIRRORPATH was pathname.

The root dbspace has not been mirrored. To add mirroring, use onspaces or onmonitor.

root dbspace 未被镜像。要添加镜像，请使用 onspaces 或 onmonitor。

-1797 The root dbspace is not large enough for the specified configuration.

The actual size is sizenum, and the required size is sizenum.

The root dbspace will not fit on the specified drive. Free the amount of space that is needed on the specified drive, or change the ROOTPATH configuration parameter to specify a different drive with more space available. Then restart the database server with the -iy parameters to initialize the root dbspace.

root dbspace 不适合指定的驱动器。释放指定驱动器上所需的空间量，或者更改 ROOTPATH配置参数以指定具有更多可用空间的其他驱动器。然后使用 -iy 参数重新启动数据库服务器以初始化 root dbspace。

Warning: Starting the database server with the parameters -iy reinitializes the root dbspace and effectively destroys any existing data. You will no longer be able to access existing databases unless you subsequently perform a full-system restore. Do not reinitialize the root dbspace unless you are certain that you want to do so.

-1800 Invalid transaction state.

You must commit or rollback the current transaction before you disconnect.

在断开连接之前，您必须提交或回滚当前事务。

-1801 Multiple-server transaction not supported.

You are attempting to span multiple connections within a single transaction. You can switch to a different connection while a transaction is active if you use the WITH CONCURRENT TRANSACTION clause when you establish the connection.

您正试图在单个事务中跨越多个连接。如果在建立连接时使用 WITH CONCURRENT TRANSACTION 子句，则可以在事务处于活动状态时切换到其他连接。

-1802 Connection name in use.

A connection with the same connection name has already been made. Each connection must have a unique connection name. Rename the connection,and try again.

数据库已完成一个具有相同连接名称的连接。每个连接必须具有唯一的连接名称。请重命名连接，然后重试。

-1803 Connection does not exist.

The connection name in a SET CONNECTION or DISCONNECT statement does not refer to an established connection. Check your program to see that the connection was made and, if so, that it was not disconnected. Also,check the spelling of the connection name in the statement that is failing.

SET CONNECTION 或 DISCONNECT 语句中的连接名称不引用已建立的连接。请检查程序，看看是否已建立连接，如果是，则表示没有断开连接。另外，请检查失败的语句中连接名称的拼写。

-1804 Invalid database environment.

The database server cannot connect to the database environment that you specified. The server cannot locate either the database server or the database that you specified. Check the syntax of your statement. If you are specifying a database server, you must use the @ sign. You cannot use //.

数据库服务器无法连接到您指定的数据库环境。服务器无法找到您指定的数据库服务器或数据库。

请检查语句的语法。如果要指定数据库服务器，则必须使用 @ 符号。不能使用 //。

-1805 Invalid connection name.

The connection name is invalid. It must conform to the same rules as any other identifier; that is, it cannot exceed the maximum length, cannot be an ANSI reserved word, must begin with a letter or underscore, and can contain only letters, digits, underscores, and dollar-sign characters.

连接名称无效。它必须符合与任何其他标识符相同的规则；也就是说，它不能超过最大长度，不能是 ANSI 保留字，必须以字母或下划线开头，并且只能包含字母、数字、下划线和美元符号。

The maximum length for identifiers depends on the database server. In GBase 8s , the maximum length is 128 characters. In other GBase 8s database servers, the maximum length is 18 characters.

标识符的最大长度取决于数据库服务器。在 GBase 8s 中，最大长度为 128 个字符。

Check that the connection name is a valid identifier and that you are using the connection name and not some other value. If a connection name was used with the original CONNECT TO statement, you must use the connection name in subsequent connection statements.

检查连接名称是否是有效的标识符，并且您正在使用连接名称而不是其他值。如果同时使用连接名称和原始 CONNECT TO 语句，则必须在后续连接语句中使用连接名称。

-1807 No connection to disconnect.

You are attempting to disconnect a connection that does not exist at this time. Check your program to see that you have not already performed a DISCONNECT statement for this connection.

您正试图断开此时不存在的连接。请检查程序，看看还没有为这个连接执行 DISCONNECT语句。

-1808 Reconnect to server_name server to perform the database operation.

If you connect to a database server using the CONNECT statement, you cannot implicitly reconnect to a server through one of the DATABASE statements (DATABASE, START DATABASE, and so on). You must switch to it with the SET CONNECTION statement.

如果使用 CONNECT 语句连接到数据库服务器，则不能通过其中一个 DATABASE 语句（DATABASE、START DATABASE 等）隐式重新连接到服务器。您必须使用 SET CONNECTION语句切换。

-1809 Server rejected the connection.

Check that you have permission to connect to the server that you specified. If you specified both a database server and a database,check to see that you have permission to access the database.

检查您是否有权连接到指定的服务器。如果同时指定了数据库服务器和数据库，请检查您是否有权访问数据库。

This error message can occur when you are trying to use a Pluggable Authentication Module (PAM) feature of IDS when one or both of the following conditions exists:当存在以下一个或两个条件时，当您尝试使用 IDS 的可插入身份验证模块（PAM）功能时，可能会出现此错误信息：* The PAM configuration file is not set correctly. Refer to the OS vendor documentation for more information.

* PAM 配置文件设置不正确。有关更多信息，请参阅 OS 供应商文档。

* The client or server computer is not configured to handle PAM messages that are generated from a connection request.

* 客户端或服务器计算机没有配置处理从连接请求生成的 PAM 消息。

-1810 Disconnect error.

A DISCONNECT ALL statement has not disconnected a connection. The database server for one of the connections might have terminated. If not, the cause is internal to the software. If the error recurs,note all circumstances and contact GBase Technical Support.

DISCONNECT ALL 语句没有断开连接。其中一个连接的数据库服务器可能已终止。如果不是，错误原因产生自软件内部。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-1811 Implicit connection not allowed after an explicit connection.

Once you have used the CONNECT TO statement to establish an explicit connection to a database server, you cannot use one of the DATABASE statements to connect implicitly to another database server. After an explicit connection, you must use the CONNECT TO statement to connect to other database servers.

一旦使用 CONNECT TO 语句建立到数据库服务器的显式连接，就不能使用其中一个 DATABASE 语句隐式连接到另一个数据库服务器。在显式连接之后，必须使用 CONNECT TO 语句连接到其他数据库服务器。

-1812 Internal error.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次出现，请记下所有情况并联系 GBase 技术支持。

-1813 Only the current connection can be made dormant.

You used the SET CONNECTION DORMANT statement incorrectly. You attempted to put a connection that was already dormant into the dormant state. Or you attempted to put a connection that is in use by another thread in a dormant state.

您错误地使用了 SET CONNECTION DORMANT 语句。试图将已处于休眠状态的连接置于休眠状态。或者尝试将另一个线程正在使用的连接置于休眠状态。

-1814 Need to allocate collection or row variable before using it.

The application needs to call ALLOCATE COLLECTION or ALLOCATE ROW before it uses a host variable of type collection or of type row in an SQL statement.

应用程序在使用 SQL 语句中的集合类型或行类型的主机变量之前，需要调用ALLOCATE COLLECTION 或 ALLOCATE ROW。

-1815 No type information for collection or row is available.

The application needs to declare a typed collection or row host variable before using it in an SQL statement. The application can fetch the complex type data from a column of type set, type list, type multiset or type row into their untyped collection or row host variable before it uses the data in the SQL statements.

应用程序需要在 SQL 语句中使用类型集合或行主机变量之前就声明它们。在使用 SQL 语句中的数据之前，应用程序可以将类型集、类型列表、类型 multiset 或类型行的列中的复杂类型数据提取到它们的非类型化集合或行主机变量中。

-1816 No such column exists in the collection or row.

The field name specified by the application does not exist in the description of the collection or row host variable. Check the description of the field names within the declaration and make sure thefield name specified matches the one in the declaration.

集合或行主机变量的描述中不存在应用程序指定的字段名称。请检查声明中字段名称的描述，并确保指定的字段名称与声明中的字段名称匹配。

-1817 No collection or row variable provided.

A collection or row host variable was expected but none was provided, or the host variable used in the derived table syntax is not a collection or row host variable.

需要集合或行主机变量，但没有提供任何变量，或者派生表语法中使用的主机变量不是集合或行主机变量。

Check the declaration of this host variable in the application and change it to a collection or row host variable declaration.

请检查应用程序中此主机变量的声明并将其更改为集合或行主变量声明。

-1818 Input variable type does not match collection or row definition.

Certain data types cannot be cast on the client. The following situations return this error:* Trying to cast any complex type into any other complex type(that is, casting a set into list)* Trying to cast a built-in type (for example, INT) into a complex type* Trying to cast a complex type into a user-defined data type* Trying to cast a built-in type into a user-defined data type Check the SQL statement and make sure the types are compatible.

某些数据类型不能在客户端上转型。以下情况会返回此错误：*尝试将任何复杂类型转换为任何其他复杂类型（将一个 set 转换为 list）*尝试将内置类型（例如，INT）转换为复杂类型*尝试将复杂类型转换为用户定义的数据类型*尝试将内置类型转换为用户定义的数据类型请检查 SQL 语句并确保类型兼容。

-1820 The host variable type was changed between fetches or puts.

If the host variable is used for user-defined-data-type columns or if the host variable itself is a user-defined-data-type host variable, the host variable type and length cannot be changed between fetches or puts.

如果主机变量用于用户定义的数据类型列，或者主机变量本身是用户定义的数据类型主机变量，则主机变量类型和长度不能在提取或放入之间更改。

-1821 Host variable is not large enough to hold the data returned from the server.

The memory allocated by the application to fetch the user-defined data type is not sufficient. Change the application so that it allocates more memory before it fetches this user-defined data type.

应用程序分配的用于获取用户定义数据类型的内存不足。请更改应用程序，以便在获取此用户定义的数据类型之前分配更多内存。

-1822 Invalid argument.

One of the arguments passed to the function has an illegal value or is NULL. Check the documentation for the valid values that can be passed to this function.

传递给该函数的参数中具有非法值或为 NULL。请检查文档以获取可传递给此函数的有效值。

-1823 Need more memory to store data.

This error is returned from ifx_var_setlen() and ifx_var_setdata() when the application tries to set the length or the data to a size that is larger than the amount of memory allocated in ifx_var_alloc(). Find the current allocated length by calling ifx_var_getlen(), resize it if necessary by calling ifx_var_alloc(), and execute ifx_var_setlen() or ifx_var_setdata() again.

当应用程序尝试将长度或数据设置为大于 ifx_var_alloc()中分配的内存量的大小时，将从 ifx_var_setlen() 和 ifx_var_setdata() 返回此错误。通过调用 ifx_var_getlen()查找当前分配的长度，如果需要请调用 ifx_var_alloc() 调整其大小，并再次执行ifx_var_setlen() 或 ifx_var_setdata()。

-1824 Message cannot be found.

The server user-defined routine has been executed, but the message text cannot be found. Check the user-defined routine to make sure all SQLSTATES returned by the server have a corresponding message text associated with them.

已经执行服务器用户定义的例程，但无法找到消息文本。请检查用户定义的例程以确保服务器返回的所有 SQLSTATES 都具有与其相关的相应消息文本。

-1825 INSERT and DELETE cannot be performed on ROW host variables.

Only UPDATE and SELECT statements can be used with row host variables.

Check the derived table syntax that is using the row host variable and use UPDATE or SELECT instead.

只有 UPDATE 和 SELECT 语句可以用于行主机变量。请检查使用行主变量的派生表语法，并使用 UPDATE 或 SELECT 代替。

-1826 DESCRIBE information about this statement is not available at this time.

When the DEFERRED_PREPARE option is turned on, the description of the statement is not known until the cursor is opened. Therefore, a DESCRIBE can only be executed after an OPEN. If DEFERRED_PREPARE and OPTOFC are both turned on, then the DESCRIBE can happen only after the FETCH, because the OPEN is not executed until the FETCH is executed.

当打开 DEFERRED_PREPARE 选项时，直到游标打开后才能知道该语句的描述。因此，一个 DESCRIBE 只能在 OPEN 之后执行。如果 DEFERRED_PREPARE 和 OPTOFC 都已打开，那么 DESCRIBE 只能在 FETCH 之后发生，因为在执行 FETCH 之前不会执行 OPEN。

-1828 Cannot use scroll or hold cursor with client collections.

A cursor declaration for a client collection cannot be for a scroll or hold cursor, as in the following declarations:客户端集合的游标声明不能用于滚动或保持游标，如以下声明所示：/** scroll cursor case **/EXEC SQL DECLARE cur1 SCROLL CURSOR FOR SELECT * FROM table(:collection_host_variable);/** hold cursor case **/EXEC SQL DECLARE cur2 CURSOR WITH HOLD FOR SELECT * FROM table(:collection_host_variable);Declare the cursor as follows instead:相反，如下所示声明游标：EXEC SQL DECLARE cur3 CURSOR FOR SELECT * FROM table(:collection_host_variable);-1829 Cannot open file citoxmsg.pam.

The file citoxmsg.pam is missing from the directory $GBS_HOME/msg.

目录 $GBS_HOME/msg 中缺少 citoxmsg.pam 文件。

If this error occurs, note all circumstances and contact GBase Technical Support.

如果发生此错误，请记下所有情况并联系 GBase 技术支持。

-1831 Combination of FetArrSize, Deferred-PREPARE, and OPTOFC is not supported.

-1832 Environment block is greater than 32K.

At the start of a session, the client groups all the environment variables that the server will use and sends the environment variables to the server as a single block. The maximum allowed size of this block is 32K. The current block of environment variables exceeds 32K. Unset one or more environment variables or reduce the size of some of the environment variables and then retry connection to IDS.

在会话开始时，客户端会将服务器将使用的所有环境变量进行分组，并将环境变量作为单个 block 发送到服务器。该 block 的最大允许大小为 32 K。当前的环境变量 block 超过 32 K。请取消设置一个或多个环境变量或减小某些环境变量的大小，然后重新连接到 IDS。

-1833 Cannot open file itoxmsg.pam.

The file itoxmsg.pam is missing from the directory $GBS_HOME/msg.

文件 itoxmsg.pam 从 $GBS_HOME/msg 目录中丢失。

If this error occurs, note all circumstances and contact GBase Technical Support.

如果发生此错误，请记下所有情况并联系 GBase 技术支持。

-2013 The output form file filename cannot be opened.

Possibly your account does not have permission to write in the specified directory; possibly the disk is full. In some systems, the problem might be related to a limit on the number of open files. Look for operating-system messages for more information.

可能是因为您的账户没有写入指定的目录的权限；可能磁盘已满。在某些系统中，问题可能与打开文件的数量限制有关。请查找操作系统消息以获取更多信息。

-2014 There were an incorrect number of arguments on the operating system command line. At least one (1) argument is expected.

When you run the Form Compiler from the command line, you must specify either the -d option or the name of a form.

从命令行运行 Form Compiler 时，必须指定 -d 选项或表单的名称。

-2015 An open comment symbol, {, was found inside an already open comment on line line, character column. This could be due to a failure to close the previously opened comment, which was begun on line line,character column.

Nested comments are not supported. Review the form specification, and inspect all comments. Check that each open brace has a matching close brace.

不支持嵌套注释。请查看表格规范，并检查所有注释。检查每个开放大括号是否有匹配的大括号。

-2016 A comment has been opened, but not closed. The last comment begun was opened on line line, character column.

Insert a close-comment symbol where appropriate in the report specification.

请在报表规范中适当的位置插入一个结束注释的符号。

-2017 The character data value does not convert correctly to the field type.

You have entered a character value (a quoted string) into a field that has a different data type (for example INTEGER). However, the characters that you entered cannot be converted to the type of the field. Consult the operating instructions for this application, then reenter the data.

您已将字符值（带引号的字符串）输入到具有不同数据类型的字段（例如 INTEGER ）。但是，输入的字符不能转换为字段的类型。请参阅此应用程序的操作说明，然后重新输入数据。

-2018 A grammatical error has been found on line line, character column.

The construct is not understandable in its context.

This message points to the exact spot in a source file where the compiler could no longer understand the input. The actual mistake might be earlier in the file, perhaps several lines earlier, but it is not later. Other, more specific error messages should also appear.

此消息指向源文件中编译器无法理解输入的确切位置。实际的错误可能早于文件，可能早于几行，但其还不算晚。会出现其它更具体的错误信息。

-2019 This integer exceeds the maximum size allowed.

The INTEGER data type can accept numbers with absolute values from 0 to 2,147,483,647 (plus or minus (2 to the 31st power) - 1). If you have to store numbers outside this range, redefine the column or variable to use DECIMAL data type. (The value -2,147,483,648 is a 32-bit value but is not acceptable; it is used in 4GL to indicate a null value.)INTEGER 数据类型可以接受绝对值从 0 到 2,147,483,647（加号或减号（2 的 31 次方）-1）的数字。如果必须存储此范围之外的数字，则请重新定义列或变量，使用 DECIMAL 数据类型。（值 -2,147,483,648 是一个 32 位值，但不可接受；它在 4GL 中用于指示空值。）-2020 The table table-name could not be opened. The operating system was asked to open it for writing.

You are using a database server that manages tables as ordinary disk files. The current database is managed as a directory, and tables are files within it. Look for operating-system error messages that might give more information. Locate the database directory (either in the current directory or on a path that is named in the DBPATH environment variable). Check that disk space is available. In UNIX, your personal account does not have to have write access to the directory and table files; however, they must be writable to the group-id GBase 8s.

您正在使用将表管理为普通磁盘文件的数据库服务器。当前数据库作为目录进行管理，表是其中的文件。查找可能提供更多信息的操作系统错误消息。找到数据库目录（在当前目录中或在 DBPATH 环境变量中命名的路径中）。检查磁盘空间是否可用。在 UNIX 中，您的个人账户不必具有对目录和表文件的写入权限；但是，GBase 8s 组必须对它们必须具有写入权限。

-2021 An illegal color has been specified. Colors 0 through 7 are white,yellow, magenta, red, cyan, green, blue, and black.

Both in a COLOR attribute in a form specification and in a display attribute in a 4GL program, you must specify colors by name and spell them as this message shows. Check the spelling and punctuation of the statement.

无论是在表单规范的 COLOR 属性中还是在 4GL 程序中的显示属性中，都必须按名称指定颜色并在此消息显示时拼写它们。请检查该与居家的拼写和标点符号。

-2022 This identifier exceeds the maximum length for identifiers,which is .

Names of fields and other identifiers cannot exceed the maximum length.

字段和其他标识符的名称不能超过最大长度。

Revise the form specification and recompile it.

请检查表单规范并重新编译它。

-2023 This quoted string exceeds the maximum length for quoted strings,which is length.

You cannot use longer quoted strings. In a form, you cannot join shorter strings to make longer ones, so this maximum is an absolute length limit. You must revise the form specification and recompile it.

无法使用更长的引用字符串。在一个表单中，不能加入较短的字符串来制作较长的字符串，因此此最大值是绝对长度限制。必须修改表单规范并重新编译它。

-2024 There is already a record name specified. If the record name is the same as a table name in the form, a default record of the same name has been created.

Check that the record-name of every screen record and screen array is unique in the form specification. A screen record is automatically defined for each table that is used in the ATTRIBUTES section to define a field. If you define a record with the name of a table, it is seen as a duplicate.

检查每个屏幕记录和屏幕数组的记录名在表单规范中是否是唯一的。屏幕记录会自动定义ATTRIBUTES 部分中用于定义字段的每个表。如果您使用表名称定义记录，则将其视为重复值。

-2025 The comment close symbol (}) has been found on line line, character column, even though no comment has been opened.

Unless comment symbols are enclosed in quotes, they must be balanced.

Probably you accidentally deleted the open-comment symbol when you were editing. Change the form specification so that comments are properly delimited.

除非注释符号用引号引起来，否则它们必须成对出现。编辑时可能意外删除了 open-comment 符号。

请更改表单规范，以便正确分隔注释。

-2026 The FORMONLY field fieldname did not have a type specified. A type must be specified if include lists or default values are specified.

The usual way of defining a form-only field (one not linked to a database column) is as follows:定义仅用于表单的字段（没有链接到数据库列）的常用方法如下所示：tagname = DISPLAYONLY.fieldname TYPE datatype The TYPE clause is required. Review the attribute statements and recompile the form. (The keyword FORMONLY is used in forms that the 4GL compiler compiles. Its meaning is the same as DISPLAYONLY.)TYPE 子句是必需的。请检查属性语句并重新编译表单。（关键字 FORMONLY 用于 4GL编译器编译的形式，其含义与 DISPLAYONLY 相同。）-2027 An illegal (invisible, control) character has been found on line line,character column. It has been replaced by a blank in the listing,but it is still in the source (input) table, and should be removed before attempting to compile again.

Illegal characters can be introduced into files by using a word-processing editor in document mode instead of text mode,by striking nonprinting keys while editing the file, or by data corruption.y通过在文档模式下使用文字处理编辑器代替文本模式，在编辑文件时按非打印键可以将非法字符引入文件。或者是由于数据损坏而引入了非法字符。

-2028 The symbol name does not represent a table prefix used in this form.

It cannot be used here to select record elements.

In a SCREEN RECORD statement, each component must be introduced by the name of the table as defined in the TABLES section or by the word FORMONLY. Review the spelling of the indicated name against the TABLES section, and check the punctuation of the rest of the statement.

在 SCREEN RECORD 语句中，每个组件必须按照 TABLES 部分中定义的表名或 FORMONLY一词的名称引入。请查看指定名称与 TABLES 部分的拼写，并检查其余部分的标点符号。

-2029 Screen record array name has component sizes which either differ from the specified dimension of the array or differ among themselves.

The dimension of the screen array is written in square brackets that follow its name, as in the following example where the dimension is 12:屏幕数组的维度写在名称后面的方括号中，如以下维度为 12 的示例所示：SCREEN RECORD details [12](items.item_num, items.item_desc, items.unit_price)In this case, exactly 12 screen fields should be associated with each of the three columns that are listed in the screen record. This error message appears when one or more of the columns appear a different number of times.

在这种情况下，屏幕记录中列出的三列中的每一列都应与 12 个屏幕字段相关联。

当一个或多个列显示不同的条目数时，会出现此错误消息。

-2030 A typographical error has been found on line line, character column.

The single character at the indicated position, although printable, is unexpected and does not fit the syntax of a form specification.

指定位置处的单个字符虽然是可打印的，却是不是预期的，并且不符合表单规范的语法。

-2031 The WORDWRAP attribute can only be specified for CHAR, VARCHAR and TEXT fields.

This PRINT statement applies the WORDWRAP function to a value that is not character data. Check that the field named is the one that you intended, and check the punctuation of the rest of the statement.

该 PRINT 语句将 WORDWRAP 函数应用于不是字符数据的值。请检查指定的字段是否是您想要的字段，并检查语句其余部分的标点符号。

-2032 The number above could not be successfully converted to either an INTEGER or a DOUBLE or a LONG.

Something is wrong with the numeric constant; probably it has too many digits. Check the punctuation of the statement; possibly two numbers have been run together.

数字常量有些问题；可能它有太多的数字。请检查语句的标点符号；可能是同时运行了两个数字。

-2033 The field name has a default value not within the range of its include list values.

The indicated field has both a DEFAULT attribute and an INCLUDE attribute, but they disagree. The default value is not one that is allowed. Modify one of the attributes, and recompile the form specification.

指定的字段同时具有 DEFAULT 属性和 INCLUDE 属性，但是它们互相冲突。缺省值不是允许的值。请修改其中一个属性，并重新编译表单规范。

-2034 This feature is not available for GBase 8s SQL. It is available for GBase 8s 4GL by using the "form4gl" form builder.

The PERFORM form compiler and the 4GL form compiler accept very similar form specifications, but they differ in some features. This statement uses a 4GL feature, but PERFORM cannot process it.

PERFORM 表单编译器和 4GL 表单编译器接受相似的表单规范，但它们在某些功能上有所不同。

该语句使用 4GL 功能，但 PERFORM 无法处理它。

-2035 The WORDWRAP attribute, if specified, should apply to all the columns in a join.

Ignore this message. It applies to a feature of PERFORM (joins) that 4GL does not support.

忽略此消息。它适用于 4GL 不支持的 PERFORM（joins）功能。

-2036 The display lines of a multi-line field lie in different screen pages.

A multiline field (multiple fields with identical tags, given the WORDWRAP attribute) must be complete within a screen page. Possibly you did not intend the field to be on two pages. If your page layout, plus 4 reserved lines, is taller than the physical screen (as specified in the SCREEN statement or in the lines dimension on the command line),the form is divided by starting a new page after the last line that can fit on the page, and this situation might accidentally split a multiline field. In any case, rearrange fields so that the multiline field fits on a single page.

多行字段（带有相同标签的多个字段，具有 WORDWRAP 属性）必须在屏幕页面内完成。可能您不打算将这个字段分成两页。如果页面布局加上 4 条保留行高于物理屏幕（如 SCREEN语句或命令行上的行尺寸中所指定的那样），则可以通过在最后一行之后开始新页面来页面上划分表单，这种情况可能会意外地分割多行字段。无论如何，请重新排列字段以便多行字段适合单个页面。

-2037 The PROGRAM attribute can only be specified for BYTE and TEXT fields.

The field attribute PROGRAM specifies an external program to edit or display a BYTE or TEXT value; these values are assumed to be too large and specialized for the normal form-display methods. However, in this statement, the attribute is applied to a column of another type, which is not supported. Check the table and column names to make sure that they are as you intended, and verify the current definition of the table in the database that is named in the DATABASE statement.

字段属性 PROGRAM 指定一个外部程序来编辑或显示 BYTE 或 TEXT 值；假定这些值太大并且使用特定的正常的形式显示。但是，在此语句中，该属性应用于另一种类型的列，但该列不支持。请检查表名和列名以确保它们符合要求，并验证当前在 DATABASE 语句中命名的数据库中的表定义。

-2038 BLOB fields cannot be joined.

Columns of BYTE and TEXT types cannot be compared. Therefore, they cannot be used in joining tables, and they cannot be named as join columns or in a COMPOSITES statement. Check that the table and column names are as you intended, and verify the current definition of the table in the database that the DATABASE statement names.

BYTE 和 TEXT 类型的列无法进行比较。因此，它们不能用于连接表，并且不能将其命名为连接列或 COMPOSITES 语句。请检查表名和列名是否符合您的要求，并验证当前数据库中 DATABASE 语句指定名称的定义。

-2039 The attributes AUTONEXT, DEFAULT, INCLUDE, VERIFY, RIGHT and ZEROFILL are not supported for BLOB fields.

Columns of BYTE and TEXT types cannot be used in the ways that these attributes imply. Check that the table and column names are as you intended, and verify the current definition of the table in the database that the DATABASE statement names.

BYTE 和 TEXT 类型列不能隐式地以这些属性的方式使用。请检查表名和列名是否符合您的要求，并验证当前数据库中 DATABASE 语句所指名称的定义。

-2040 The form name name exceeds the maximum length of length characters.

The limit of the form compiler on names might be shorter than that of the host operating system. Rename the form-specification file, and issue the command again.

表单编译器在名称上的限制可能比主机操作系统的限制短。重命名窗体规范文件，并再次发出该命令。

-2041 The form filename cannot be opened. This is probably because it does not exist, or the user does not have read permission.

Check the spelling of filename. Check that the form file exists in your current directory. If it is in another directory, check that the correct pathname has been provided. On a UNIX system, if these things are correct, verify that your account has read permission on the file.

检查文件名的拼写。检查表单文件是否存在于当前目录中。如果它在另一个目录中，请检查是否提供了正确的路径名。在 UNIX 系统上，如果以上几点都是正确的，请确认您的账户对文件具有读取权限。

-2042 The usage of a BLOB field in or around the above statement is incorrect.

Columns of BYTE and TEXT types cannot be used in the ways that this statement implies. Check that the table and column names are as you intended, and verify the current definition of the table in the database that the DATABASE statement names.

BYTE 和 TEXT 类型列不能隐式地以这些属性的方式使用。请检查表名和列名是否符合您的要求，并验证当前数据库中 DATABASE 语句所指名称的定义。

-2043 Screen layout exceeds the specified screen width. This is a warning only.

The assumed screen width is taken from the SCREEN statement or a command-line parameter to the form compiler, with a default of 80 characters. If the current form specification is displayed on a terminal of that width, either some lines truncate, or lines wrap unattractively.

假定的屏幕宽度是从 SCREEN 语句或 acommand-line 参数获取到表单编译器，缺省值为 80 个字符。如果当前表单规范在该宽度的终端上显示，则可能会有一些行被截断，或者换行很难看。

-2044 At most one color attribute may be specified for each field with each condition.

Review this ATTRIBUTES statement; a problem exists near a COLOR attribute. Look for missing punctuation.

请检查 ATTRIBUTES 属性；COLOR 属性旁存在一个问题。请检查缺少的标点符号。

-2045 The conditional attributes of a 4GL field cannot depend on the values of other fields.

The Boolean expression in a WHERE clause of a COLOR attribute can use only the name of that field and constants. Revise this attribute, and recompile the form.

COLOR 属性的 WHERE 子句中的布尔表达式只能使用该字段和常量的名称。修改此属性并重新编译表单。

-2100 Field field has validation string error, String = string.

One of the formatting or validation strings that is stored in the syscolval or syscolatt tables is improperly coded. The string is shown as is the field to which it applies. Use the Column Attributes Dictionary utility in Windows or the upscol utility in DOS and UNIX to update the string.

存储在 syscolval 或 syscolatt 表中的格式化或验证字符串被错误地编码。字符串显示为它应用的字段。使用 Windows 中的 Column Attributes Dictionary 实用程序或 DOS 和 UNIX 中的 upscol 实用程序来更新字符串。

-2800 The first line of the specification must be the keyword database followed by the database name, or the FORMONLY keyword (4GL only). An optional WITHOUT NULL INPUT may also follow.

Aside from comment lines, a form specification must begin by naming a database. Review the file for punctuation and spelling errors. Refer to the reference manual for this product for the options that are allowed in the DATABASE statement.

除了注释行外，表单规范必须以命名数据库开始。查看文件中的标点符号和拼写错误。

有关 DATABASE 语句中允许的选项，请参阅本产品的参考手册。

-2810 The name name is not an existing database name.

This name, which was found in the DATABASE statement at the start of the form specification, is not a database that can be found. If you are using GBase 8s SE, the database must reside either in the current directory or in a directory that the DBPATH environment variable names.

在表单规范开头的 DATABASE 语句中找到的名称，不是现有的数据库名称。如果您正在使用 GBase 8s SE，则数据库必须位于当前目录中或 DBPATH 环境变量所指定的目录中。

-2811 The temporary table table-name could not be opened for writing.

The application is attempting to create a temporary table in the database or some other temporary file but received an error code from the database server. The most probable cause is a lack of disk space.

Look for other error messages, including operating-system messages,that might give more information.

应用程序正试图在数据库或其他临时文件中创建临时表，但收到数据库服务器的错误代码。

最可能的原因是缺少磁盘空间。查找可能提供更多信息的其他错误消息，包括操作系统消息。

-2812 The temporary table table-name could not be read.

The application created and filled a temporary table in the database or created and filled some other temporary file, but when it tried to read rows from it, it received an error code from the database server.

Probably a hardware failure occurred. Look for other error messages,including operating-system messages, that might give more information.

应用程序在数据库中创建并填充了一个临时表，或者创建并填充了一些其他临时文件，但是当它尝试从中读取行时，它从数据库服务器收到错误代码。可能是发生了硬件故障。查找可能提供更多信息的其他错误消息，包括操作系统消息。

-2820 The label name between brackets is incorrectly given or the label is missing.

In this line of the SCREEN section of a form specification, square brackets indicate a field. The brackets should contain a simple name.

Instead, they contain spaces or an invalid name. Review the punctuation of the line to make sure that the brackets contain only a simple identifier.

在表单规范的 SCREEN 部分的该行中，方括号表示一个字段。方括号应该包含一个简单的名称。相反，它们包含空格或无效名称。检查该行的标点符号以确保括号只包含一个简单的标识符。

-2830 A left square bracket has been found on this line, with no right square bracket to match it.

A screen field cannot span lines. Review the SCREEN section to make sure all fields are properly marked. To create a multiline field, mark off multiple complete fields all with the same field tag.

屏幕字段不能跨越行。请查看 SCREEN 部分以确保所有字段都已正确标记。要创建多行字段，请标记多个完整字段，并使用相同的字段标记。

-2831 The control block has exceeded the maximum of limit fields.

Too many columns or tables are listed in the OF clause of this control block. Write separate control blocks, each for part of the list.

该控制块的 OF 子句中列出了太多的列或表。请编写单独的控制块，根据列表的每个部分划分。

-2832 This form uses "|" to both start and end a field placement.

Because of this, the form must specify left and right delimiters which are the same character. This is done with the DELIMITERS command in the INSTRUCTIONS section.

因此，表单必须指定相同字符的左右分隔符。通过 INSTRUCTIONS 部分中的 DELIMITERS 命令完成。

Make sure that a DELIMITERS statement is present and that it specifies the same character for both left and right delimiters.

确保存在 DELIMITERS 语句，并为左右分隔符指定相同的字符。

-2834 NULL cannot be used as the default. It is already the default if you specify nothing.

This ATTRIBUTES statement contains a DEFAULT clause that specifies NULL. Either delete the clause, or specify another value.

此 ATTRIBUTES 语句包含一个指定 NULL 的 DEFAULT 子句。要么删除该子句，要么指定另一个值。

-2840 The label tag was not defined in the form.

The indicated name appears at the left of this ATTRIBUTES statement,but it does not appear within brackets in the SCREEN section. Review the field tags that have been defined to see why this one was omitted.

指定的名称出现在 ATTRIBUTES 语句的左侧，但它不出现在 SCREEN 部分的括号内。请查看已经定义的字段标签，以了解为什么省略这个字段标签。

-2841 The form must include a tables declaration before the attributes section.

Check that the form-specification file contains a DATABASE statement, a SCREEN section, a TABLES section, and an ATTRIBUTES section, in that order.

按照该顺序检查表单规范文件是否包含 DATABASE 语句、SCREEN 部分、TABLES 部分和ATTRIBUTES 部分。

-2843 The column column-name does not appear in the form specification.

A name in this ATTRIBUTES statement should have been defined previously in the form specification. Check that all names in the statement are spelled correctly and defined properly.

此 ATTRIBUTES 语句中的名称应该已经在表单规范中定义。检查声明中的所有名称的拼写是否正确并正确定义。

-2844 The column column-name is associated with more than one field in the form specification.

Any one table column can be related to only one field in an ATTRIBUTES statement. Possibly you are trying to display columns from two or more tables that have the same column names; in that case, prefix the table names to the column names to distinguish them.

任何一个表列都只能与 ATTRIBUTES 语句中的一个字段相关联。可能您试图显示来自两个或多个具有相同列名称的表的列；在这种情况下，将表名添加到列名前面以区分它们。

-2845 The composite column for table table-name containing column column is not indexed. Performance will be much improved by creating an index on the column.

The presence of an index can greatly reduce the time that is needed to join tables. However, an index is not essential, especially when the tables are small, or during initial testing.

索引的存在可以大大减少连接表所需的时间。但是，索引不是必需的，特别是在表很小或初始测试期间。

-2846 The field field-name is not a member of the table table-name.

Something in this statement suggests that the name shown is part of this table, but that is not true in the current database. Review the spelling of the two names. If they are as you intended, check that the correct database is in use and that the table has not been altered.

该语句中的某些内容表明所显示的名称是此表的一部分，但在当前数据库中不是这样。请查看这两个名字的拼写。如果它们符合您的要求，请检查是否正在使用正确的数据库并且表未被更改。

-2850 The name name is not a column name in this database.

The tables that are specified in the TABLES section of the form exist,but the column name, which is named in the ATTRIBUTES section, does not. Check its spelling against the actual table. Possibly the table was altered, or the column was renamed. You can use GBase 8s SQL to check column names under the Tables menu, Info selection.

在表单的 TABLES 部分中指定的表存在，但在 ATTRIBUTES 部分中不包含命名的列名。

检查其对实际表的拼写。可能表被更改了，或者列被重新命名了。可以使用 GBase 8s SQL检查 Info Tables 的信息。

-2856 The TODAY attribute may be assigned only to date columns.

The TODAY function (not attribute) returns the value of today's date.

That value can be assigned only to a field that has the DATE or DATETIME data type. The field in this statement has a different type.

Automatic data conversion is provided in 4GL programs, but not in the context of a form.

TODAY 函数（非属性）返回今天日期的值。该值只能分配给具有 DATE 或 DATETIME数据类型的字段。该语句中的字段具有不同的类型。在4GL程序中提供自动数据转换。

但不在表单的上下文中提供。

-2857 There can be only one dominant composite column in a join list.

This statement defines a join list, a list of two or more column names that are related to the same form field. In such lists, an asterisk preceding a column name indicates that column is the dominant column in a verify join. Only one such column is allowed in any join, but two or more are present in this list. Review the documentation on verify joins, and choose a single dominant table.

该语句定义了一个连接列表，是与同一个表单字段相关的两个或多个列名称的列表。在这样的列表中，列名前面的星号表示该列是验证连接中的显性列。在任何连接中只允许有一个这样的列，但是此列表中有两个或更多列。请查看关于验证连接的文档，并选择一个统一的表。

-2858 The table table-1 is joined to the table table-2, but its joined columns do not belong to a composite key.

You have defined two or more different joining columns between the two indicated tables. However, no composite index exists on the joining columns. Such an index is required to ensure that a composite key exists; that is, that any combination of values from the joining columns will occur only once. Review the two or more ATTRIBUTES statements that define join columns for these two tables. Make sure that they are as you intended; for example, make sure that you intended to join two tables on two or more columns, instead of joining three or more tables on one column each. If you intended the composite key, then use the CREATE INDEX command to create a composite unique index on those columns for at least table1.

已在两个指定的表之间定义了两个或更多不同的连接列。但是，连接列上不存在组合索引。

需要组合索引确保组合建的存在；也就是说，来自连接列的值的任何组合都只会出现一次。

请查看定义这两个表的连接列的两个或多个 ATTRIBUTES 语句。确保它们是您想要的；例如，确保在两列或多个列上连接两个表，而不是每列连接三个或更多表。如果打算使用组合键，则使用 CREATE INDEX 命令在这些列上至少为 table1 创建一个组合唯一索引。

-2859 The column column-name is a member of more than one table -- you must specify the table name.

Two or more tables that are named in the TABLES section have columns with the name shown. You must make clear which table you mean. To do this, write the table name as a prefix of the column name, as table.column, wherever this name is used in the form specification.

在 TABLES 部分中命名的两个或多个表具有相同名称的列。您必须明确目的。为此，请将表名作为列名称的前缀写入，如 table.column 所示，在表单规范中使用该形式的限定名。

-2860 There is a column/value type mismatch for column-name.

This statement assigns a value to the field with the DEFAULT clause or uses its value with the INCLUDE clause, but it does so with data that does not agree with the data type of the field. Review the data type of the field (which comes from the column with which it is associated),and make sure that only compatible values are assigned.

该语句使用 DEFAULT 子句将值赋给字段，或者将值与 INCLUDE 子句一起使用，但与该字段的数据类型不一致的数据使用了该值。请查看字段的数据类型（相关联的列）的数据类型，并确保只分配兼容值。

-2861 You have exceeded the maximum of number tables.

A limit exists on the number of tables that can be in use at one time.

(This limit might be different on different host systems or with different database servers.) Reduce the number of tables that you use in the form.

一次可以使用的表的数量存在限制（此限制可能会因不同的主机系统或不同的数据库服务器而有所不同）。请减少表单中使用的表次数。

-2862 The table table-name cannot be found in the database.

All tables used in a form must exist at the time that the form is compiled, so that the compiler can verify the data types of the columns. The indicated table does not exist in the database that is named in the form. Check the spelling of the table name and database name. If they are as you intended, either you are not using the version of the database that you expected (check the value in the DBPATH environment variable), or the database has been changed.

在表单中使用的所有表必须在表单编译时存在，以便编译器可以验证列的数据类型。指定的表不存在于表单中命名的数据库中。检查表名和数据库名称的拼写。如果它们符合您的要求，那么要么您没有预期版本的数据库（检查 DBPATH 环境变量中的值），要么数据库已更改。

The tables that are specified in the TABLES section of the form exist,but column-name, which is named in the ATTRIBUTES section, does not.

Check its spelling against the actual table. Possibly the table was altered, or the column was renamed. You can use GBase 8s SQL to check column names under the Tables menu, Info selection.

在 TABLES 部分中指定的表存在，但在 ATTRIBUTES 部分中命名的 column-name 不存在。

请检查其对实际表的拼写。可能表被更改，或者列被重新命名。您可以使用 GBase 8s SQL来 Info Table 的信息。

-2863 The column column-name does not exist among the specified tables.

The tables that are specified in the TABLES section of the form exist,but column-name, which is named in the ATTRIBUTES section, does not.

Check its spelling against the actual table. Possibly the table was altered, or the column was renamed. You can use GBase 8s SQL to check column names under the Tables menu, Info selection.

在 TABLES 部分中指定的表存在，但在 ATTRIBUTES 部分中命名的 column-name 不存在。

请检查其对实际表的拼写。可能表被更改，或者列被重新命名。您可以使用 GBase 8s SQL来 Info Table 的信息。

-2864 The table table-name is not among the specified tables.

The indicated table is used in this statement but is not defined in the TABLES section of the form specification. Check its spelling; if it is as you intended, add the table in the TABLES section.

在此语句中指定表未在表单规范的 TABLES 部分中定义。请检查其拼写；如果它符合您的要求，请在 TABLES 部分添加该表。

-2865 The column column-name does not exist in the table table-name.

Something in this statement implies that the column shown is part of the indicated table (most likely the statement refers to table-name.column). However, it is not defined in that table. Check the spelling of both names. If they are as you intended, then check the contents of the database; possibly the table has been altered or the column renamed.

该语句中的某些内容指示所显示的列是指定表的一部分（很可能该语句引用了table-name.column）。

但是，它没有在该表中定义。请检查两个名称的拼写。如果它们符合您的要求，请检查数据库的内容；可能表已被更改或列已重命名。

-2866 The NOW attribute may be assigned only to datetime columns.

This message is not in use in any current product. SQL does not support any NOW attribute or function; use the CURRENT function.

此消息已经不再在任何当前产品中使用。 SQL 不支持任何 NOW 属性或函数；请使用 CURRENT 函数。

-2867 The CURRENT attribute may be assigned only to datetime columns.

The CURRENT function (not attribute) produces the current date and time as a DATETIME value, but the field that is referenced in this statement does not have the DATETIME data type. Automatic data conversion is not supported in this context. Review the statement to make sure that it refers to the field that you intended, and revise the form to assign DATETIME values only to DATETIME fields.

CURRENT 函数（不是属性）将当前日期和时间作为 DATETIME 值生成，但在此语句中引用的字段不具有 DATETIME 数据类型。在此上下文中不支持数据自动转型。请查看语句以确保它引用了想要的字段，并修改表单，将 DATETIME 值分配给 DATETIME 字段。

-2870 The subscripted column size does not match the space allocated in the display field.

This attribute statement relates a substring of a column to a display field. However, either the substring numbers are wrong (the first is less than 1 or greater than the size of the column, the second is less than the first), or they are correct but the number of characters that they select is different from the size of the display field. Revise the substring numbers to select exactly as many characters as the field requires.

该属性语句将列的子串与显示字段相关联。但是，子字符串数字是错误的（第一个小于 1或大于列的大小，第二个长度小于第一个），或者它们是正确的，但它们选择的字符数与显示的字段的大小不同。请修改子字符串数以选择与字段完全一样多的字符。

-2880 The word 'screen' or 'end' has been left out.

Every form specification must end in the keyword END and must contain the keyword SCREEN. Both must begin in the first column of a line.

Review the contents of the form specification to make sure that all the necessary sections are properly marked.

每个表单规范必须以关键字 END 结尾，并且必须包含关键字 SCREEN。两者都必须从行的第一列开始。请查看表格规范的内容，确保所有必要的部分都被正确标记。

-2890 A screen definition must begin with a left curly bracket '{'.

Each screen layout must be enclosed in braces ({ }). The open brace must be the first character on its line. Review the form specification to make sure that the screen layout is punctuated properly.

每个屏幕布局必须用大括号（{}）括起来。大括号必须是行中的第一个字符。

检查表单规范，确保屏幕布局使用了正确的标点符号。

-2892 The column column-name name appears more than once. If you wish a column to be duplicated in a form, use the same display field label.

The expected way to display the same column in two or more places is to put two or more fields in the screen layout, each with the same tag-name. Then put a single statement in the ATTRIBUTES section to associate that tag-name with the column name. The current column value will be duplicated in all fields. If you intended to display different columns, the column names as listed in the ATTRIBUTES section must differ. If you intend to display different columns that happen to have the same column-names, prefix each with its table-name.

在两个或多个位置显示相同列的方法是在屏幕布局中放置两个或多个字段，每个字段都具有相同的标签名称。然后在 ATTRIBUTES 部分中添加一条语句，将该标签名称与列名称关联。

当前列值将在所有字段中重复。如果打算显示不同的列，则 ATTRIBUTES 部分列出的列名称必须不同。如果打算显示具有相同列名的不同列，则在每个列前加上它的表名。

-2893 The display field label tag-name appears more than once in this form, but the lengths are different.

You can put multiple copies of a field in the screen layout (all will display the same column), but all copies must be the same length.

Review the SCREEN section to make sure that, if you intended to have multiple copies of one field, all copies are the same.

您可以在屏幕布局中放置多个字段副本（全部将显示相同的列），但所有副本必须具有相同的长度。请检查 SCREEN 部分，如果打算包含一个字段的多个副本，则所有副本都必须相同。

-2895 Display field length of field-size does not match the database column length of column-size. This is a warning only.

The size of the character field that is defined in this statement (as shown by its appearance in the SCREEN section) is different from the size of the associate column. You specified the -v option to the form compiler to request warnings of this type.

此语句中定义的字符字段的大小（在 SCREEN 部分中的显示）与关联列的大小不同。

为表单编译器指定 -v 选项来请求此类型的警告。

-2901 Field name contains two conflicting attributes, first and second.

This statement contradicts itself. The UPSHIFT and DOWNSHIFT attributes cannot be applied to the same field; nor can NOENTRY and REQUIRED or NOETNRY and VERIFY. Review the statement, and correct the selection of attributes.

该语句自相矛盾。UPSHIFT 和 DOWNSHIFT 属性不能应用于同一字段；NOENTRY 和 REQUIRED也不能应用于同一字段，NOETNRY 和 VERIFY 也不行。请查看该语句，并修改属性。

-2920 The column column is a dominant column but it is not indexed.

Performance will be much improved by creating an index on the column.

You have defined the indicated column as dominant in a verify join.

Whenever the operator enters a value in the field, it will be looked up in this column. Such a lookup operation is very quick when an index is present. No index on the column exists at this time. Without one, a lookup might be extremely slow. Unless the field does not allow operator input (in which case you should remove the asterisk) or the table is very small (a few dozen rows at most), you should create an index for this column before you put the form into use.

您已将指定的列定义为判定连接中的显式列。每当操作者在该字段中输入值时，都会在此列中查找。索引存在时，这种查找操作会非常快速。此时列上没有索引。没有索引，查找可能会非常缓慢。除非该字段不允许操作者输入（在这种情况下，应该删除星号）或者表非常小（最多几十行），否则您应该在使用该表单之前为该列创建一个索引。

-2921 The database dbname is not compatible with the current version of GBase 8s SQL.

A prior version of GBase 8s software created the database that is named in the DATABASE statement in this form. Before the present system can use the database, you must use the sqlconv utility to convert it.

先前版本的 GBase 8s 软件在此表单中 DATABASE 语句中创建了命名的数据库。

在本系统可以使用数据库之前，您必须使用 sqlconv 实用程序对其进行转换。

-2930 Portions of the column name are displayed on the screen more than once.

This form displays subscripted portions of the indicated column in different fields. This situation is permitted; however, no single character can appear in more than one field. That is, the subscripts cannot overlap. For example, you can display name[25,49] in one field and name[50,74] in another. You cannot display name[25,49] and name[25,74] because some characters would be displayed twice.

该表在不同的字段中显示指定列的下标部分。这种情况是允许的。但是，单个字符不能出现在多个字段中。也就是说，下标不能重叠。例如，可以在一个字段中显示名称[25,49]，在另一个字段中显示名称[50,74]。不能显示名称[25,49]和名称[25,74]，因为某些字符会显示两次。

-2931 There is an error in the format specification.

Check the content of the FORMAT string in this statement. It is not correct for the data type; that is, it has characters other than # and. for a numeric column, and it has an incorrect internal length for a DATE column (for example, yyy, which calls for a three-digit year).

检查这个语句 FORMAT 字符串的内容。数据类型不正确；也就是说，它具有＃和 . 以外的其他字符。对应 DATE 列的数值列的内部长度不正确（例如，yyy，它要求三位数年份）。

-2932 Formats may be specified only for float, smallfloat,decimal, or date columns.

This attribute statement specifies a FORMAT string, but the data type of the field is not one of the four that support formatting: FLOAT,SMALLFLOAT, DECIMAL (or MONEY), and DATE. If this column is not DISPLAYONLY, check that it has been associated with the right column and that the column is defined in the database as you expected.

此属性语句指定一个 FORMAT 字符串，但该字段的数据类型不是以下支持格式化的四种格式：FLOAT、SMALLFLOAT、DECIMAL（或 MONEY）和 DATE。如果此列不是 DISPLAYONLY，请检查它是否与右列相关联，并且是否按照预期在数据库中定义了该列。

-2933 The format width is larger than the allocated display width.

The length of the FORMAT string that is specified for this field is greater than the length of the field itself as shown in the SCREEN section. Review the screen layout, and revise it or the format so that they agree.

为该字段指定的 FORMAT 字符串的长度大于字段本身的长度，如 SCREEN 部分所示。

请查看屏幕布局，修改它或 FORMAT 字符串的格式以便匹配。

-2934 The format width is less than the allocated display width.

The length of the FORMAT string that is specified for this field is less than the length of the field itself as shown in the SCREEN section. Review the screen layout, and revise it or the format so that they agree.

为该字段指定的 FORMAT 字符串的长度小于字段本身的长度，如 SCREEN 部分所示。

请查看屏幕布局，修改它或 FORMAT 字符串的格式以便匹配。

-2935 The number of lines specified with the '-l' option or in the screen section must be a positive integer from 6 to 600.

The vertical size of the screen, as indicated in the SCREEN statement or in the -l (lowercase L) command-line option, is out of range. Change it to specify the expected size of the terminal where the form will be used.

如 SCREEN 语句或 -l（小写L）命令行选项所示，屏幕的垂直大小超出范围。请将其更改为指定使用该表单的终端的预期大小。

-2936 The number of columns specified with the '-c' option or in the screen section must be a positive integer from 30 to 600.

The horizontal size of the screen, as indicated in the SCREEN statement or in the -c command line option, is out of range. Change it to specify the expected size of the terminal where the form will be used.

如 SCREEN 语句或 -c 命令行选项所示，屏幕的水平尺寸超出范围。将其更改为指定使用该表单的终端的预期大小。

-2940 The column name appears both with and without subscripts.

This form displays all of the indicated column, and subscripted portion of it, in different fields. You can display different, subscripted parts of a column in different fields, but the parts cannot overlap.

That is, portions of a column cannot be displayed twice on the same screen. Review all uses of the indicated column. Perhaps you did not intend to name it in both places. Perhaps two or more columns of the same name exist in different tables, and you need to use the table name to distinguish them. Otherwise, use nonoverlapping subscripts on each field of the column.

该表单在不同的字段中显示所有指示的列和其下标部分。可以在不同字段中显示不同字段的下标部分，但该部分不能重叠。也就是说，列不能在同一屏幕上显示两次。查看指定列的所有用法。也许您不打算在这两个地方都命名它。也许在不同的表中有两个或多个同名的列，您需要使用表名区分它们。否则，请在列的每个字段上使用不重叠的下标。

-2941 name is not a display field name on the form.

This statement refers to a field as name, but no such name is defined.

Check the spelling, and review the ATTRIBUTES section to see how the field was defined.

该语句引用字段的名称，但没有定义这样的名称。请检查拼写，并查看 ATTRIBUTES 部分，查看该字段是如何定义的。

-2943 You have exceeded the pseudo machine capacity.

The expression in this statement is too complex to process. Simplify it, and recompile the form. (See also error message -2988.)该语句中的表述太复杂，无法处理。请简化它，并重新编译表单。（另请参阅错误消息 -2988。）-2944 You may apply the after add, update, query, or remove commands to a table only -- not a column.

The operations of Add, Update, Remove, and Query all apply to whole rows. Consequently, these control blocks must list only table names,not names of individual columns, in their opening command. Review the names in this statement, and change column names to the names of their tables.

Add、Update、Remove 和 Query 操作会应用于整行。因此，这些控制块必须在其打开命令中仅列出表名，而不是单个列的名称。请查看此语句中的名称，并将列名更改为它的表的名称。

-2945 You may apply the after add, update, query, or remove commands to a table only -- not a column.

Aggregates (AVG, MIN, MAX, COUNT, TOTAL) can only be performed on fields that are associated with tables (not on DISPLAYONLY fields), and the tables must be listed in the opening command of the same control block. Revise the form specification, and recompile.

聚集（AVG、MIN、MAX、COUNT、TOTAL）只能在与表关联的字段上执行（而不是在 DISPLAYONLY字段中），并且必须在同一控制块的打开命令中列出表。请修改表单规范并重新编译。

-2946 You may not calculate an aggregate on the display-only field name.

Aggregates can only be performed on fields that are associated with tables (not on DISPLAYONLY fields), and the tables must be listed in the opening command of the same control block. Revise the form specification, and recompile.

只能在与表关联的字段（不在 DISPLAYONLY 字段中）上执行聚集函数，并且必须在同一控制块的打开命令中列出表。请修改表单规范并重新编译。

-2950 The column name has no section which starts at 1. Remember that the first subscript is one, not zero.

Multiple substrings from the same column are assigned to display fields. However, the substrings do not cover adjacent, nonoverlapping portions of the column. Either there is no first section (starting from column 1), or one section overlaps another. Review the substrings that are specified. Consider using a multiline edit field instead of a group of substrings; it is simpler to code and provides better editing for data entry.

来自同一列的多个子字符串被分配给显示字段。但是，子串不包括列的相邻非重叠部分。要么没有第一部分（从第 1 列开始），要么一部分与另一部分重叠。请检查指定的子字符串。考虑使用多行编辑字段而不是一组子字符串；这样编程更简单，并能提供更好编辑方式。

-2951 The left and right delimiters must be specified in a two character string.

The DELIMITERS instructions require a string of exactly two characters,the left and right delimiter (marker) characters to be used when displaying fields. The characters can be the same, but there must be two of them.

DELIMITERS 指令需要一个正好包含两个字符的字符串，即显示字段时要使用的左右分隔符（标记）字符。角色可以相同，但必须有两个角色。

-2952 In order to use a picture, the picture length must be the same as the display field length.

The string that is specified with the PICTURE attribute must have exactly the same length as the field as depicted in the SCREEN section.

Review the definition of this field, and make the two lengths agree.

使用 PICTURE 属性指定的字符串必须与 SCREEN 部分中描述的字段的长度完全相同。

请检查这个字段的定义，并使这两个长度一致。

-2953 The name name is not a database column in this form.

All the columns that are named in a COMPOSITES list must be defined in the ATTRIBUTES section. Check the spelling of all the names, and make sure that they have been defined.

所有在 COMPOSITES 列表中命名的列必须在 ATTRIBUTES 部分中定义。检查所有名称的拼写，并确保它们已被定义。

-2954 You have exceeded the maximum of number control instructions.

The INSTRUCTIONS section of this form has exceeded the ability of the form compiler to handle it. Remove some instructions to simplify the form.

此表单的 INSTRUCTIONS 部分超出了表单编译器处理它的能力。请删除一些说明以简化表单。

-2955 The name field-tag is not a displayed field in this form.

The name that is shown appears in the ATTRIBUTES section but nowhere in the SCREEN section. Check the spelling of the name; it is wrong in one of those places, or it has been omitted from the screen layout.

显示的名称出现在 ATTRIBUTES 部分，但没有在 SCREEN 部分中出现。请检查名称的拼写；它其中一个地方是错误的，或者已在屏幕布局中省略它。

-2956 You may not set display field field-tag to a value because none of its associated database columns belong to the same table as table, nor is it a variable display-only field.

You cannot assign values in a LET statement across tables. All columns that are associated to the field-tag in a LET statement must belong to tables that are named in the opening command of the control block, or it must be a display-only field.

您不能在 LET 语句中跨表分配值。与 LET 语句中的 field-tag 关联的所有列必须属于在控制块的打开命令中命名的表，或者它必须是 display-only 字段。

-2957 You may not set the next field to that-tag because none of its associated database columns belong to the same table as this-tag.

The field that is named in a NEXTFIELD statement must be associated with the same table as the current field. Review the relationships between columns and tables in this form, and revise it.

在 NEXTFIELD 语句中命名的字段必须与当前字段相同的表关联。请检查这种形式的列和表之间的关系，并对其进行修改。

-2958 You may have a maximum of ten parameters in a C-function.

This improper call to an external C function has too many parameters.

Find some way to pass the same information in fewer parameters.

这种对外部 C 函数的错误调用具有太多参数。找到某种方法以更少的参数传递相同的信息。

-2959 Two tables may join with a maximum of limit column pairs,including all components of composite columns.

A limit exists on the number of columns that are involved in a join.

This limit includes both the join columns that are named in an ATTRIBUTES statement and those that are named in a COMPOSITES statement for the same table.

连接中涉及的列数存在限制。此限制包括在 ATTRIBUTES 语句中命名的连接列和在同一个表的 COMPOSITES 语句中命名的连接列。

-2970 The column name joins with other columns, but it is not indexed.

It is recommended that columns be indexed for cross-table queries.

Performance will be much improved by creating an index.

The presence of an index on at least one of the columns that are involved in a join can make join operation much faster. However, an index is not required when one or both tables are small (dozens of rows). Consider creating an index on all join columns before you put the form into production.

若参与连接的列上存在索引就可以使连接操作快得多。但是，当一个或两个表很小（几十行）时，不需要索引。在将表单投入生产之前，请考虑在所有连接列上创建索引。

-2971 This column is not a character column, and therefore cannot be subscripted.

This statement contains a subscript, a pair of numbers in square brackets, after a column name. However, the data type of the column is not CHAR, VARCHAR, or TEXT. Only such columns can be subscripted. Check that you named the correct column. If you did, check its definition in the database.

该语句在列名后面包含一个下标、一个在方括号内的数字对。但是，该列的数据类型不是 CHAR、VARCHAR 或 TEXT。只有这样的列才可以下标。请检查是否命名了正确的列。如果命名正确，请在数据库中检查它的定义。

-2972 This column cannot be right justified or zero-filled because its displayed width does not match the actual column width.

In order to use the RIGHT or ZEROFILL attributes, make sure that the field size (as depicted in the SCREEN section) is exactly the same as the width of the database column. Review this statement, the screen layout, and the definition of the table in the database to make sure these sizes agree.

为了使用 RIGHT 或 ZEROFILL 属性，请确保字段大小（如 SCREEN 部分中所示）与数据库列的宽度完全相同。检查语句、屏幕布局和数据库中表的定义，以确保这些尺寸一致。

-2973 There may be only one dominant column in a display field description.

This statement defines a join list, a list of two or more column names that are related to the same form field. In such lists, an asterisk that precedes a column name indicates that column is the dominant column in a verify join. Only one such column is allowed in any join,but this list contains two or more. Review the documentation on verify joins, and choose a single dominant table.

该语句定义了一个连接列表，它是与同一个表单字段相关的两个或多个列名称的列表。在这样的列表中，列名前面的星号表示该列是验证连接中的显性列。在任何连接中只允许有一个这样的列，但该列表包含两个或更多。请查看关于验证连接的文档，并选择一个统一的表。

-2975 The display field label tag-name has not been used.

The indicated name was defined in the SCREEN section but not in the ATTRIBUTES section. Review the tags in each section, and revise the form so that all tags are defined.

指定的名称在 SCREEN 部分定义，但没有在 ATTRIBUTES 部分中定义。请查看每个部分中的标签，修改表单以便定义所有标签。

-2976 The end of the form has been reached prematurely.

This form specification has a SCREEN section but no TABLES or ATTRIBUTES sections. Complete the form specification.

这个表单规范有 SCREEN 部分，但没有 TABLES 或 ATTRIBUTES 部分。请完成表格规范。

-2977 Table table1 cannot be a master of table table2 because they do not join.

The two tables that are named in a MASTER OF instruction must be joined. A join between tables is expressed by naming columns from both tables in one statement in the ATTRIBUTES section. Check the spelling of the table names here, and review the attribute statements.

在 MASTER OF 指令中命名的两个表必须连接。在 ATTRIBUTES 部分的一个语句中，通过在两个表中命名列来表示表之间的连接。检查表名称的拼写，并查看属性语句。

-2978 The column column1 and the column column2 cannot be joined columns because their types or lengths are different.

The columns in a join must contain data from the same domain. The fact that these columns have different types or (if they are character columns) different lengths indicates that their contents are not from the same domain. Check the spelling of the column names to make sure that you named the correct columns. Review the design of the database,and make sure that these tables are meant to be joined on these columns.

连接中的列必须包含来自同一个域的数据。这些列具有不同类型或（如果它们是字符列）不同长度，这表明它们的内容不是来自同一个域。请检查列名称的拼写以确保您命名了正确的列。检查数据库的设计，确保这些表连接了这些列。

-2984 The table identifier table is defined more than once.

Correct the statements in the TABLES section so that each table is defined just once. Possibly you have defined an alias that is the same as a real table name.

更正 TABLES 部分中的语句，以便每个表只定义一次。可能已经定义了一个与实际表名相同的别名。

-2985 The table identifiers name1 and name2 represent the same table.

In the TABLES section, these two names are defined in such a way that they refer to the same database table. One or both of them is a table alias. Change the statements so that each name stands for just one table and each table has just one name.

在 TABLES 部分中，这两个名称的定义方式使它们引用同一个数据库表。其中一个或两个都是表别名。请更改语句，以便每个名称仅代表一个表，每个表只有一个名称。

-2986 The form specification has exceeded the maximum of limit master/detail pairs.

A restriction exists on the number of master-detail pairs that can be supported in one form. You must find a way to simplify the form.

一种形式可支持的主 - 细节对的数量存在限制。您必须找到简化表单的方法。

-2987 The form specification has exceeded the maximum of limit screens.

A restriction exists on the number of screen layouts that can be supported in one form. You must find a way to simplify the form.

一种形式中可支持的屏幕布局的数量存在限制。您必须找到简化表单的方法。

-2988 FORMBUILD has run out of memory.

The form compiler cannot get enough data memory to process the form specification. You must find a way to simplify the form.

表单编译器无法获取足够的数据内存来处理表单规范。您必须找到简化表单的方法。

-2989 The column name is a reference column, but it is not indexed.

It is recommended that reference columns be indexed for lookups.

Performance will be much improved by creating an index.

You have defined the indicated column as a reference column using the LOOKUP attribute. Whenever the operator enters a value in the field, it will be looked up in this column. Such a lookup operation is quick when an index is present, but no index on the column exists at this time.

Without one, a lookup might be extremely slow. Unless the field does not allow operator input (in which case you should remove the asterisk)or the table is very small (a few dozen rows at most), you should create an index for this column before you put the form into use.

您已使用 LOOKUP 属性将指定的列定义为参考列。只要操作员在该字段中输入一个值，就会在该列中查找该值。当存在索引时，这样的查找操作很快，但此时该列上没有索引存在。如果没有索引，查找可能非常缓慢。除非该字段不允许操作员输入（在这种情况下，您应该删除星号）或者表非常小（最多几十行），在表单投入使用之前请为该列创建一个索引。

-2990 The columns column1 and column2 are not in the same database table.

All columns that are cited in a single LOOKUP attribute must belong to the same table. Check the spellings of the names, and make sure that they are the columns you intended.

在单个 LOOKUP 属性中引用的所有列都必须属于同一个表。检查名称的拼写，并确保它们是您想要的列。

-2991 Warning: Only the first screen of your multiple-screen form will be displayed under 4GL.

This warning appears when you use the 4GL forms compiler to compile a multipage PERFORM screen. A 4GL program can display only the first page of a multipage form. If the form specification has more than one SCREEN section, it has been purposely divided into multiple pages, and you will have redesign it for 4GL. If it has only a single screen layout,the 4GL forms compiler has split it into two pages because it will not fit on the screen. The form design might not allow for the four screen lines that 4GL reserves.

当您使用 4GL 表单编译器编译多页 PERFORM 屏幕时，会出现此警告。4GL 程序只能显示多页表单的第一页。如果表单规范有多个 SCREEN 部分，则它会被故意划分为多个页面，并且您将为 4GL 重新设计它。如果它只有一个屏幕布局，那么 4GL 表单编译器将其分成两页，因为它不适合屏幕。表单设计可能不允许 4GL 保留的四条屏幕线。

-2992 The display label name has already been used.

The forms compiler indicates that name has been defined twice. These names must be defined uniquely in the form specification. Review all uses of the name to see if one of them is incorrect.

表单编译器指出该名称已被定义两次。在表单规范中这些名称的定义必须是唯一的。

请查看名称的所有用法，查看其中一个是否错误。

-2993 There is a circular join path specified in the form.

This form defines a series of three or more joins such that table A joins to table B, table B joins to table C, and table C joins to table A. The circularity might not be obvious due to the use of table-alias names. Review all the statements in the ATTRIBUTES section and any COMPOSITES statements, and draw a diagram of the join relationships.

Then modify the form so that no circular joins are created.

该表单定义了一系列三个或多个连接，表 A 连接到表 B，表 B 连接到表 C，表 C 连接到表 A 。由于使用表别名，循环可能不明显。请查看 ATTRIBUTES 部分和任何 COMPOSITES 语句中的所有语句，并绘制连接关系图。然后修改表单，以便不创建循环连接。

-2994 The form has exceeded the maximum number of joins between tables.

A limit exists on the number of joins that can be specified. You must find a way to simplify the form.

能指定的连接数量有限。您必须找到简化表单的方法。

-2995 The form has exceeded the maximum number of tables contained in joins.

A limit exists on the number of tables that can be contained in one join. You must find a way to simplify the form.

一个连接中可以包含的表的数量有限。您必须找到简化表单的方法。

-2996 The unanticipated error number os-error has occurred.

Contact Technical Support.

The error number that is displayed came from the host operating system.

RDS was at one time the name of GBase 8s Software. This error should not occur. If the error recurs, note all circumstances and contact GBase Technical Support.

显示的错误号码来自主机操作系统。RDS 曾经是 GBase 8s Software 的名称。该错误不应该发生。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-2997 See error number.

The database server returned the error number that is shown. Look it up in this document. Also look for other error messages that might give more information or contact GBase Technical Support.

数据库服务器返回了显示的错误号。请在文件中查找它。另请查看可能提供更多信息的其他错误消息或联系 GBase 技术支持。

-2998 Operating system error os-error: text.

The error that is displayed came from the host operating system. This error should not occur. If the error recurs, note all circumstances and contact GBase Technical Support.

显示的错误号码来自主机操作系统。RDS 曾经是 GBase 8s Software 的名称。该错误不应该发生。

如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-2999 SQL server terminated.

The application has lost contact with the database server. Someone might have shut down the database server, or an internal error might have damaged a pipe between the application and the database server. In a local area network system, the database server process or thread in the file server might have been terminated, or the file server might be down. Look for other messages, especially operating-system messages,that might give more detail.

应用程序与数据库服务器失去联系。可能有人关闭了数据库服务器，或者内部错误可能损坏了应用程序和数据库服务器之间的管道。在局域网系统中，文件服务器中的数据库服务器进程或线程可能已被终止，或者文件服务器可能已关闭。请查找其他消息，尤其是操作系统消息，它可能提供更多详细信息。

-3000 ISAM or system error number number.

Look up the error number in the finderr utility.

使用 finderr 实用程序查找错误号。

-3001 There are no forms in the current directory.

You can run only forms that are present in the current directory or a directory that is named in your DBPATH environment variable. Change directories to the one that contains the desired forms, or change the contents of DBPATH.

您只能运行当前目录中存在的表单或 DBPATH 环境变量中命名的目录。将目录更改为包含所需表单的目录，或者更改 DBPATH 的内容。

-3002 There are no BLOB fields to view.

You selected the View menu option. This option lets you view the contents of TEXT and BYTE fields of a form, but this form has none.

您选择了“View”菜单选项。该选项可让您查看表单的 TEXT 和 BYTE 字段的内容，但此表单没有该选项。

-3003 This BLOB field is empty.

You selected the View menu option. The cursor is positioned in a field that represents a BYTE column, and you pressed the ! key to edit the contents of the field. However, the field is null; no data exists to view. Use Query to select a row that includes nonnull data in this field.

您选择了“View”菜单选项。游标位于表示 BYTE 列的字段中，并且您按下 ! 键编辑该字段的内容。

但是，该字段为空；没有数据可供查看。使用 Query 选择此字段中的非空数据的行。

-3005 You do not have permission to access the form form-name.

The form file form-name does exist; however, your account does not have operating-system permissions to read and write it.

表单文件 form-name 确实存在；但是，您的账户没有操作系统权限来读取和写入它。

-3006 An unknown code has been found in the .frm file. Recompile your form before running it again.

Recompile the form to make sure that the .frm file has not been corrupted. If the same error occurs, check that you are running FORMBUILD and PERFORM products at the identical version level (version numbers are displayed when the commands are executed from the command line if you do not use the -s option). If the error recurs, note all circumstances and contact GBase Technical Support.

重新编译表单以确保 .frm 文件未被损坏。如果发生相同的错误，请检查您是否在相同版本级别运行 FORMBUILD 和 PERFORM 产品（如果不使用 -s 选项，则在命令行执行命令时显示版本号）。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-3007 Your form is incompatible with the current version of PERFORM. Recompile your form before running it again.

Use FORMBUILD to compile the form, then run PERFORM again.

使用 FORMBUILD 编译表单，然后再次运行 PERFORM。

-3010 Database database-name not found.

The database that is named in the DATABASE section of the form could not be opened. Either it could not be found, or your account has not been granted CONNECT privilege for it. You can use GBase 8s SQL to separate these cases. Use Select option from the Database menu. If database-name is listed, the database can be found but could not be opened.

无法打开在表单的 DATABASE 部分中命名的数据库。可能是找不到，或是您的账户没有被授予 CONNECT 权限。可以使用 GBase 8s SQL 分离这些情况。使用 Database 菜单中的 Select 选项。如果列出数据库名称，则能找到数据库但无法打开。

The database server looks for a database first in the current directory and then in directories that are named in the DBPATH environment variable. Check to see if database-name.dbs exists in one of those directories.

数据库服务器首先在当前目录中查找数据库，然后在 DBPATH 环境变量中指定的目录中查找数据库。请检查一下这些目录中是否存在 database-name.dbs。

-3011 A table is locked -- no reading or writing is permitted.

Because another user has locked a table in exclusive mode, PERFORM cannot continue. Rerun the transaction when the table is not locked.

由于另一个用户以互斥模式锁定表，PERFORM 无法继续。表未被锁定时重新运行事务。

-3019 Unanticipated error number has occurred; call Technical Support.

Note all circumstances and contact GBase Technical Support.

请记录所有的情况并联系 GBase 技术支持。

-3020 The table table-name is not in the database. Build your form again.

A table that is listed in the TABLES section of the form cannot be found. Review the DATABASE statement to ensure that the form is using the correct database. If so, and if the table name is spelled as you intended, the table has been dropped or renamed. You can use GBase 8s SQL to check table names under Info selection in the Tables menu. Revise the form to use the correct name.

无法找到表单 TABLES 部分列出的表。查看 DATABASE 语句以确保表单使用正确的数据库。

如果正确，并且表名拼写正确，则该表已被删除或重命名。您可以使用 GBase 8s SQL 检查 Info Table 的信息。请修改表单，使用正确的名称。

-3030 The column column-name is not in the database. Build your form again.

The tables that are specified in the TABLES section of the form do exist, but the column column-name, which was named in the ATTRIBUTES section, does not. Check the spelling of column-name against the actual table. The table might have been altered, or the column may have been renamed. You can use GBase 8s SQL to check column names under Info selection in the Tables menu. Revise the form to use the correct column name.

表单 TABLES 部分中指定的表确实存在，但 ATTRIBUTES 部分中命名的列 column-name 不存在。请检查列名与实际表的拼写。该表可能已被更改，或该列可能已被重命名。您可以使用 GBase 8s SQL 检查“Tables”菜单中“Info”选项下的列名称。请修改表单，使用正确的名称。

-3031 The form form-name cannot be found or opened.

PERFORM cannot locate the compiled form form-name.frm in the current directory or in a directory that is named in the DBPATH environment variable. Or if it did find the file, it could not open it. Check the spelling of the name. Verify that the file exists, and check that your account has read access to it.

PERFORM 无法在当前目录或在 DBPATH 环境变量中命名的目录中找到编译后的表单 form.name.frm。或者如果它的确找到了文件，但无法打开它。请检查名称的拼写。验证文件是否存在，并检查您的账户是否具有对其的读取权限。

-3035 The column column-name has changed column type. Build your form again.

The column column-name, which is named in the ATTRIBUTES section of the form, no longer has the data type that it had when the form was compiled (the table has been altered since). Check the present data type; then examine the form specification to make sure that it will display the column in a field of the appropriate size. Modify the form as required, and rebuild it.

在表单 ATTRIBUTES部分中命名的列 column-name 不再具有编译表单时所具有的数据类型（表已被更改）。检查当前的数据类型；然后检查表单规范以确保它将在适当大小的字段中显示该列。根据需要修改表单并重建它。

-3037 The column column-name is not a composite column. Build your form again.

The column column-name is mentioned as part of a COMPOSITE in the INSTRUCTIONS section of the form specification. However, no composite index (an index over all the columns of a composite key) exists over this column and its fellows in the database. After the form was compiled, the composite index was dropped. Either it should be restored, or the form should be revised.

列 column-name 是作为表单规范的 INSTRUCTIONS 部分中的 COMPOSITE 的一部分提及的。但是，此列和数据库中的其它列不存在索引（对组合键的所有列的索引）。

表单编译完成后，组合索引被删除。要么恢复该索引，要么修改表单。

-3050 Operating system error. Cannot open a temporary file.

PERFORM is trying to open a temporary file that it created earlier.

Look for operating-system error messages that might give more information. Possibly you have exceeded a limit on the number of open files. If the error recurs, note all circumstances and contact GBase Technical Support.

PERFORM 试图打开它之前创建的临时文件。查找可能提供更多信息的操作系统错误消息。

可能您已经超过了打开文件数量的限制。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-3060 Operating system error. Cannot create a temporary file.

PERFORM is trying to create a temporary file but cannot. On UNIX systems, check that your account is allowed to write in the /tmp directory or the directory that is named in the DBTEMP environment variable and that the directory is not full. Possibly you have exceeded an operating-system limit on the number of open files. In that case,you will have to reduce the number of tables that are used in this form.

PERFORM 试图创建一个临时文件，但失败。在 UNIX 系统上，检查是否允许您的账户户写入 /tmp 目录或 DBTEMP 环境变量中指定的目录，并且该目录未满。可能您已经超出了打开文件数量的操作系统限制。在这种情况下，您将不得不减少在该表单中使用的表的数量。

-3081 The specified output file name has a bad extension.

The output filename cannot end in any of the following suffixes:.dat, .idx, .aud, .per, .frm, .ace, .arc, .sql, or .unl.

输出文件名不能以任何以下后缀结尾：.dat、.idx、.aud、.per、.frm、.ace、.arc、.sql 或 .unl。

Select a different filename.

选择不同的文件名。

-3082 No program specified to edit this BYTE field.

The form user has keyed! in the display of a BYTE field. However, no program= attribute was defined for this field.

表单用户在显示 BYTE 字段的中键入！。但是，该字段没有定义 program= attribute。

-3101 The column column-name does not allow null values.

When you added data to a table, you did not specify data for the column shown. However, that column is defined in the database as not allowing null values. You cannot add the row unless you supply a value.

将数据添加到表时，您没有为显示的列指定数据。但是，该列在数据库中定义为不允许空值。

除非您提供值，否则不能添加该行。

-3120 Error in field.

The data that is entered into the current field is not appropriate for the data type of the field.

输入到当前字段的数据不适合该字段的数据类型。

-3200 There are no rows in the current list.

You must first query the table before you execute the UPDATE, REMOVE,NEXT or PREVIOUS command.

在执行 UPDATE、REMOVE、NEXT 或 PREVIOUS 命令之前，必须先查询表。

-3210 The current row position contains a deleted row.

Another user has just deleted the row now displayed. That row no longer exists. You cannot use the UPDATE, REMOVE, NEXT, or PREVIOUS commands until you use QUERY to display a valid row.

另一位用户刚刚删除了现在显示的行。该行不再存在。在使用 QUERY 显示有效行之前，不能使用 UPDATE、REMOVE、NEXT 或 PREVIOUS 命令。

-3260 This is an invalid value -- it does not exist in table-name table.

This column has a verify join with a column in table table-name. Any value that is entered in this field must be found in that table. The value just entered was not found. Enter a correct value.

该列与表 table-name 中的列进行验证连接。任何在此字段中输入的值都必须能在该表中找到。刚刚输入的值未找到。请输入一个正确的值。

-3261 Invalid value -- its composite value does not exist in table-name table.

This column is listed with others as a COMPOSITE in the INSTRUCTIONS section of the form specification. It is shown there as needing to be verified against matching columns of table table-name. The value you have entered, considered with the other values in the composite, does not occur in table-name.

在表单规范的 INSTRUCTIONS 部分中，此列与其他列一起作为一个 COMPOSITE 列出。

它显示在那里，因为需要根据表名的匹配列进行验证。您输入的值会与组合中的其它值一起考虑，它们不会出现在表名中。

-3265 A required index on column-name is missing. Restore.

All dominant columns (those with asterisks before their names) in verify joins must be indexed. Perhaps the index has been dropped since the form was compiled. Re-create the index, and run the form again.

在验证连接中的所有显性列（名称前带星号的列）必须进行索引。自从编译表后，该索引可能已经被删除。请重新创建索引，然后再次运行表单。

-3300 There are no more rows in the direction you are going.

You reached the beginning or the end of the current list of rows. You can start a new query with the QUERY command, or use the PREVIOUS or NEXT command to reverse through the list the other way.

您已到达当前行列表的开始或结尾。可以使用 QUERY 命令启动新的查询，或者使用 PREVIOUS 或 NEXT 命令以其他方式反转列表。

-3400 There are no rows satisfying the conditions.

No rows in the database match the values that are entered in the form.

Enter different values, and query again.

在数据库没有行与表单中输入值匹配。请输入不同的值，然后再次查询。

-3420 This value is not among the valid possibilities.

A list or range of acceptable values has been established for this column (via an INCLUDE attribute in the form-specification file). You must enter a value within the acceptable range.

已经为该列建立了可接受值的列表或范围（通过格式规范文件中的 INCLUDE 属性）。

您必须输入一个在可接受的范围内的值。

-3421 The joined field table.column cannot be selected by the current user.

This form queries the column in the table shown in joining two tables.

However, your account name does not have SELECT privilege for that table and column. Contact the owner of the table or a Database Administrator to be given this privilege.

该表单查询两表连接中显示的列。但是，您的账户名称对该表和列没有 SELECT 权限。

请联系表的所有者或数据库管理员以获得此权限。

-3430 This field requires an entered value.

The row cannot be added to the table until a value has been entered in the indicated field. A REQUIRED attribute in the form-specification file has been associated with the column. Enter a value in the field.

只有在指定字段中输入值后，该行才能添加到表中。表单规范文件中的 REQUIRED 属性已与列关联。请在该字段中输入一个值。

-3450 Someone else has deleted a row which is in your list.

Another user, accessing a table that is queried by your form, has deleted a row that your latest query selected. Restart your query to get an accurate selection of rows. ou query a view. Early versions of the product did not support views.

另一个用户访问表单查询的表，已删除最近查询选定的行。重新启动您的查询以获得行的精确选择。

-3451 This form has no fields requiring data entry.

None of the fields in this form specification permit data entry; they are all marked as either LOOKUP or DISPLAYONLY without the ALLOWING INPUT keywords.

本表单中没有字段允许数据输入；它们都被标记为 LOOKUP 或 DISPLAYONLY，但没有ALLOWING INPUT 关键字。

-3452 Add, Update and Remove operations not allowed on a remote table.

The table that is being queried is in a database that is external to the current database (the one that is named in the DATABASE section of the form). Such tables cannot be modified.

被查询的表位于当前数据库（在表单的 DATABASE 部分中命名的数据库）外部的数据库中。

不能修改这些表。

-3460 This row has been locked by another user -- try again later.

Another individual is currently using the table. Wait a few moments,and reenter your statement.

另一个人正在使用该表。请稍等，然后重新输入您的语句。

-3500 The two entries were not the same. Try again.

To guard against typographical errors, you must enter the value in this field twice. The values that are entered must be identical. Carefully reenter the data. (A VERIFY attribute in the form-specification file has been associated with this column.)为了防止印刷错误，您必须在该字段中输入两次值。输入的值必须相同。注意重新输入数据。（表单规范文件中的 VERIFY 属性已与此列相关联。）-3600 No detail table has been specified for this table.

You must first establish this table as the master of another table in the INSTRUCTIONS section of the form.

您必须首先在表单的 INSTRUCTIONS 部分中将此表建立为另一个表的主数据表。

-3610 No master table has been specified for this table.

You must first establish this table as the detail of another table in the INSTRUCTIONS section of the form.

您必须首先在表单的 INSTRUCTIONS 部分中将此表建立为另一个表的详细信息。

-3620 You do not have permission to write into this table.

You do not have insert or update privilege for the table, so you cannot insert or update a column. Check with the owner of the table or the person who has Database Administrator (DBA) privilege for the database for the necessary permission.

您没有该表的插入或更新权限，因此无法插入或更新列。请联系表的所有者或具有数据库管理员（DBA）权限的人员，以获得必要的权限。

-3630 Operating system error. Cannot write into a temporary file.

PERFORM earlier created a temporary file but now cannot write into it.

The most likely cause of this error is that the disk has filled up.

Alternatively, another user might have deleted the temporary file after it was created.

PERFORM 之前创建了一个临时文件，但现在无法写入它。此错误最可能的原因是磁盘已满。或者，另一个用户可能在创建临时文件后又删除了该临时文件。

-3650 You must first remove table-name rows which join this row.

The row you wish to remove is the dominant member of a verify join. You cannot remove this row without first removing any rows that join it.

您希望删除的行是验证连接的主要成员。如果不先删除连接它的任何行，则无法删除此行。

-3651 You have exceeded the number of opened tables allowed by your system.

Executing the statement would require that PERFORM exceed an operating system limit on the number of open files. You will have to reduce the number of tables that are included in the form specification.

执行该语句会要求 PERFORM 超出操作系统对打开文件数量的限制。您将不得不减少表单规范中包含的表的数量。

-3660 You must first update table-name rows which join this row.

The row you wish to update is the dominant member of a verify join. You are not allowed to change a row value in this column that would invalidate joined rows in other tables. You must first update the rows in table-name that join this column.

您希望更新的行是验证连接的主要成员。您不允许更改此列中的行值，这会使其它表中的连接行无效。必须首先更新连接该列的 table-name 中的行。

-3670 Operating system error. Cannot seek into a temporary file.

Earlier PERFORM created a temporary file; now it cannot change the file position in that file. Perhaps another user deleted the file after it was created. Look for messages from the operating system that might give more detail on the problem.

早期的 PERFORM 创建了一个临时文件；现在它不能更改该文件中的文件位置。也许其他用户在创建后删除了该文件。请从操作系统中查找可能提供有关此问题更多详细信息的消息。

-3680 PERFORM has run out of memory.

PERFORM cannot get the memory data space it needs. You will have to reduce the complexity of the form.

PERFORM 无法获取所需的内存数据空间。必须降低表单的复杂性。

-3690 Detail cannot be executed -- tables first and second do not join.

A master-detail relationship for these two tables is specified in the INSTRUCTIONS section of the form. However, the two tables do not join.

Add a join attribute in the ATTRIBUTES section.

在表单的 INSTRUCTIONS 部分中指定了这两个表的主 - 副关系。但是，这两张表不会连接。

请在 ATTRIBUTES 部分添加一个连接属性。

-3700 Permission not granted to allow reading of table-name.

Your account has not been granted SELECT privilege for the table table-name. The owner of the table, or a person who has Database Administrator (DBA) privilege for the database, can grant this privilege level to you.

您的账户尚未被授予表 table-name 的 SELECT 权限。表的所有者或具有数据库的数据库管理员（DBA）权限的人员可以授予您此级别的权限。

-3710 Permission not granted to allow update of table-name.

Your account has not been granted UPDATE privilege for the table table-name. The owner of the table, or a person who has Database Administrator (DBA) privilege for the database, can grant this privilege level to you.

您的账户尚未被授予表 table-name 的 UPDATE 权限。表的所有者或具有数据库的数据库管理员（DBA）权限的人员可以授予您此级别的权限。

-3720 Permission not granted to allow add of table-name.

Your account has not been granted INSERT privilege for the table table-name. The owner of the table, or a person who has Database Administrator (DBA) privilege for the database, can grant this privilege level to you.

您的账户尚未被授予表 table-name 的 INSERT 权限。表的所有者或具有数据库的数据库管理员（DBA）权限的人员可以授予您此级别的权限。

-3730 Permission not granted to allow remove of table-name row.

Your account has not been granted DELETE privilege for the table table-name. The owner of the table, or a person who has Database Administrator (DBA) privilege for the database, can grant this privilege level to you.

您的账户尚未被授予表 table-name 的 DELETE 权限。表的所有者或具有数据库的数据库管理员（DBA）权限的人员可以授予您此级别的权限。

-3731 Cannot open the table table-name.

The database server cannot open the file that represents this table.

You might have exceeded an operating-system limit on open files; if that is the case, you will have to reduce the number of tables that are included in the form. However, first make sure that a file exists for this table in the database directory (its name is database-name.dbs)and that your account has read access to it. The name of the table file is composed of table-name, a 3-digit number, and the suffix .dat.

数据库服务器无法打开代表此表的文件。您可能已经超过了打开文件的操作系统限制；如果是这种情况，必须减少表单中包含的表数量。但是，首先确保数据库目录（其名称为 database-name.dbs）中该表的文件存在，并且您的账户具有对其的读取访问权限。表文件的名称由表名、3 位数字和后缀.dat组成。

-3750 Command aborted.

No current GBase 8s product returns this message. If the error recurs,note all circumstances and contact GBase Technical Support.

当前 GBase 8s 产品不会返回此消息。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-3751 Type carriage return to continue.

No current GBase 8s product returns this message. If the error recurs,note all circumstances and contact GBase Technical Support.

当前 GBase 8s 产品不会返回此消息。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-3752 You cannot use this editing feature because a picture exists.

定义此字段（在 form-specification 文件中）具有 PICTURE 属性，以此来指定它的格式。

在编辑这样的字段时，您不能使用某些编辑键（例如：CTRL-A、CTRL-D 和 CTRL-X）。只能使用可打印的字符和退格键输入值。

-3754 You have exceed the pseudo machine stack space.

Reduce the complexity of the form. In particular, reduce the level of nesting of loops and IF statements, and break very complicated expressions in LET statements up into simpler ones.

减少表单的复杂性。特别是，降低循环和 IF 语句的嵌套级别，并将 LET 语句中非常复杂的表达式分解为更简单的表达式。

-3755 The selected display-only field tagname cannot be accessed.

The field tag name that is passed to the C function pf_nxfield() is the name of a display-only field. Because the user is not allowed to enter data in a display-only field, the cursor cannot be located in one.

Check the tag name that is supplied; if it is the one that you intended, review the attributes of that field, and find out why it has been set display-only.

传递给 C 函数 pf_nxfield() 的字段标签名称是 display-only 字段的名称。由于不允许用户在 display-only 字段中输入数据，所以光标不能位于其中。请检查提供的标签名称；如果它是想要的标签，请查看该字段的属性，并找出它被设置为 display-only 的原因。

-3756 The selected field tag-name cannot be assigned a value at this time.

The specified field is not in the current table. The cursor is not allowed to enter such fields, and values cannot be set in them.

指定的字段不在当前表中。游标不允许输入这些字段，并且不能在其中设置值。

-3757 A conversion error has occurred for the field tag-name.

The data type of the value that is passed to pf_putval() could not be converted into the data type of the screen field tag-name. Review the value and the valtype flag versus the data type of the field in the form definition.

传递给 pf_putval() 的值的数据类型无法转换为屏幕字段标签名的数据类型。

请在表单定义中查看值和 valtype 标志与字段的数据类型。

-3758 The next selected field tag-name is not in the current table.

The field tag name that is passed to the C function pf_nxfield() is the name of a field that is not in the current table. The cursor is not allowed to enter such fields.

传递给 C 函数 pf_nxfield() 的字段标签名称不是当前表中的字段名。因此，游标不允许输入这些字段。

-3759 The display field field-name does not exist in the form.

The field tag name that is passed to the C function pf_nxfield() is not defined in this form. Review the string that is passed; if it is as you intended, inspect the form definition to see what has been changed. A common error is to confuse the tag name, which is used in the screen layout and to the left of the equal sign in the ATTRIBUTES section,with the field name, which is the column name used to the right of the equal sign in the ATTRIBUTES section. The latter is used when referring to fields.

传递给 C 函数 pf_nxfield() 的字段标签名称未在此表单中定义。请检查传递的字符串；如果它符合您的要求，请检查表单定义以查看已更改的内容。一个常见的错误是将在屏幕布局中使用的标记名称和 ATTRIBUTES 部分中等号的左侧的标记名称及字段名称混淆，字段名称是在 ATTRIBUTES 部分中等号右边使用的列名称。当引用字段时，使用后者。

-3760 Matching may not be used between non-character fields or expressions.

An IF-THEN-ELSE statement in the INSTRUCTIONS section of the form uses the keyword MATCHES to compare two fields. However, at least one of the fields is not a character field, and you can use MATCHES only with character fields. Review all uses of MATCHES in the INSTRUCTIONS section to make sure it is applied only to character fields.

表单 INSTRUCTIONS 部分中的 IF-THEN-ELSE 语句使用关键字 MATCHES 比较两个字段。但是，至少有一个字段不是字符字段，您只能在字符字段中使用 MATCHES。请在 INSTRUCTIONS 部分查看 MATCHES 的所有用法，以确保它仅适用于字符字段。

-3761 ERROR -- attempt to divide by zero has occurred.

A division expression in the INSTRUCTIONS section has a zero divisor.

Review all uses of division in the INSTRUCTIONS section, and look for any that might have a denominator of zero (possibly the denominator is a field into which the user entered a zero). Protect these expressions with tests for zero using IF-THEN-ELSE.

INSTRUCTIONS 部分中的除法表达式的除数为零。请查看 INSTRUCTIONS 部分中所有除法的用法，并查找一个分母为零的分子（可能分母是用户输入零的字段）。

使用 IF-THEN-ELSE 保护这些表达式。

-3762 The user function funcname defined in the form could not be found in the C function definition table userfuncs.

The INSTRUCTIONS section of the form includes a call to a function funcname, and sperform assumes that this is the name of an external C function. However, the name and address of each such function must appear in a static array that is named userfuncs. That array, along with the computer code of the external functions, is linked with a custom version of sperform. Because name did not appear in the array,sperform cannot call it.

表单的 INSTRUCTIONS 部分包含对函数 funcname 的调用，并且 sperform 假定这是外部 C 函数的名称。但是，这样函数的名称和地址必须出现在名为 userfuncs 的静态数组中。该数组以及外部函数的计算机代码与自定义版本的 sperform 链接。由于名称未出现在数组中，因此 sperform 无法调用它。

Check that you are executing the correct, customized version of sperform (the original version of the program has no external functions linked to it). Check to see if funcname is correctly spelled. Then examine the source of the C functions to make sure that the userfuncs array is defined correctly.

检查您是否正在执行正确定制版本的 sperform （没有外部函数连接到原始版本的程序）。

请检查 funcname 是否拼写正确。然后检查 C 函数的来源以确保 userfuncs 数组的定义正确。

-3763 This program has an invalid serial number. Consult your installation instructions.

The GBase 8s software product has been improperly installed. Review the installation procedure. If you need help, contact GBase Technical Support.

GBase 8s 软件产品安装不正确。请检查安装过程。如果需要帮助，请联系 GBase 技术支持。

-3764 Screen too small. Must be at least 6 lines and 30 columns.

PERFORM cannot operate in a screen or window that is smaller than 6 lines by 30 columns. You must increase the size of the terminal window in which you are executing PERFORM. The absolute minimum is 6 lines by 30 columns. However, the window must also be large enough to contain the form that will be displayed.

PERFORM 无法在小于6 行乘 30 列的屏幕或窗口中运行。您必须增加执行 PERFORM 的终端窗口的大小。最小绝对值是 6 行乘 30 列。但是，该窗口还必须足够大以包含要显示的表单。

-3765 Form image too large to fit in the screen window.

The screen image as defined in the form file is larger (either wider or taller) than the dimensions of the current window. If the current window is the main window, its size is set by the dimensions of the terminal in use. If the current window was opened with OPEN WINDOW, you should specify more rows or columns. Review the form file, and either reduce the size of the screen image or display it as a bigger window.

表单文件中定义的屏幕图像比当前窗口的尺寸大（更宽或更高）。如果当前窗口是主窗口，则其大小由正在使用的终端的尺寸设置。如果当前窗口是用 OPEN WINDOW 打开的，则应该指定更多的行或列。

请查看表单文件，并减小屏幕图像的大小或将其显示为更大的窗口。

-3766 Usage: SPERFORM [-s] [-d database] filename . . .

This message displays the command-line option of the sperform program.

此消息显示 sperform 程序的命令行选项。

-3767 An unknown option option name was found on the command line.

Make sure that you typed the correct command-line option.

确保您输入了正确的命令行选项。

-3999 System internal error in file filename at line number.

This error should not occur. If the error recurs, note all circumstances and contact GBase Technical Support.

这个错误不应该发生。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-4000 Intrinsic member functions cannot be declared as SHARED.

This statement attempts to declare one of the intrinsic members of this class (the class constructor, or the !copy() or !derive() function) as SHARED. You can declare these functions in order to extend them, but the declaration cannot specify SHARED.

该语句试图声明这个类中的内部成员（类构造函数或 !copy() 或 !derive() 函数）为 SHARED。

您可以声明这些函数以扩展它们，但声明不能指定 SHARED。

-4001 Fundamental type name "type" cannot be used as a class name.

This CLASS statement attempts to declare a class with the same name as a built-in data type such as INTEGER. Find a different name for your class.

此 CLASS 语句尝试声明与内置数据类型（如 INTEGER ）相同名称的类。请为您的类声明不同的名称。

-4002 Argument n of function "name" is not convertible to its formal parameter's type.

The indicated argument expression or default argument expression is not compatible with the declared type of that function argument. Review the declaration of the function to see what type is expected.

指定的参数表达式或默认参数表达式与该函数参数的声明类型不兼容。请检查函数的声明以查看预期的类型。

-4004 Member "name" of class "class-name" cannot be accessed in this context.

The compiler is aware of the member, but the access control for the member makes it inaccessible in the statement. Check for a PUBLIC,PRIVATE, or PROTECTED declaration. Member variables default to PROTECTED access, but member constants and member functions default to PUBLIC.

编译器知道该成员，但成员的访问控制使其无法在语句中访问。检查 PUBLIC、PRIVATE或 PROTECTED 声明。成员变量默认为 PROTECTED 访问，但成员常量和成员函数默认为 PUBLIC。

-4005 You cannot redefine private base member function "name".

This FUNCTION declaration in a class declaration names a member that is inherited from a base class of this class. However, that inherited name is declared as PRIVATE, so it cannot be overridden in this class.

Review the declarations of all base classes; then choose a name for your function that will be unique to this class.

类声明中的 FUNCTION 声明指定了从此类的基类继承的成员。但是，继承的名称被声明为PRIVATE，因此它不能在此类中重写。请检查所有基类的声明；然后为您的函数选择一个名称，该名称对于此类是唯一的。

-4007 Record member "name" is undefined.

This statement refers to record.name. While the variable record is indeed a record, name is not the name of one of its component fields.

Find the definition of record (it might be in the GLOBALS file), and verify the names of its fields. Then correct the spelling of name.

该语句引用了 record.name。虽然变量记录确实是一条记录，但 name 不是其中一个组件字段的名称。找到记录的定义（可能在 GLOBALS 文件中），验证其字段的名称。然后更正name 的拼写。

-4009 Non-shared member "name" cannot be used in default values.

A default value expression in this function declaration refers to the value of a normal member variable of this class. This action is not supported. Default value expressions can refer to variables, but they must be declared at the module level or be shared members of classes.

函数声明中的缺省值表达式引用了该类的普通成员变量的值。不支持该操作。

缺省值表达式可以引用变量，但是它们必须在模块级声明或者是类的共享成员。

-4010 Include file "pathname" is not found.

This INCLUDE statement names a file that the compiler cannot find. If a complete pathname is used, the file does not exist. Check the spelling of all the directories and the filename. If only a filename is given,that file could not be found in the current directory, in$GBS_HOME/incl, or in any directory that is specified in a -H compiler argument. Perhaps one of these arguments was omitted or misspelled.

该 INCLUDE 语句命名了一个编译器找不到的文件。如果使用完整的路径名，那么该文件不存在。

请检查所有目录和文件名的拼写。如果仅给出文件名，那么在当前目录、$GBS_HOME/incl中或在 -H 编译器参数中指定的任何目录中都找不到该文件。也许是因为其中之一的参数被忽略或拼写错误。

-4011 Class "name" is not declared.

This statement refers to a class of the indicated name, but no such class has been declared to this point in the source module. Check the spelling of the name. Make sure that all desired include files have been included.

该语句引用了一个指定名称的类，但是在源模块上没有声明这样的类。请检查名称的拼写。

确保包含了所有需要包含的文件。

-4012 You can only specify a base clause for class constructors.

This function declaration is followed by a colon, class-name, and argument list (in short, a base clause). This syntax is used only when declaring the constructor function for a class (the function whose name is the same as the name of the class), in order to specify function arguments to the constructor of the base class.

该函数声明后面跟着一个冒号、类名和参数列表（简而言之，是一个基本子句）。此语法仅用于为类声明构造函数（函数的名称与类的名称相同），以便为基类的构造函数指定函数参数。

-4013 Invalid intrinsic member function "!name".

The supported intrinsic member functions are !copy(), !derive(), and the class-name (the constructor). No other functions can be declared with an initial exclamation mark. Check the spelling of name. If it is not one of the supported names, declare the function as a normal member function.

支持的内部成员函数是!copy()、!derive()和类名称（构造函数）。其它函数不能用感叹号来声明。请检查名称的拼写。如果它不是支持的名称，则将该函数声明为普通成员函数。

-4014 You cannot specify the RETURNING type for intrinsic member functions.

This declaration of an intrinsic member function includes a RETURNING clause. This action is not supported. The compiler defines the returned value from an intrinsic member function. Omit the RETURNING clause.

内部成员函数的声明包含 RETURNING 子句。不支持此操作。编译器定义从内部成员函数返回的值。请省略 RETURNING 子句。

-4016 Each class declaration must have at least one member function.

This class declaration contains no member functions. A class must contain at least one, because the point at which the first (or only)member function is defined is also the point at which the class itself is defined. If the class has no other members, declare its constructor function. Because the constructor is declared, it must also be defined(although the definition need not contain any statements beyond FUNCTION and END FUNCTION unless you wish).

该类声明不包含成员函数。一个类必须至少包含一个成员函数，因为定义第一个（或唯一）成员函数也是定义类本身。如果该类没有其他成员，则声明其构造函数。因为声明了构造函数，所以它也必须被定义（尽管定义不需要包含除 FUNCTION 和 END FUNCTION 之外的任何语句。）。

-4018 The columns specified in the THRU option do not belong to the same table.

This statement refers to some table first THRU (or THROUGH) last;however first and last are not both columns in that table. Check the spelling of these column names. Make sure that the correct database is current at this point in the compilation (the most recent preceding DATABASE statement).

该语句引用了某些表的 first THRU (or THROUGH) last；然而，第一列和最后一列都不是该表中的两列。检查这些列名的拼写。确保在编译(最近一次 DATABASE 语句)的当前时刻正确的数据库是当前的。

-4019 The columns specified in the THRU option appear in the reverse order.

This statement refers to some aggregate (table, record, or object) with the qualification "first THRU (or THROUGH) last." However, first and last do not appear in that order in the aggregate; last precedes first.

Check the spelling of the two names. Make sure that the correct database is current at this point in the compilation (the most recent preceding DATABASE statement).

该语句引用了一些具有“first THRU（或 THROUGH）”的聚集（表、记录或对象）。

但是，第一次和最后一次没有按顺序显示在聚集中；最后在第一位。请检查两个名称的拼写。确保在编译(最近一次 DATABASE 语句)的当前时刻正确的数据库是当前的。

-4020 Function "member" is not a member of class "class".

This statement tries to invoke class::member(), either directly or as object.member(). However, no such member function is available from that class. Check the spelling of the member name and the class or object name. If the reference is class::member(), review the declaration of the class for the correct spelling of the names of its members. If the reference is through an object, make sure the object is declared as having the class you intended. You can only call members of the stated class (the class it is declared to have) of an object. If you want to call a member of an actual class (the class that you think will be present at execution time), use the CAST operator.

该语句试图直接或者以 object.member() 方式调用 class::member()。但是，该类没有此类成员函数。检查成员名称和类或对象名称的拼写。如果引用是 class::member(),请检查类的声明以获取其成员名称的正确拼写。如果通过对象引用，则请确保该对象被声明为想要的类。只能调用所声明的类的成员（它声明拥有的类）的对象。如果要调用实际类的成员（您认为将在执行时出现的类），请使用 CAST 运算符。

-4021 A class member cannot be named "SELF".

You cannot use SELF, regardless of letter case, as the name of a member variable, member constant, or member function. The identifier SELF is a built-in identifier that New Era provides automatically. You can refer to SELF to make your code more readable when a member has the same name as an identifier that is declared as in the global or module scope, or to access a member when a local entity has the same name.

不管字母大小写，都不能使用 SELF 作为成员变量、成员常量或成员函数的名称。标识符 SELF 是 New Era 自动提供的内置标识符。当成员与全局或模块作用域中声明的标识符具有相同的名称时，可以引用 SELF 使代码更具可读性，或者在本地实体具有相同名称时访问成员。

-4022 The reserved keyword "name" cannot be used as a 4GL identifier.

Keywords cannot be used to name a function, report, variable, or constant. Consult the GBase 8s 4GL Language Reference for a list of reserved words.

不能使用关键字命名函数、报表、变量或常量。请参阅 GBase 8s 4GL 语言参考以获取保留字列表。

-4023 A class cannot derive from itself.

This CLASS statement asserts that the class is DERIVED FROM itself.

This action is not supported. Either remove the clause, or name another base class.

该 CLASS 语句声明的类是 DERIVED FROM 本身。但不支持此操作。要么删除该子句，要么命名另一个基类。

-4024 Identifier "name" has multiple declarations with different types.

Multiple declarations of a given name in a given scope must be consistent (that is, they must have the same type). The identifier that is shown has been declared with a different type.

给定范围内指定名称的多个声明必须一致（即它们必须具有相同的类型）。但显示的标识符使用了不同的类型声明。

-4025 Function "name" is already declared in the class.

A function with the specified name has already been declared in the current class.

已在当前类中声明了具有指定名称的函数。

-4026 Member "name" is already defined in base class "class".

A derived class inherits all the members of its base classes. You cannot add a member that has the same name as a member from the base class.

派生类继承其基类的所有成员。不能添加与基类成员具有相同名称的成员。

-4029 The type of expression on which member "name" is selected is not an object reference or record.

This statement refers to .name as if name were a member of a record or of a class. However, the expression that precedes the dot is neither the name of a record nor a reference to an object. If you think name is a member of a record, check the definition of the record, and make sure that its name is correctly spelled immediately preceding the dot. If you think name is a class member, make sure that the dot is preceded by an expression that yields a reference to an object of the right class.

该语句将 .name 作为名称，如同名称是记录或类的成员一样。但是，点之前的表达式既不是记录的名称，也不是对象的引用。如果您认为名称是记录的成员，请检查记录的定义，并确保点之前的名称的拼写正确。如果您认为名称是类成员，请确保该点前面有一个表达式，该表达式可以产生对正确类的对象的引用。

-4030 Warning: Cannot further expand an expanded expression.

An expression cannot have multiple .* suffixes.

一个表达式不能具有多个 .* 后缀。

-4032 Warning: The structure part of the THRU member "name" is ignored.

The statement included a THRU phrase of the following form:该语句包含以下格式的 THRU 短句：rec.first THRU rec.last The correct form is:正确的格式为：rec.first THRU last The logic is that first THRU last modifies rec.

逻辑是首先 THRU 最后修改 rec。

-4033 Base member name "name" cannot be used for class name.

This statement attempts to declare a class name, but it also specifies a DERIVED FROM clause. One of the members that is inherited from that base class is called name. The name of a class cannot be the same as the name of one of its members because the constructor function must use that name. Review the inheritance for this new class, and then choose a different name for it.

该语句试图声明一个类名，但它也指定了一个 DERIVED FROM 子句。从该基类继承的成员之一称为 name。类名不能与其成员的名称相同，因为构造函数必须使用该名称。请检查这个新类的继承，然后为它选择一个不同的名称。

-4034 SQL statements and two-pass reports are not allowed when compiling with the "-nosql" switch.

The compiler was invoked with the "-nosql" switch, but the source included either explicit SQL statements or a two-pass report (which involves SQL statements). Compiling with "-nosql" causes generation of.c code (instead of .ec code) in which no SQL statements are allowed.

编译器是通过“-nosql”开关调用的，但是源代码包含显式 SQL 语句或双向报表（涉及 SQL 语句）。

使用“-nosql”进行编译会导致生成无法使用 SQL 语句的 .c 代码（而不是 .ec 代码）。

-4035 Function "name" cannot be redefined in a derived class "class" with different access permissions.

The parent class of the function "name" has an access permission(PRIVATE, PROTECTED, or PUBLIC) different from this declaration.

函数“name”的父类具有不同于此声明的访问权限（PRIVATE、PROTECTED 或 PUBLIC）。

-4036 Function "name" cannot be redefined in a derived class"class" with different scope of reference.

The base class of the function "name" is declared as SHARED and "name"is not, or "name' is declared as SHARED and its base class is not.

函数“name”的基类声明为 SHARED 但“name”没有，或者“name”声明为 SHARED，但基类没有声明为 SHARED。

-4037 Multiple declarations of function "name".

Although you can declare multiple distinct versions of a user-defined function, you cannot do so for functions such as a name that GBase 8s software defines.

虽然您可以声明一个用户定义函数的多个不同版本，但是对于 GBase 8s 软件定义的名称等函数，您不能这样做。

-4041 Including "file" again will cause an infinite loop.

This INCLUDEAGAIN statement specifies a file that includes itself. If you force it to be included, a loop will follow. Make sure that this is the file you intended to include. Review the contents of the file.

该 INCLUDEAGAIN 语句指定一个包含它自己的文件。如果强制将其包含在内，则会出现循环。

确保这是您想要包含的文件。检查文件的内容。

-4042 This form of declaration can only appear in the global (module) scope.

The declaration for identifier::identifier can appear only in the global scope.

identifier::identifier 的声明只能出现在全局范围内。

-4043 Illegal EXTERNAL declaration.

This statement tries to declare an EXTERNAL classname::membername. A program cannot use a global EXTERNAL declaration to declare a shared member variable. To accomplish this, include the class description of which it is a SHARED member.

该语句试图声明一个 EXTERNAL classname::membername。程序不能使用全局 EXTERNAL声明来声明共享成员变量。为此，请包括它是共享成员的类描述。

-4044 Member "name" not defined in class "class".

This statement tries to access class::name. However, no such variable or constant is defined for that class. Check the spelling of the member name and the class or object name. If the reference is class::name,review the declaration of the class for the correct spelling of the member names. If the reference is through an object, make sure that the object is declared as having the class that you intended.

这个语句试图访问 class::name。但是，没有为该类定义这样的变量或常量。请检查成员名称和类或对象名称的拼写。如果引用是 class::name，请查看类的声明，以获取正确拼写的成员名称。如果引用是通过对象进行的，请确保将该对象声明为具有您想要的类。

-4045 Member "name" is defined in class "class", but not as a variable or constant.

The identifier name is defined in the class, but as something other than a variable or a constant, such as a member function. Check the spelling of the member name and the class or object name.

标识符名在类中定义，但定义为变量或常量以外的其他内容，例如成员函数。

请检查成员名称以及类或对象名称的拼写。

-4046 Formal declaration appeared previously for this informal function definition. The formal declaration is invalidated.

A formal declaration for this function appeared previously in this source module. At this point, a definition in the informal function syntax appears.

此函数的正式声明出现在此源模块中。此时，出现非正式函数语法中的定义。

-4047 Mixed informal and formal function declaration syntax.

Return type is ignored.

A function declaration has blended informal (FUNCTION program block)and formal (FUNCTION prototype) syntax. The parenthesized list of arguments gave only names, with the types to be defined later in a VARIABLE statement, but the declaration then continued with a RETURNING clause, available only in the FUNCTION prototype style of declaration.

Consult the GBase 8s 4GL Reference Manual.

函数声明混合了非正式语法（ FUNCTION 程序块）和正式语法（ FUNCTION 原型）。

带括号的参数列表只给出了名称，类型将在后面的 VARIABLE 语句中定义，但是声明继续使用 RETURNING 子句，仅以 FUNCTION 原型声明的样式可用。请参阅 GBase 8s 4GL 参考手册。

-4048 Driver statements for a report are not allowed within the body of that report.

This statement defines a record variable and uses initialization expressions when it declares one or more members. This action is not supported. You can use an initialization expression only when you define a simple variable.

该语句定义了一个记录变量，并在声明一个或多个成员时使用初始化表达式。

不支持此操作。只有在定义一个简单变量时才可以使用初始化表达式。

-4050 Function "name" has been used and hence declared as informal before this formal declaration.

A call to this function appears prior to this declaration of it. Calls to undeclared functions are supported only for compatibility with previous versions of the 4GL language. When the compiler encountered the call to the function, it assumed an informal declaration for it.

Move the declaration of the function to the top of the source module so that it precedes calls to it.

在函数声明之前出现对此函数的调用。只有旧版本的 4GL 语言支持调用未声明的函数。

当编译器遇到对该函数的调用时，它假定函数有一个非正式的声明。将函数的声明移到源模块的顶部，以便声明先于调用。

-4051 Member "name" is defined in class "class", but not as a function.

This statement tries to invoke class::member(), either directly or as object.member(). The class has a member of that name, but it is a member variable, not a function. Check the spelling of the member name and the class or object name. Review the declaration of the class for the correct spelling of its member names.

该语句试图直接或者以 object.member() 方式调用 class::member()。类具有该名称的成员，但它是一个成员变量，而不是函数。请检查成员名称以及类或对象名称的拼写。

检查类的声明，确保它们成员名拼写正确。

-4052 Identifier "name" is not defined in the global scope.

A constant or variable is used that is not locally defined, so the compiler assumes that it is to be globally defined but does not find it there either.

使用的常量或变量不是本地定义的，因此编译器假定它是全局定义的，但找不到它。

-4053 Function "name" has already been declared with a different prototype.

The function that is described in this FUNCTION statement has already been declared, and the previous declaration disagrees with this one in the number or type of the arguments. Review included files for declarations of this function, and make those statements consistent.

在 FUNCTION 语句中描述的函数已经被声明，但前面的声明与这个参数的数量或类型不一致。

请检查包含该函数声明的文件，使这些语句保持一致。

-4054 Function "name" has already been declared with a different return type.

The function that is described in this FUNCTION statement has already been declared, and the previous declaration disagrees with this one in the number or type of returned values. Review included files for declarations of this function, and make those statements consistent.

在 FUNCTION 语句中描述的函数已经被声明，但前面的声明与该返回值的数量或类型不一致。

请检查包含该函数声明的文件，使这些语句保持一致。

-4055 Overriding the constructor of a base class is not allowed.

This FUNCTION declaration in a CLASS statement specifies a function whose name is the same as the name of a base of this class. In other words, you are trying to override the constructor function of a base class. This action is not permitted. Review the names of members that are inherited by this class, and choose unique names for its member functions.

CLASS 语句中的 FUNCTION 声明指定了一个函数，其名称与该类的基类名称相同。换句话说，您试图覆盖基类的构造函数。此操作是不允许的。请检查该类继承的成员的名称，并为其成员函数选择唯一名称。

-4057 A class cannot be derived from a class with PRIVATE intrinsic functions.

This statement declares a new class with a DERIVED FROM clause.

However, the specified base class has one or more intrinsic functions(class constructor, function such as !copy()) that are declared PRIVATE. The intrinsic functions of a base class must be available for calling from within the same functions of the derived class. Private members cannot be called so; therefore, you cannot derive a class from a base class with private intrinsic functions. Make sure that you specified the correct base class, and review its declaration.

这条语句声明了一个带有 DERIVED FROM 子句的新类。但是，指定的基类具有一个或多个声明为 PRIVATE 的内部函数（类构造函数、类似 !copy() 的函数）。基类的内部函数必须可用于从派生类的相同函数内进行调用。私有成员不能这么调用；因此，无法从具有私有内部函数的基类中派生类。请确保指定了正确的基类，并检查它的声明。

-4058 Symbol with constructor name is not a function.

A class name that is followed by the name of a member variable or constant is not allowed in this context.

在此上下文中不允许类名后跟成员变量或常量的名称。

-4059 More actual arguments than formal arguments for function "name".

This statement invokes function name, but it specifies more argument expressions than were called for in the declaration of function name.

Check the syntax of the argument list. Review the declaration of the function for the expected number and type of arguments.

该语句调用函数名称，但它指定的参数表达式比函数名称声明中调用的参数表达式多。

检查函数的声明，以确定参数的预期数量和类型。

-4060 Fewer actual arguments than formal arguments without defaults for function "name".

This statement invokes function name, but it specifies fewer argument expressions than were called for in the declaration of function name.

Check the syntax of the argument list. Review the declaration of the function for the expected number and type of arguments.

该语句调用函数名称，但它指定的参数表达式数量少于函数名称声明中要求的值。

请检查参数列表的语法。检查函数的声明，以确定参数的预期数量和类型。

-4062 Warning: Informal function "name" returns (or is expected to return)different number of results at different places.

The function name is called at more than one place in this source module, and it is implied to return different numbers of arguments.

Possibly this correct; it is possible to write functions that return different numbers of values in different circumstances. However, you should check that this is the case and that the expected number of values will be returned in each case.

在此源模块中的多个位置调用函数名称，并且隐含返回不同数量的参数。这可能这是正确的；可以编写在不同情况下返回不同数值的函数。但是，您应该检查是否存在这种情况，并且在每种情况下都将返回预期的值数。

-4063 Function "name" should not return any results.

This statement invokes the function "name" in a context that implies it should return one or more values. However, that function has been declared earlier in this module without a RETURNING clause or with RETURNING VOID. Make sure that you have called the function you intended; then review its declaration.

该语句在上下文中调用函数“name”，这意味着它应该返回一个或多个值。但是，该函数在此模块的前面已经声明过，没有 RETURNING 子句，没有 RETURNING VOID。确保您已经调用了您想要的函数；然后检查它的声明。

-4064 Type of returned value does not match the declared return type of function "name".

The function "name" was not explicitly declared but has already been called with one prototype, and the current call provides a different prototype. Make sure that you have called the function you intended.

Then review its earlier call, or create an explicit declaration for it.

函数“name”没有显式声明，但是已经用一个原型调用了，当前的调用提供了不同的原型。

确保您已经调用了您想要的函数。然后检查它以前的调用，或者为它创建一个显式声明。

-4065 Multiple exception handlers for the same exception class "name".

Two or more ON EXCEPTION statements exist for the same exception class in this block. Only one can be invoked. Review the statements, make sure that each specifies the correct exception class, and remove or combine duplicate handlers.

对于该块中的同一异常类，存在两个或更多 ON EXCEPTION 语句。只能调用一个。

检查语句，确保每个语句指定了正确的异常类，删除或合并重复的处理程序。

-4066 RETURN statement not allowed in the body of intrinsic functions.

This statement is part of the definition of an intrinsic member function (the class constructor, !copy, and so on). These functions do not have explicit result values; or more precisely, code that the compiler automatically generates produces their returned values. Delete the RETURN statement.

该语句是内部成员函数定义的一部分（类构造函数，!copy等）。这些函数没有明确的结果值;或者更确切地说，编译器自动生成的代码会产生它们的返回值。请删除 RETURN 语句。

-4067 This RETURN statement must provide a value.

This RETURN statement does not specify a value to return, but the function was declared with a RETURNING clause that specified other than VOID. If you want to terminate a function early without producing a value, you could put a label on the END FUNCTION statement and use a GOTO, or redesign the function logic to avoid the need for an early exit.

此 RETURN 语句没有指定要返回的值，但是该函数是使用除 VOID 之外指定的 RETURNING子句声明的。如果想要在不产生值的情况下提前终止函数，可以在 END FUNCTION 语句上添加一个标签并使用 GOTO，或者重新设计函数逻辑以避免提前退出。

-4068 Function "class::member" has not been declared as SHARED.

This statement uses the double-colon syntax to invoke a class-member function. However, the specified member function was not declared as SHARED. Only shared member functions can be called this way; normal member functions must be called through a reference to an object because they need the object reference as the value of their SELF reference. Check that you have specified the class and member that you intended; then review the declaration of that class.

该语句使用双冒号语法来调用类成员函数。但是，指定的成员函数未声明为 SHARED。

只有共享的成员函数可以这样调用；正常成员函数必须通过对对象的引用来调用，因为它们需要对象引用作为其 SELF 引用的值。检查是否指定了想要的类和成员；然后检查该类的声明。

-4069 The type of expression on which member function "name" is called is not a class.

This statement attempts to invoke the specified function using either the scope resolution (::) operator or the record membership (.)operator. However, the name to the left of the scope resolution operator is not the name of a class in which name is a member, or the name to the left of the record membership operator is not the name of an object reference of which name is a member. If you intended to call name through a reference to an object, use object.name syntax.

Otherwise, make sure that you have specified the class and member names that you intended, and review the declaration of the class.

该语句尝试使用范围解析（::)运算符或记录成员（.）运算符来调用指定的函数。

但是，范围解析运算符左侧的名称不是名称是其成员的类的名称，或者记录成员运算符左侧的名称不是名称为其对象引用的名称会员。如果您打算通过对对象的引用来调用名称，请使用 object.name 语法。否则，请确保您已指定您想要的类和成员名称，并查看该类的声明。

-4070 Cannot assign to "SELF".

This statement would assign a new value to the implicit function argument named SELF. Since the value of SELF is used implicitly in any reference to a member of the self object, assignment to it is not permitted.

该语句将为名为 SELF 的隐式函数参数分配一个新值。由于 SELF 的值在对 self 对象的任何引用中都被隐式引用，因此不允许对其赋值。

-4071 Cannot assign to constant "name".

This statement would assign a new value to name, but name was declared(in this scope) with a CONSTANT statement. Constants do not have memory locations and cannot be assigned new values. Check that name is the identifier you intended to use. Then review its declaration. Possibly you want to assign into a module-level variable name, but it has been declared as a local constant or a member constant that takes precedence in this context.

该语句将为 name 赋予新值，但是名称是使用 CONSTANT 语句声明的（在此范围内）。常量没有内存位置，也不能分配新值。检查该名称是您打算使用的标识符。然后检查它的声明。

可能您想分配一个模块级别的变量名称，但它已被声明为一个本地常量或一个在此上下文中优先的成员常量。

-4072 Cannot expand structure with no members.

The statement attempted to perform an expansion, but it failed. The expansion was of the form object.*, but the object that is named does not have any public member variables, so the expansion set is empty.

Check that you are referring to the correct class and member.

该语句试图进行扩展，但失败了。扩展是表单 object.*，但被命名的对象没有任何公共成员变量，所以扩展集是空的。检查是否引用了正确的类和成员。

-4073 Beginning or ending name in THRU specification is not a member of the target record.

This statement makes a reference to some structure (table, record, or object) with the qualification "first THRU (or THROUGH) last". However,first or last does not appear as an element of that aggregate. Check the spelling of the two names.

该语句引用了具有“first THRU（或 THROUGH）last”限定的结构（表、记录或对象）。

但是，第一个或最后一个不会显示为该聚集的元素。检查两个名称的拼写。

-4074 No more than two substring index expressions are allowed.

The substring qualifier consists of a pair of integer expressions,separated by a comma and surrounded by brackets (example: name[1,23]).

The first value cannot be larger than the second. Both must be positive and no larger than the string length (or the declared length of the receiving data type).

子字符串限定符由一对整数表达式组成，用逗号分隔并用括号括起来（例如：name [1,23]）。

第一个值不能大于第二个值。两者都必须是正数并且不能大于字符串长度（或声明的接收数据类型的长度）。

-4075 Simple string expressions must have type CHAR or VARCHAR.

The compiler expected a string expression but found an expression that was neither CHAR nor VARCHAR data type.

编译器期望字符串表达式，但发现一个既不是 CHAR 也不是 VARCHAR 数据类型的表达式。

-4076 Class of CAST object must be a base of class specified as right argument.

You cannot cast an object to any class; you can only cast it as being of a class that is derived from its stated class. In the CAST expression in this statement, the stated class of the object reference on the left is not a base class of the class that is named as the right argument. Review the expression to make sure that you have specified the object that you intended (possibly you need to use parentheses around the object reference) and the target class.

不能将对象强制转换为任何类；只能将其转换为派生自其指定类的类。在此语句中的 CAST 表达式中，左侧对象引用的指定类不是命名为右边参数的类的基类。检查表达式，以确保指定了您想要的对象(可能需要在对象引用周围使用括号)和目标类。

-4077 This operation is not valid on an operand of this type.

The operator cannot accept operands of this type. Correct any other errors that might have been reported, and verify that this operator is defined for operands of this type. Then compile the program again.

操作者不能接受这种类型的操作数。更正可能报告的任何其他错误，并确认此运算符是否为此类型的操作数定义的。然后再次编译程序。

-4078 Operand is missing, or is of a type that is not supported.

The operator has been directed to operate on an invalid type. Perhaps a function returns VOID, a blob (TEXT or BYTE), or FOREIGN result. IS NULL and IS NOT NULL operators can operate upon TEXT or BYTE and FOREIGN operands and can receive assignment from other operands of the same type or NULL.

已指示运算符对无效类型进行操作。函数可能返回 VOID、blob（TEXT 或 BYTE）或 FOREIGN结果集。IS NULL 和 IS NOT NULL 运算符可以对 TEXT 或 BYTE 和 FOREIGN 操作数进行操作，并且可以接收来自相同类型或 NULL 类型的其它操作数的赋值。

-4079 Operation is not allowed in index expressions.

An operation such as expansion (.*), COPY, NEW, or THRU was attempted in an index expression.

在索引表达式中尝试了扩展（.*）、COPY、NEW 或 THRU 等操作。

-4080 Warning: Operation on NULL returns NULL.

While the compiler was optimizing expressions, it found an expression composed of literal values, at least one of which was NULL.

当编译器优化表达式时，它发现了一个由文字值组成的表达式，其中至少有一个是 NULL。

-4081 Warning: A DATETIME expression cannot be negative.

A "-" operator occurred with a DATETIME operand. No negative points exist in time. INTERVAL can be negative, but DATETIME cannot. Inspect the syntax of the expression, and revise it to make it greater than or equal to zero.

一个“-”操作符与 DATETIME 操作数一起发生。时间上不存在负点。INTERVAL 可以是负值，但 DATETIME 不能。请检查表达式的语法，并将其修改为大于或等于零。

-4082 Operands of MATCH and LIKE operations must be of CHAR or VARCHAR type.

This statement uses the MATCH or LIKE operator with an argument expression that is numeric or binary. No automatic conversion of data types exists in this case. Examine the expression. If it is written as you intended, revise it to assign the values to character variables(thus forcing their conversion to character) before you use them with MATCH or LIKE.

该语句使用 MATCH 或 LIKE 运算符以及数字或二进制的参数表达式。在这种情况下数据类型不会自动转换。请检查表达式。如果它是按照您的意图编写的，那么修改它，将值赋值给字符变量(从而强制将它们转换为字符)，然后再将它们与 MATCH 或 LIKE 一起使用。

-4083 Warning: Initialization of external variables will be ignored.

This is only a warning. This statement declares a variable with both the EXTERNAL keyword and an initialization expression. You can initialize a variable only at the point where it is defined (that is,where memory is allocated for it). This is a declaration, not a definition, so the initialization is ignored.

这只是一个警告。该语句使用 EXTERNAL 关键字和初始化表达式声明一个变量。您只能在定义它的位置（也就是为其分配内存的位置）初始化一个变量。这是一个声明，而不是一个定义，所以初始化被忽略。

-4085 Cannot output expression of this type.

The statement attempted to output an expression of a type that cannot be output, such as FOREIGN, or an expression that includes an invocation of a function that returns VOID.

该语句试图输出无法输出的类型的表达式，例如 FOREIGN，或者包含调用返回 VOID 的函数的表达式。

-4091 Cannot assign to or refer to an array as a whole. Use indexing to refer to individual elements.

The compiler attempted to convert the result of one expression to conform with the type of another expression, and only one of them was an ARRAY. Either both must be ARRAY type, or neither can be.

编译器试图将一个表达式的结果转换为符合另一个表达式的类型，其中只有一个是 ARRAY。

两者都必须是 ARRAY 类型，或都不是。

-4092 Type mismatch between CLASS and non-CLASS type.

The compiler attempted to convert the result of one expression to conform with the type of another expression, and only one of them was a CLASS. Either both must be CLASS type, or neither can be.

编译器试图将一个表达式的结果转换为符合另一个表达式的类型，其中只有一个是 CLASS。

两者都必须是 CLASS 类型，或者都不是。

-4093 Type mismatch between RECORD and non-RECORD type.

The compiler attempted to convert the result of one expression to conform with the type of another expression, and only one of them was a RECORD. Either both must be RECORD type, or neither can be.

编译器试图将一个表达式的结果转换为符合另一个表达式的类型，其中只有一个是 RECORD。

两者都必须是 RECORD类型，或者都不是。

-4094 Length of compared CHAR or VARCHAR types is different.

The compiler was attempting to process a comparison between two string types (such as comparing function signatures), and the two strings had different bounds.

编译器试图处理两个字符串类型之间的比较（如比较函数签名），这两个字符串具有不同的边界。

-4095 Records have different number of fields or fields of incompatible types.

In this multiple-field assignment the values that are being assigned do not correctly match to the fields in the receiving record or object.

Examine the syntax of the value expression; then review the declaration of the receiving variable.

在此多字段分配中，正在分配的值无法正确匹配接收记录或对象中的字段。检查值表达式的语法；然后检查接收变量的声明。

-4096 Expression class must be equal to or derived from result class.

The statement attempted to assign a value of one class to an object of a different class that is not derivable from the former class.

该语句试图将一个类的值赋值给另一个类的对象，而该对象不能从前一个类派生。

-4097 Multiple declarations for class "name".

This class has been declared previously in the source module (perhaps in an included file). Only one declaration is allowed. Find all declarations of the class, and reduce them to one.

该类已经在源模块中声明过（可能在一个包含文件中）。只允许一个声明。找到该类的所有声明，并将其减少到一个。

-4098 Type of expression that is expanded must be class or record.

This statement refers to name.* (or uses THRU notation); however, the name it refers to is not declared as a record or as an object of some class. Check the spelling of the name, and review its declaration.

该语句引用 name.* （或使用 THRU 符号）；然而，它引用的名称并没有被声明为记录或某个类的对象。检查名称的拼写，并查看其声明。

-4099 Type to CAST to must be a class.

The right argument to the CAST operator in this statement is not the name of a class. Review the syntax and spelling of the statement. Make sure that you have included all necessary header files to declare classes.

此语句中 CAST 运算符的正确参数不是类的名称。检查语句的语法和拼写。确保包含了声明类所需的所有头文件。

-4100 Illegal definition of constant identifier "name".

A name already established as that of a constant identifier has appeared as a declaration for a new identifier. Suppose, for example,that maxval has already been declared to be a constant in class x, and then a later declaration of VARIABLE x::maxval INT occurs.

已确定为常量标识符的名称已作为新标识符的声明出现。例如，假设 maxval 已经声明为 x 类中的常量，然后出现 VARIABLE x::maxval INT 的后续声明。

-4103 The compiler detected an internal error in file "name" at line number.

Consult your system administrator or contact GBase Technical Support to report this error.

请咨询您的系统管理员或联系 GBase 技术支持部门报告此错误。

Note the specified file name and line number. Then report this internal error.

记下指定的文件名和行号。然后报告这个内部错误。

-4104 The type of a column value does not match the type of a variable.

The INITIALIZE statement cannot establish a match between the type of the column value and the type of the corresponding variable.

INITIALIZE 语句不能在列值的类型和对应变量的类型之间建立匹配。

-4106 An expression of type DATETIME is expected.

In an EVENT statement, a function definition or declaration, an EXTERNAL REPORT statement, a HANDLER statement, a function invocation,or just an expression, the compiler found something other than a DATETIME expression.

在 EVENT 语句中、函数定义或声明、EXTERNAL REPORT 语句、HANDLER 语句、函数调用或者表达式中，编译器找到了不是 DATETIME 表达式的其它项。

-4107 An expression of type INTEGER or SMALLINT is expected.

在 EVENT 语句、函数定义或声明、EXTERNAL REPORT 语句、HANDLER 语句、函数调用或表达式中，编译器发现的不是 INTEGER 或 SMALLINT 表达式的其它项。

-4108 An expression of type DATE is expected.

在 EVENT 语句、函数定义或声明、EXTERNAL REPORT 语句、HANDLER 语句、函数调用或表达式中，编译器发现的不是 DATE 表达式的其它项。

-4109 An expression of type DATE or DATETIME is expected.

在 EVENT 语句、函数定义或声明、EXTERNAL REPORT 语句、HANDLER 语句、函数调用或表达式中，编译器发现的不是 DATE 或 DATETIME 表达式的其它项。

-4110 You cannot use more than one of the REPORT TO options in the OUTPUT section of a REPORT routine.

In this OUTPUT section, the statement REPORT TO appears more than once. Only one such specification is allowed. Remove all but one.

在此 OUTPUT 部分中，语句 REPORT TO 多次出现。只允许有一个这样的规范。

只保留一个，其余全部删除。

-4111 Warning: The function name is declared informally. For stronger type checking, use a function defined formally.

The compiler detected that function name is an informal function.

Possibly the function returned a different number of arguments in different circumstances, or the function has no prototype declaration. Although nothing is wrong with defining a function this way, informal functions are more prone to errors at runtime. It is recommended that you use formal function declarations (along with function prototypes) that are less error-prone and that the compiler checks more rigorously.

编译器检测到函数名是非正式函数。函数可能在不同情况下返回不同数量的参数，或者该函数没有原型声明。虽然用这种方式定义函数没什么问题，但非正式函数在运行时更容易出错。建议您使用不易出错的正式函数声明（以及函数原型）并且编译器检查得更严格。

-4117 A constant expression is expected here.

At least one of the values in one of the constant expressions in this CONSTANT statement cannot be evaluated at compile time. See the information on constant expressions in the GBase 8s 4GL Reference Manual for information on what types of operations can be used in constant expressions.

此 CONSTANT 语句中的常量表达式中至少有一个值不能在编译时计算。有关常量表达式中可以使用哪些类型的操作的信息，请参阅“ GBase 8s 4GL 参考手册”中有关常量表达式的信息。

-4118 Expressions of this data type are not allowed in constant expressions.

The indicated expression cannot be evaluated to a constant. Correct any other errors that might have been reported against this expression, and recompile.

指定的表达式不能计算为常量。纠正可能根据此表达式报告的任何其他错误，并重新编译。

-4119 Time-dependent functions must be used with the function CONSTANT() in constant expressions.

One of the constant expressions in this CONSTANT statement refers to function such as CURRENT, whose value depends on the current time. Such functions have to be written as arguments to the CONSTANT() function,which returns their value as of the time of compilation. (You cannot use the time of execution in a constant value.)此 CONSTANT 语句中的常量表达式引用了类似 CURRENT 的函数，其值取决于当前时间。

这些函数必须作为参数写入 CONSTANT() 函数，该函数在编译时返回它们的值。

（不能以常量使用执行时间。）-4120 Declare variable "name" either external or local to module,but not both.

The specified variable has been declared or defined more than once. At least one of those times declared it with EXTERNAL, and another was a definition as a module variable (lacking either EXTERNAL or GLOBAL).

Review the declarations and definitions of name, recalling that some of them might be in included files. If you intend name as a variable private to this module, give it a unique name. (You can declare a variable as EXTERNAL more than once, and you can declare it as EXTERNAL and then define it as GLOBAL. Both of these things can happen as a result of including header files, and they have well-defined meanings.

But it is contradictory to have a variable that is both external and local to the module.)已多次声明或定义指定的变量。其中至少有一次使用 EXTERNAL 声明，另一次是定义为模块变量(缺少 EXTERNAL 或 GLOBAL)。检查名称的声明和定义，回顾其中一些可能在包含的文件中。如果您打算将名称命名为此模块的私有变量，请给它一个唯一的名称。(您可以多次将变量声明为 EXTERNAL，也可以将其声明为 EXTERNAL ，然后将其定义为 GLOBAL。这两种情况都可能由于包含头文件而发生，而且它们都有明确的含义。但是，但是有一个变量既是外部的，也是模块的本地变量，这是矛盾的。）-4121 Reports cannot be invoked through the CALL statement or in function call expressions.

This statement attempts to call a report as if it were a function.

Although a report has the general form of a function definition, it cannot be used like one. Check the names of functions that are called in this statement; one is a report. If you meant to send a row of data to the report, use the OUTPUT TO REPORT statement.

该语句试图调用一个报告，就像它是函数一样。尽管报告具有函数定义的一般形式，但它不能像函数定义那样使用。检查在此语句中调用的函数的名称；其中一个是报告。如果您打算向报告发送一行数据，请使用 OUTPUT TO REPORT 语句。

-4122 Parser limitations have been exceeded. Try to reduce complexity or size of module.

The parser has returned an error that is NOT a syntax error. This error could be caused by a parser-stack overflow (too many levels of nesting within IF statements, WHILE statements, or the like) or by the parser running out of parser-stack space (the module is too large). Try to reduce the complexity of the code by splitting complex functions into multiple functions or splitting the module into multiple modules.

解析器返回了一个不是语法错误的错误。这个错误可能是由解析器堆栈溢出（IF 语句，WHILE 语句等嵌套层次太多）或解析器堆栈空间不足（模块太大）造成的。尝试通过将复杂功能分解为多个功能或将模块分成多个模块来降低代码的复杂性。

-4123 CALL to function "name" must have a RETURNING clause.

The function name is declared as returning a result, so the CALL statement must provide a RETURNING clause to receive the result.

函数名称被声明为返回结果集，所以C ALL语句必须提供一个 RETURNING 子句来接收结果。

-4125 Not defined/declared as a member in the class hierarchy "name".

The element indicated is either not declared, or is declared but not defined, as a member of the class hierarchy "name."指定的元素未声明，或者已声明但未定义为类层次结构“name”的成员。

-4126 Handler expected.

The identifier in the WITH clause of the HANDLE statement does not identify a handler. If the identifier of the handler specifies a class,check to see that the handler is declared as belonging to that class;otherwise, check to see that it is declared as belonging to the declared class of the target object.

HANDLE 语句的 WITH 子句中的标识符不标识处理程序。如果处理程序的标识符指定了类，请检查处理程序是否被声明为属于该类；否则，检查它是否被声明为属于目标对象的声明类。

-4127 Event expected.

The identifier before the WITH clause of the HANDLE statement does not identify an event. The event must be declared in or inherited by the declared class of the target object (which can be the SELF object).

HANDLE 语句的 WITH 子句前面的标识符不标识事件。该事件必须在目标对象（可以是 SELF对象）的声明类中声明或继承。

-4128 Handler should be a member of either the same class, or else a base class, of the object.

The indicated handler is declared in the program but is not a member of same class as the object or of a base class from which the object is derived.

指示的处理程序在程序中声明，但与对象或派生对象的基类的成员不同。

-4129 Object name expected.

In the HANDLE statement, the event was prefixed with a "name." qualifier,but the name is not that of a known object.

在 HANDLE 语句中，该事件的前缀是“name.”限定符，但名称不是已知对象的名称。

-4130 Handler can't be invoked directly.

A handler cannot be the object of an explicit CALL statement. The only way to invoke a handler is through calling or posting the event to which the handler has been assigned by a HANDLE statement.

处理程序不能是显式 CALL 语句的对象。调用处理程序的唯一方法是通过调用或发布由 HANDLE 语句分配处理程序的事件。

-4131 No implied object for this non-shared function call ("SELF" is not defined in this context).

No object reference has been supplied for this member function call. If the member function call was made inside a member function, "self"would be the implied object reference. This call was made in a nonmember function body, so there is no implied object reference.

未为此成员函数调用提供对象引用。如果成员函数调用是在成员函数中进行的，那么“self” 就是隐含的对象引用。此调用是在非成员函数体中进行的，所以没有隐含的对象引用。

-4132 Incorrect base class name in base clause.

The program has declared a base class and has declared another class as DERIVED FROM that base class. In the definition of the constructor for the derived class, a base constructor clause specifies a call to a function that is NOT the base class constructor. Suppose a derived class is called "bread" and its base class is called "food"; if the constructor for loaf should have a definition that begins FUNCTION bread::bread(args1):food(args1). If it begins FUNCTION bread::bread(args1):beverage(args1), the error message appears.

程序声明了一个基类，并声明了从该基类派生的另一个类。在派生类构造函数的定义中，基础构造函数子句指定对不是基类构造函数的函数的调用。假设派生类被称为"bread"，其基类称为"food"；如果面包的构造函数应该有一个以 FUNCTION bread::bread(args1):food(args1) 开头的定义。如果以 FUNCTION bread::bread(args1):beverage(args1) 开始，则显示错误消息。

-4133 Only events can be posted.

A POST statement specified something other than event. Member functions, handlers, and reports cannot be posted.

POST 语句指定了事件以外的其他内容。不能发布成员函数、处理程序和报告。

-4134 Class qualification not allowed when invoking an event.

The program specified a class name followed by a scope resolution operator (::) and the name of an event. Replace the class name with the name of the appropriate object.

该程序指定了一个类名，后跟范围解析运算符（::)和事件的名称。请将类名替换为适当对象的名称。

-4135 Only shared class variables can be defined outside class declaration.

A class variable described as SHARED cannot be defined outside the class declaration. The variable definition indicated is completing the definition of a variable already described without a SHARED qualifier in a class declaration.

不能在类声明外定义描述为 SHARED 的类变量。所指出的变量定义是在类声明中完成已经描述的变量的定义，而没有 SHARED 限定符。

-4136 Intrinsic function name() has wrong signature.

The correct signature for a !copy() function is FUNCTION !copy (obj this_class), having one parameter whose type is an object of the containing class. The correct signature for a !derive() function has no arguments, only a pair of parentheses.

!copy() 函数的正确签名是 FUNCTION !copy (obj this_class) 其中一个参数的类型是包含类的对象。!derive() 函数的正确签名是没有参数的，只有一对括号。

-4137 Embedded C code is allowed in compiled-4GL programs only.

A BEGIN_C and END_C block can be included only in compiled NewEra programs. It is not valid in a interpreted (p-code) NewEra program.

BEGIN_C 和 END_C 块只能包含在已编译的 NewEra 程序中。它在解释（p-code）NewEra 程序中无效。

-4138 Arrays of CHAR(*) are not allowed.

ARRAY [ ] OF CHAR(*) is not a valid type.

ARRAY [ ] OF CHAR(*) 是一个无效的类型。

-4139 The constant "name" cannot be used within its own definition.

A constant cannot be used until it is defined. Therefore, a constant cannot be used in its own definition.

除非定义了常量，否则不能使用它。因此，常量不能在其本身的定义中使用。

-4140 Compiler cannot continue.

This error is output if an unrecoverable error occurs in the compiler(that is, SEG VIO, BUS ERROR). This situation could occur if the user terminated the compilation explicitly. Otherwise, if the error recurs,note all circumstances and contact GBase Technical Support.

如果编译器中出现不可恢复的错误，则输出此错误（即，SEG VIO、BUS ERROR）。

如果用户显式终止编译，则可能发生这种情况。否则，如果错误再次发生，请注意所有情况，并与 GBase 技术支持部门联系。

-4141 Unknown 4GL compiler flag "name" will be ignored.

This error occurs when the user invokes components of the NewEra product directly, instead of through standard interfaces. The executable fglc or fglp has been passed a compiler switch that is not understood.

当用户直接调用而不是通过标准接口定义 NewEra 产品的组件时，会发生此错误。

可执行文件 fglc 或 fglp 已被传递给一个无法解释的编译器开关。

-4142 Functions called in the WHENEVER statement cannot require parameters.

The WHENEVER statement in the program has the form WHENEVER condition CALL function, and the function being called is declared to have parameters. The function call in this context cannot even have parentheses, let alone arguments. Note that main has implicit parameters, so it cannot be used in this form of the WHENEVER statement.

程序中的 WHENEVER 语句具有 WHENEVER 条件 CALL 函数格式，被调用的函数被声明为具有参数。在这种情况下的函数调用甚至不能有括号，更不用说参数了。请注意，main 有隐式参数，所以它不能以 WHENEVER 语句这种形式使用。

-4143 Functions called in the WHENEVER statement cannot return values.

The WHENEVER statement in the program has the form WHENEVER condition CALL function, and the function that is being called is declared with a RETURNING clause. The function call in this context cannot return any values.

程序中的 WHENEVER 语句具有 WHENEVER 条件 CALL 函数的形式，并且正在调用的函数使用 RETURNING 子句声明。此上下文中的函数调用不能返回任何值。

-4144 A grammatical error has been found in an INCLUDEd file. The construct is not understandable in its context.

This general message shows an inability to parse a NewEra statement from a file summoned by an INCLUDE statement. Start at the point where the error was issued, and work backward in the program looking for other error messages, and for missing punctuation, missing END statements, and other mistakes. Often, a missing END IF is the culprit.

If the cause for this error is not obvious, concentrate on eliminating any other, more specific error messages, and this one will probably go away also.

此一般消息显示无法从 INCLUDE 语句调用的文件中解析 NewEra 语句。从发出错误的位置开始，在程序中反向查找其他错误消息、缺少标点符号、缺少 END 语句和其他错误。通常，缺少 END IF 是罪魁祸首。如果这个错误的原因不明显，那就集中精力消除任何其他更具体的错误信息，这个错误信息也可能会消失。

-4145 Too many errors, compiler will quit.

Too many compiler errors have been detected. The compiler reports the errors it has found to this point and quits.

检测到太多的编译错误。编译器报告它发现的错误并退出。

-4146 Too many input files specified.

The executables fglc and fglp allow only 1 input file.

可执行文件 fglc 和 fglp 只允许一个输入文件。

-4147 A RETURN statement is required in this function.

The function was declared with a RETURNING clause that specified other than VOID, but no RETURN statement occurs in the body of the function.

该函数声明了 RETURNING 子句，该子句指定的不是 VOID，但函数的主体中没有发生 RETURN 语句。

-4148 CHAR (*) type is not allowed in SQL statements.

The CHAR(*) type is not allowed as an SQL type. It cannot be used in CREATE TABLE, ALTER TABLE, and so on.

不支持 CHAR(*) 类型作为 SQL 类型。它不能用于 CREATE TABLE、ALTER TABLE 等。

-4149 Expressions of this type are not allowed in SQL statements.

An identifier that is mentioned in an SQL statement is of a type such as FOREIGN, or it names an object (a member of a class) or a record.

在 SQL 语句中提到的标识符是类似 FOREIGN 的类型，或者它命名了对象（类的成员）或记录。

-4150 First parameter must be an ixRow object.

For calls to the built-in functions packrow() and unpackrow(), the first argument must be of type ixRow.

对于调用内建函数 packrow() 和 unpackrow()，第一个参数必须是 ixRow 类型。

-4151 Constructor cannot be called directly.

A constructor cannot be called directly using the CALL statement or as the function in a function call expression. The constructor should be invoked indirectly using the NEW operator.

不能直接使用 CALL 语句调用构造函数，或这在函数调用表达式中作为函数使用。

构造函数必须直接使用 NEW 操作符调用。

-4152 Invalid begin or end name for THROUGH expression.

Invalid expressions have been used in a THROUGH expression in an SQL statement.

SQL 语句中的 THROUGH 表达式中使用了无效的表达式。

-4153 Warning: The constant expression with the USING clause has been evaluated based on the values of the environment variables at compile time.

This warning is generated when a value for a CONSTANT contains a USING clause. The settings for environment variables DBFORMAT and DBMONEY can affect the result of the USING operation. This warning reminds the user that the USING clause in the CONSTANT statement will be evaluated at compile time and might not be consistent with other USING clauses that are evaluated at runtime.

当 CONSTANT 的值包含 USING 子句时会生成此警告。环境变量 DBFORMAT 和 DBMONEY 的设置可能会影响 USING 操作的结果。此警告提醒用户 CONSTANT 语句中的 USING 子句将在编译时进行计算，并且可能与运行时计算的其他 USING 子句不一致。

-4154 The maximum size allowed for a constant of type CHAR or VARCHAR is 255.

In a CONSTANT declaration or definition, the size of a character type constant (CHAR or VARCHAR) cannot exceed 255.

在 CONSTANT 定义或声明中，字符类型常量（CHAR 或 VARCHAR）的大小不能超过 255。

-4155 Warning: Only static cursor names are allowed in the WHERE CURRENT OF clause. Cursor name will be processed as a static cursor name.

In the UPDATE and DELETE statements, the WHERE CURRENT OF cursor-name clause cannot cite a cursor name that has been declared as dynamic.

在 UPDATE 和 DELETE 语句中，WHERE CURRENT cursor-name 子句不能引用已声明为动态游标的游标名称。

-4156 Warning: The loop counter may overflow.

This warning can occur for a FOR statement when the upper limit of the FOR loop is within the STEP value of the maximum value of that type. As an example, suppose the FOR statement tried to run IX from 1 to 32760 with a step of 20, and IX was declared as SMALLINT; the compiler would issue the warning because IX would overflow without satisfying the loop termination condition.

当 FOR 循环的上限在该类型的最大值的 STEP 值内时，可能会发生此警告。例如，假设 FOR语句试图以 20 步从 1 到 32760 运行IX，并且 IX 被声明为 SMALLINT；编译器会发出警告，因为 IX 会溢出，而不满足循环终止条件。

-4157 The statement is too complex. Try to simplify it.

This error occurs if a stack overflow is detected during compilation.

Under Windows, the stack size is limited. Try to reduce the complexity of your code. Complex expressions, such as many string concatenations('||'), can consume a large portion of the stack.

如果在编译期间检测到堆栈溢出，则会发生此错误。在 Windows 下，堆栈大小有限。尽量减少代码的复杂性。复杂的表达式（如多个字符串连接（'||'））可能占用大部分堆栈。

-4158 GBase 8s FORM and WINDOW statements are not supported in this product. Use the Visual Class Library for screen interaction.

The compiler encountered an OPEN FORM or OPEN WINDOW statement. In NewEra, these functionalities are handled through Visual Class Library objects. Consult the Graphical and Connectivity Reference Manual. Other grammatical errors might be generated in addition to this one.

Replacing the offending statements with VCL calls and recompiling should eliminate the additional messages.

编译器遇到 OPEN FORM 或 OPEN WINDOW 语句。在 NewEra 中，这些功能是通过Visual Class Library 对象处理的。请参阅图形和连接参考手册。除此之外，可能会产生其他语法错误。用 VCL 调用替换违规语句并重新编译应该可以排除附加的消息。

-4159 Subscripting cannot be applied to the expression because it is not a character or array reference.

The expression cannot be qualified by a subscript because the expression is neither an ARRAY nor CHAR() type.

表达式不能由下标限定，因为表达式既不是 ARRAY 也不是 CHAR() 类型。

-4160 This expression cannot be used as the target of an assignment statement.

An illegal assignment was detected. For example, you declared abc to be a constant, but here you attempted to assign a value to it. Some statements that involve assignment: LET, SELECT...INTO, OPEN CURSOR...INTO, FETCH INTO, FOREACH...INTO, FOR iterator (the iterator is assigned values), INITIALIZE, and LOCATE. Only NewEra returns this error.

检测到非法赋值。例如，将 abc 声明为常量，但在此试图为其赋值。涉及赋值的语句有：LET、SELECT ... INTO、OPEN CURSOR ... INTO、FETCH INTO、FOREACH ... INTO、FOR iterator（迭代器赋值）、INITIALIZE 和 LOCATE。只有 NewEra 返回此错误。

-4161 This variable has not been defined as a record or object.

The variable indicated has been used with an asterisk or with the THRU or THROUGH keywords. However, it has not been defined as a record or an object. Check the spelling of the name. If it is as you intended,locate the definition of the variable, and find out why it was not defined as expected. Only NewEra returns this error.

指示的变量已于星号或 THRU 或 THROUGH 关键字一起使用。但是，它没有被定义为记录或对象。检查名称的拼写。如果它是您想要的，找到变量的定义，并找出它没有按预期定义的原因。只有 NewEra 返回此错误。

-4162 Values cannot be RETURNed from within reports.

A report cannot include a RETURN statement because that would return control to the routine that invoked the report.

报告不能包含 RETURN 语句，因为这会将控制权返回给调用报告的例程。

-4163 Intrinsic function "name" of class "class" cannot be called directly.

Constructors of the form classname::classname() are invoked through the NEW operator. The classname::!copy() is invoked through the COPY operator. The classname::!derive() is invoked through the AS clause in both the NEW and the COPY operator. Only NewEra returns this error.

通过 NEW 运算符调用形如 classname::classname() 的构造函数。classname::!copy()通过 COPY 运算符调用。通过 NEW 和 COPY 运算符中的AS 子句调classname ::!derive()。

只有 NewEra 返回此错误。

-4164 The variable is too complex a type to be used in an assignment statement.

The type of the variable cannot be used in an assignment.That is, you cannot assign a value (except for the nonvalue NULL) to a BYTE or TEXT variable. You cannot assign any value to an ARRAY variable.

变量的类型不能用于赋值。也就是说，不能将值（除了非值 NULL）赋值给 BYTE 或 TEXT 变量。不能将任何值分配给 ARRAY 变量。

-4167 The PRAGMA LOCATION statement should be the last statement on the line.

No other NewEra statement can follow PRAGMA LOCATION on the same line.

If your source file includes any other NewEra statement or compiler directive after PRAGMA LOCATION, insert a linefeed character immediately following the end of the PRAGMA LOCATION compiler directive. (The last specification of PRAGMA LOCATION must be a line number, a filename, or the keyword RESET.)其他 NewEra 声明都不能与 PRAGMA LOCATION 同行。如果源文件在 PRAGMA LOCATION之后包含任何其他 NewEra 语句或编译器指令，请在 PRAGMA LOCATION 编译器指令结束后立即插入换行符。（PRAGMA LOCATION 的最后一个规格必须是行号、文件名或关键字 RESET。）-4168 An unexpected character was detected in this NewEra name.

A multibyte character (or other non-ASCII character that supports the locale) was found in the name of a NewEra identifier. For this release of NewEra, multibyte characters and other locale-specific characters are not valid in NewEra identifiers.

NewEra 标识符的名称中含有多字节字符（或支持其它语言环境的非 ASCII 字符）。对于此版本的 NewEra，多字节字符和特定于其它语言环境的字符在 NewEra 标识符中无效。

-4169 Error loading locale.

A failure occurred in trying to load the CLIENT_LOCALE locale file.

Verify that the specified files exist, that these files have appropriate permissions set, and that sufficient space is available in which to load them.

尝试加载 CLIENT_LOCALE 语言环境文件时发生故障。请验证指定的文件是否存在，这些文件是否设置了适当的权限，并且有足够的空间可用于加载它们。

-4200 Write error -- out of disk space.

The compiler failed to write some information to the output file because it ran out of disk space.

编译器无法将一些信息写入输出文件，因为它的磁盘空间不足。

-4201 Write error. Check available disk space and ulimit.

The compiler failed to write some information to the output file, but the cause of the error was not reliably determined. This usually means that the ulimit was exceeded, but possibly the error was detected too late for the auxiliary information to be accurate, or other errors have occurred since.

编译器未能将一些信息写入输出文件，但错误原因没有可靠地确定。这通常意味着 ulimit 超限，但可能错误被检测得太晚，以致辅助信息无法准确，或者此后发生了其他错误。

-4202 The compilation was not successful. Errors found: n. The file filename was not written successfully either.

The compiler failed to produce the output file because of errors and it also failed to produce the error file. Probably not enough disk space was available.

编译器由于错误而无法生成输出文件，也无法生成错误文件。可能没有足够的磁盘空间可用。

-4203 The compilation was successful, with n warnings. The file filename was not written successfully.

The compiler produced the output file. It also detected some warnings,and it failed to produce the error file as well. Probably not enough disk space was available.

编译器生成了输出文件。它还检测到一些警告，并且也无法生成错误文件。可能没有足够的磁盘空间可用。

-4300 This statement contains too many levels of function call nesting.

This statement has calls to functions that are nested within the parameter lists of other function calls, to a level exceeding four. The maximum level supported is four, as in the following expression:Afun(2-Bfun(3+Cfun(4*Dfun(5)))).

该语句调用嵌套在其他函数调用的参数列表中的函数，其层级超过 4。支持的最高层级是四，如以下表达式所示：Afun(2-Bfun(3+Cfun(4*Dfun(5))))。

Rewrite the expression to store the result of the innermost function calls in a variable, and use the variable in the expression.

重写表达式以将最内层函数调用的结果存储在变量中，并在表达式中使用该变量。

-4301 The program has too many levels of WHILE, FOR, MENU, and/or CASE statements.

You can only nest CASE, FOR, MENU, and WHILE statements (in any combination)to a depth of 25. Rearrange the program so that the nesting depth does not exceed 25, for example, by moving some of the inner structures to a separate module or isolating them in a function.

您只能将 CASE、FOR、MENU 和 WHILE 语句（以任意组合）嵌套 25 层。重新排列程序以使嵌套深度不超过 25。例如，通过将某些内部结构移动到单独的模块或在函数中分隔它们。

-4302 The record description is nested too deep.

Rewrite the record definition so that it does not exceed the limit of five nested levels of records.

请重写记录定义，使其不超过五个嵌套层级的限制。

-4303 A blob variable or cursor name expected.

The argument to the FREE statement must be the name of a cursor or prepared statement or, in 4GL, the name of a variable with the BYTE or TEXT data type.

FREE 语句的参数必须是游标或预准备语句的名称，或者在 4GL 中是带 BYTE 或 TEXT数据类型的变量的名称。

-4304 A different database has already been declared. If your program uses a global definition file, it must contain the same database name as this one.

This module contains a non-procedural DATABASE statement and also uses the GLOBALS filename statement to include a global definitions file. In that file there is a DATABASE statement that names a different database. Change either the module or the globaldefinitions file so they name the same database.

此模块包含非程序化 DATABASE 语句，并使用 GLOBALS 文件名语句包含全局定义文件。在该文件中有一个名为不同数据库的 DATABASE 语句。请更改模块或全局定义文件，以便命名相同的数据库。

-4305 The database "name" cannot be found or opened. If the database exists, check the database permissions on the database. In addition,check the system permissions on the database directory and its ascendant directories.

Check the spelling of the database name. Check that the database name exists in your current directory or in a directory included in your DBPATH environment variable. If the database is in a different directory, make sure that you have the ability to read that directory(to test this, make it the current directory and list the names of files in it). If these items are correct, make sure that you have at least CONNECT privilege for the database.

检查数据库名称的拼写。检查数据库名称在当前目录或在 DBPATH 环境变量中包含的目录中是否存在。

如果数据库位于不同的目录中，请确保您有能力读取该目录（测试目录，将其作为当前目录并列出其中的文件名称）。如果这些条目是正确的，请确保您至少具有数据库的 CONNECT 权限。

-4306 The GLOBALS file "pathname" cannot be opened for reading.

The file specified in the GLOBALS statement cannot be opened.

Check that the file exists and that you can read it, for example, by displaying it with an operating system command. If these items are correct, double-check the spelling of the pathname. If the file is not in the current directory, give the complete path.

GLOBALS 语句中指定的文件无法打开。请检查文件是否存在，以及是否可以读取它。例如，通过使用操作系统命令显示该文件。如果这些条目正确，请仔细检查路径名的拼写。如果文件不在当前目录中，请输入完整路径。

-4307 The number of variables and/or constants in the display list does not match the number of form fields in the display destination.

There must be exactly as many items in the list of values to display as there are fields listed following the TO keyword.

在要显示值列表中，必须包含与 TO 关键字后面列出的字段相同的项。

-4308 The number of input variables does not match the number of form fields in the screen input list.

Your INPUT statement must specify the same number of variables as it does fields. When checking this, keep in mind that when you refer to a record using an asterisk or THRU, it is the same as listing each record component individually.

您的 INPUT 语句必须指定与字段相同数量的变量。在检查时，请记住，当使用星号或 THRU引用记录时，这与单独列出每个记录组件是一样的。

-4309 Printing cannot be done within a loop or CASE statement contained in report headers or trailers.

4GL needs to know how many lines of space will be devoted to page headers and trailers; otherwise, it does not know how many detail rows to allow on a page. Since it cannot predict how many times a loop will be executed, or which branch of a CASE will be execute, it forbids the use of PRINT in these contexts within FIRST PAGE HEADER, PAGE HEADER,and PAGE TRAILER sections. You have to rearrange the code to place the PRINT statement where it will always be executed.

4GL 需要知道将有多少空间用于页眉和页尾；否则，它不知道在页面上允许多少行。由于无法预测循环将执行多少次，或 CASE 的哪个分支将被执行，因此它禁止在这些上下文的 FIRST PAGE HEADER、PAGE HEADER、和 PAGE TRAILER 中使用 PRINT。您必须重新排列代码，以便将 PRINT 语句放置在始终执行的位置。

-4310 Files cannot be printed within report headers or trailers.

4GL needs to know how many lines of space will be devoted to page headers and trailers; otherwise, it does not know how many detail rows to allow on a page. Since it cannot predict how many lines are in a file, it forbids printing a file in a header or trailer. You can write PRINT statements in the control blocks for FIRST PAGE HEADER, PAGE HEADER, and PAGE TRAILER. However, you cannot write PRINT FILE statements in these control blocks.

4GL 需要知道将有多少空间用于页眉和页尾；否则，它不知道在页面上允许多少行。由于无法预测循环将执行多少次，它禁止在页眉和页尾打印文件。可以在 FIRST PAGE HEADER、PAGE HEADER、和 PAGE TRAILER 的控制块中编写 PRINT。但是您不能在这些控制块中写 PRINT FILE 语句。

-4311 The variable "variable-name" was not defined as a record.

It cannot be used in this fashion.

The variable name that is shown is being used with THRU (or THROUGH)notation or with .* notation, but is not defined as a record.

Check that the variable name is the one that you intended. If it is,find the place where it is defined (which may be in a global definition file included with the GLOBALS statement) and find out why it is no longer defined as a record.

显示的变量名正在与 THRU（或 THROUGH）表示法或 .* 表示法一起使用，但未被定义为记录。检查变量名称是否是您想要的名称。如果是，找到定义它的位置（可能位于 GLOBALS语句的全局定义文件中）并找出它不再被定义为记录的原因。

-4312 The NEED statement is allowed only within reports.

The NEED n LINES statement is used in a report to cause a conditional page skip. This is only relevant in the context of the FORMAT section of a report. Check to see if a REPORT statement has been omitted.

在报告中使用 NEED n LINES 语句导致条件页跳过。这只在报告的 FORMAT 部分中有用。

检查是否省略了 REPORT 语句。

-4313 The NEED statement cannot be used within report headers or trailers.

The NEED n LINES statement is used in a a report to cause a conditional page skip. In the context of a FIRST PAGE HEADER, PAGE HEADER, and PAGE TRAILER section, however, it is irrelevant. If it did cause a page skip, an endless loop could ensue.

在报告中使用 NEED n LINES 语句导致条件页跳过。然而，在 FIRST PAGE HEADER、PAGE HEADER 和 PAGE TRAILER 部分的上下文中，这是无关紧要的。如果确实导致页面跳过，则可能会出现无限循环。

-4314 The program cannot continue or exit a menu at this point because it is not within a MENU statement.

This CONTINUE or EXIT statement uses the MENU keyword, but it is not located within a COMMAND section of a MENU statement. Either the statement is in error, or some other error has prevented 4GL from recognizing the MENU statement.

该 CONTINUE 或 EXIT 语句使用 MENU 关键字，但它不在 MENU 语句的 COMMAND 部分。

该语句可能是错误的，或者其他错误阻止了 4GL 识别 MENU 语句。

-4315 The program cannot exit a FOREACH statement at this point because it is not within a FOREACH statement.

This CONTINUE or EXIT statement uses the FOREACH keyword, but it is not located within a FOREACH loop. Either the statement is in error, or some other error has prevented 4GL from recognizing the FOREACH statement.

该 CONTINUE 或 EXIT 语句使用 FOREACH 关键字，但它不在 FOREACH 循环中。

该语句可能是错误的，或者其他错误阻止了 4GL 识别 FOREACH 语句。

-4316 The program cannot exit a WHILE statement at this point because it is not within a WHILE statement.

This CONTINUE or EXIT statement uses the WHILE keyword, but it is not located within a WHILE loop. Either the statement is in error, or some other error has prevented 4GL from recognizing the WHILE statement.

此 CONTINUE 或 EXIT 语句使用 WHILE 关键字，但它不在 WHILE 循环内。

该语句可能是错误的，或者其他错误阻止了 4GL 识别 WHILE 语句。

-4317 The program cannot exit a FOR statement at this point because it is not within a FOR statement.

This CONTINUE or EXIT statement uses the FOR keyword, but it is not located within a FOR loop. Either the statement is in error, or some other error has prevented 4GL from recognizing the FOR statement.

此 CONTINUE 或 EXIT 语句使用 FOR 关键字，但它不在 FOR 循环内。

该语句可能是错误的，或者其他错误阻止了 4GL 识别 FOR 语句。

-4318 The program cannot exit a CASE statement at this point because it is not within a CASE statement.

This CONTINUE or EXIT statement uses the CASE keyword, but it is not located within a CASE statement. Either the statement is in error, or some other error has prevented 4GL from recognizing the CASE statement.

此 CONTINUE 或 EXIT 语句使用 CASE 关键字，但它不在 CASE 循环内。

该语句可能是错误的，或者其他错误阻止了 4GL 识别 CASE 语句。

-4319 The symbol variable-name has been defined more than once.

The variable that is shown has appeared in at least one other DEFINE statement before this one. If this DEFINE is within a function or the MAIN section, the prior one is also. If this DEFINE is outside any function, the prior one is also outside any function; however, it might be within the file included by the GLOBALS statement.

显示的变量至少出现在此语句之前的另一个 DEFINE 语句中。如果该 DEFINE 在函数或 MAIN 部分中，那么前面的部分也是。如果此 DEFINE 在任何函数之外，则前面的函数也在任何函数之外；但是，它可能在 GLOBALS 语句包含的文件中。

-4320 The symbol table-name is not the name of a table in the specified database.

The named table does not appear in the database that is named in the latest DATABASE statement. It may be spelled wrong in the program, or the table might have been dropped or renamed since the last time the program was compiled.

指定的表不会出现在最新 DATABASE 语句指定的数据库中。它可能在程序中拼写错误，或者自上次编译程序以来表可能已被删除或重命名。

-4321 An array may have the maximum of three dimensions.

You have written more than three subscripts following the name of an array. However, 4GL only supports arrays of three dimensions or fewer.

Check the syntax of the subscript; an extra comma might have been entered in error.

您已经在数组的名称后面写入了三个以上的下标。但是，4GL 仅支持三维或更小的数组。

请检查下标的语法；可能错误地输入了额外的逗号。

-4322 The symbol column-name is not the name of a column in the specified database.

The preceding statement suggests that the named column is part of a certain table in the database that is in the last DATABASE statement.

The table exists, but the column does not appear in it. Check the spelling of the column name. If it is spelled as you intended, then either the table has been altered, or the column renamed, or you are not accessing the database you expected.

上述语句表明，该命名列是数据库中某个表的一部分，该表在最后一个 DATABASE 语句中。

该表存在，但该列不在其中显示。检查列名称的拼写。如果它按照您的意图进行拼写，那么表已被更改，或者列已重命名，或者没有访问您所期望的数据库。

-4323 The variable variable-name is too complex a type to be used in an assignment statement.

The named variable is a record or an array. 4GL does not support the assignment of whole records or arrays. In the case of a record, you must assign the individual record components, or you can assign groups of components to groups of components using asterisk notation. In the case of an array, you must use a subscript to designate a single array element. This error is not produced by any version of 4GL later than Version 4.1.

指定的变量是一个记录或一个数组。4GL 不支持给整个记录或数组赋值。在记录的情况下，必须为单个记录组件赋值，或者可以使用星号符号将组的组件分配给组。对于数组，必须使用下标来指定单个数组元素。4GL 的任何版本都不会在 V4.1 之后产生此错误。

-4324 The variable variable-name is not a character type, and cannot be used to contain the result of concatenation.

This statement attempts to concatenate two or more character strings(using the comma as the concatenation operator) and assign the result to the named variable. Unfortunately, it is not a character variable.

4GL will not perform automatic conversion from characters in this case.

Assign the concatenated string to a character variable; then, if you want to treat the result as numeric, assign the string as a whole to a numeric variable.

此语句尝试连接两个或多个字符串（使用逗号作为连接运算符）并将结果分配给指定的变量。不幸的是，该变量不是字符变量。在这种情况下，4GL 不会执行字符的自动转换。将连接字符串分配给字符变量；那么，如果想将结果视为数字，请将该字符串作为整体分配给数字变量。

-4325 The source and destination records in this record assignment statement are not compatible in types and/or lengths.

This statement uses asterisk notation to assign all components of one record to the corresponding components of another. However, the components do not correspond. Note that 4GL matches record components strictly by position, the first to the first, second to second, and so on; it does not match them by name. If the source and destination records do not have the same number and type of components, you will have to write a simple assignment statement for each component.

该语句使用星号符号将一个记录的所有组件分配给另一个记录的相关组件。但是，组件不对应。

请注意，4GL 严格按位置匹配记录组件，第一个对第一个，第二个对第二个等；而不是通过名称匹配。如果源记录和目标记录没有相同数量和类型的组件，则必须为每个组件编写简单的赋值语句。

-4326 A NULL value may not be applied to substrings.

The value NULL is a whole value that is relevant to complete variables only. You can assign NULL to the name of this variable (omitting the substring notation) to make the entire variable contain the null string. Alternatively, you can assign spaces to a substring to make it blank. The only way to delete a portion of a string is to write an expression that extracts the leading and trailing substrings that are to be retained and concatenates them.

NULL 值是一个完整的值，只与完整的变量有关。您可以将 NULL 赋值给此变量的名称（省略子字符串表示法）以使整个变量包含空字符串。或者，可以将空格分配给子字符串，使其为空。删除字符串的一部分的唯一方法是编写一个表达式，该表达式提取要保留的前导和后续子字符串，并将它们连接起来。

-4327 The variable variable-name is not of type INTEGER or SMALLINT. It cannot be used as a loop index.

The index variable in a FOR loop must be an integer type. Specify a different variable, or redefine the one named.

FOR 循环中的索引变量必须是整数类型。指定不同的变量，或重新定义命名的变量。

-4328 The variable variable-name has too complex a type to be used as the destination of a return from a function.

The named variable is a record or an array. Only simple variables can be returned by a function, although the function can return a list of simple variables. In the case of a record, you can use the asterisk or THRU notation as shorthand to specify a list of components.

命名的变量是一个记录或一个数组。虽然函数可以返回简单变量列表，但函数只能返回简单变量。

在记录的情况下，可以使用星号或 THRU 符号作为简写来指定组件列表。

-4329 The variable variable-name is not a record. Only record variables may be expanded using the .* or THROUGH shorthand.

You have used the displayed name with either dot-asterisk (.*) or the word THRU (or THROUGH), which is shorthand notation to specify a list of the components of a record. Unfortunately, the variable is not defined as a record. Make sure that you specified the right variable and that it is defined as a record.

您已使用带星号（.*）或 THRU（或 THROUGH）这个简写符号的显示名称来指定记录组件的列表。

不幸的是，该变量没有被定义为记录。确保您指定了正确的变量并将其定义为记录。

-4330 Values cannot be RETURNed from the MAIN program.

Although RETURN is equivalent to EXIT PROGRAM in a MAIN program, it cannot include a value to be returned. NewEra programs return this error.

虽然 RETURN 与 MAIN 程序中的 EXIT PROGRAM 相同，但不能包含要返回的值。NewEra 程序返回这个错误。

-4331 Only variables of type INTEGER or SMALLINT may be used to index display fields This statement uses a subscript to refer to one element of a screen array. However, the subscript variable is not an integer type. Make sure that the subscripting variable is the one you intended to use,and make sure it is defined as INTEGER or SMALLINT.

该语句使用下标来引用屏幕数组的一个元素。但是，下标变量不是整数类型。

确保下标变量是您要使用的变量，并确保将其定义为 INTEGER 或 SMALLINT。

-4332 The LET statement must have at least one source expression.

This LET statement has no valid expression to the right of the equals sign. Check the punctuation; perhaps part of the statement was deleted in error, or perhaps a comment delimiter has been inserted in the wrong place.

LET 语句等号右边的表达式无效。请检查标点符号；或许错误地删除了部分语句；或者可能是在错误的地方插入了注释分隔符。

-4333 The name has already been called with a different number of parameters.

Earlier in the program, there is a call to this same function or event with a different number of parameters in the parameter list. At least one of these calls must be in error. Examine the FUNCTION or EVENT statement for name to find out the correct number of parameters. Then examine all calls to it, and make sure that they are written correctly.

When this error appears near the top of a function in conjunction with error -4336, fix error -4336 first, and -4333 will usually disappear.

NewEra programs return this error.

在程序的前面，会调用这个函数或事件，参数列表中有不同数量的参数。这些调用中至少有一个必须出错。检查 FUNCTION 或 EVENT 语句的名称，找出正确的参数。然后检查对它的所有调用，并确保它们编写正确。当此错误与错误 -4336 一起出现在函数顶部附近时，首先修复错误 -4336，并且 -4333 通常会消失。NewEra 程序返回此错误。

-4334 The variable variable-name in its current form is too complex to be used in this statement.

By "too complex" 4GL means "has too many component parts." In this statement, only simple variables (those that have a single component)can be used. If variable-name is an array, you must provide a subscript to select just one element. If it is a record, you must choose just one of its components. (However, if this statement permits a list of variables, as in the INITIALIZE statement, you can use asterisk or THRU notation to convert a record name into a list of components.)4GL 的“太复杂”是说具有太多的组件。在该语句中，只能使用简单变量（具有单个组件的变量）。

如果 variable-name 是数组，必须提供下标来选择元素。如果它是记录，则必须选择其中一个组件。（但是，如果此语句允许使用变量列表（如在 INITIALIZE 语句中那样），则可以使用星号或 THRU 表示法将记录名称转换为组件列表。）-4335 The symbol field is not an element of the record record.

This statement refers to record.field. Although the variable record is indeed a record, field is not the name of one of its component fields.

Find the definition of record (it may be in the GLOBALS file), verify the names of its fields, and correct the spelling of field.

该语句引用了 record.field。虽然变量记录确实是一条记录，但字段不是其组件字段的名称。

查找记录的定义（可能位于 GLOBALS 文件中），验证其字段的名称，并更正字段的拼写。

-4336 The parameter variable-name has not been defined within the function or report.

The name variable-name appears in the parameter list of the FUNCTION statement for this function. However, it does not appear in a DEFINE statement within the function. All parameters must be defined in their function before use. Possibly you wrote a DEFINE statement but did not spell variable-name the same way in both places.

variable-name 出现在该函数的 FUNCTION 语句的参数列表中。但是，它不会出现在函数中的 DEFINE 语句中。使用前必须在函数中定义所有参数。可能编写了 DEFINE 语句，但是在两个地方都没有以相同的方式拼写变量名。

-4338 The symbol variable-name has already been defined once as a parameter.

The name that is shown appears in the parameter list of the FUNCTION statement and in at least two DEFINE statements within the function body. Only one appearance in a DEFINE statement is permitted.

显示的名称出现在 FUNCTION 语句的参数列表中，并且在函数中至少有两个 DEFINE 语句。

在 DEFINE 语句中只允许出现一个。

-4339 4GL has run out of data space memory.

Your 4GL program requires more memory than is available.

If your program was executing sucessfully prior to this message, examine your code to see if FREE, CLOSE FORM,CLOSE WINDOW, or other 4GL statements can release memory used by 4GL program objects that are no longer needed.

4GL 程序需要更多的内存。如果程序在发出此消息之前执行成功，请检查您的代码以查看 FREE、CLOSE FORM、CLOSE WINDOW 或其他 4GL 语句是否可以释放不再需要的 4GL 程序对象所使用的内存。

If your program was using a shared memory connection, try setting GBASEDBTSHMBASE to a larger value. Alternatively,use a streams (olipcstr) or network (oltlitcp) connection.

如果程序使用共享内存连接，请尝试将 GBASEDBTSHMBASE 设置为更大的值。

或者，使用流（olipcstr）或网络（oltlitcp）连接。

If you receive this message during compilation, a .4gl source module might be too large to compile. Divide it into smaller modules, and compile them separately. If the error persists, divide the 4GL program into smaller programs.

如果在编译期间收到此消息，则 .4gl 源模块可能太大而无法编译。将它分成更小的模块，并分别进行编译。如果错误仍然存在，请将 4GL 程序分成更小的程序。

-4340 The variable variable-name is too complex a type to be used in an expression.

By "too complex," NewEra means "has too many component parts." In an expression, only simple variables (those that have a single component)can be used. If the variable indicated is an array, you must provide a subscript to select just one element. If it is a record or object, you must choose just one of its components. NewEra programs return this error.

4GL 的“太复杂”是说具有太多的组件。在表达式中，只能使用简单变量（具有单个组件的变量）。

如果指示的变量是数组，必须提供下标来选择元素。如果是记录或对象，则必须选择其中一个组件。

NewEra 程序返回此错误。

-4341 Aggregate functions are only allowed in reports and SELECT statements.

Aggregate functions such as SUM, AVG, and MAX can only appear in SQL statements and within certain statements you use in the context of a report body. They are not supported in ordinary expressions in program statements. You might be able to write an application-specific function to form this aggregate function on your data; however, you must name it something else because names such as SUM, AVG, and MAX are reserved words.

例如 SUM、AVG 和 MAX 之类的聚集函数只能出现在 SQL 语句中以及在报表正文上下文中使用的某些语句中。程序语句的一般表达式中不支持它们。您可能可以编写一个特定于应用程序的函数，以在数据上形成这个聚集函数;但是，必须将其命名为其他名称，因为名称（如 SUM、AVG 和 MAX）是保留字。

-4342 PAGENO and LINENO are allowed only in reports.

These functions are only relevant in the body of a report function (one following a REPORT statement). Only within the report-generating code is the idea of a current page or line meaningful. You can make these values available outside a report through global variables. For example, you could put a statement such as this one in the PAGE HEADER control block:这些函数只与报表函数的正文相关（在 REPORT 语句之后）。只有在报表生成代码中，当前页面或行的概念才有意义。可以通过全局变量使这些值在报表外部可用。例如，可以在 PAGE HEADER 控制块中放置如下所示的语句：LET CURR_PAGE = PAGENO This would assign the current page to a global variable (called CURR_PAGE in the example) that could be tested by code outside the report function.

这会将当前页面分配给全局变量（在本例中称为 CURR_PAGE），该变量可以由报表函数外部的代码进行测试。

-4343 Subscripting cannot be applied to the expression because it is not a character or array reference.

You can write subscript expressions (integer-valued expressions separated by commas and enclosed in square brackets) following an expression that evaluates to an array. You can specify a substring (two integer expressions in square brackets) following a character expression. However, in this statement, expressions in square brackets follow something that is neither character nor an array. Review the punctuation of the statement and the declaration of the variables in it. Error -4343 with this text is produced by 4GL through Version 4.1.

可以在求值为数组的表达式后面编写下标表达式（用逗号分隔的整数值表达式并用方括号括起来）。

可以在字符表达式后面指定一个子字符串（两个整数表达式包括在方括号内）。但是，在这个语句中，方括号中的表达式跟随的既不是字符也不是数组。请查看语句的标点符号和变量的声明。本文的错误 -4343 是由 V4.1 版本的 4GL生成的。

-4344 The variable variable-name cannot be used with substrings because it is not a character variable.

This statement contains what appears to be a substring expression (two numbers in square brackets) following the identifier shown. However,that variable is not of data type CHAR or VARCHAR. If you intended this variable as a substring, then you either named the wrong variable, or the variable is not correctly defined. If you meant this as an array subscript, the same is true.

该语句包含一个子字符串表达式（方括号中有两个数字），它位于所示的标识符后面。但是，该变量不是 CHAR 或 VARCHAR 数据类型。如果希望将此变量作为子字符串，那么要么命名了错误的变量，要么该变量未正确定义。如果把它当作一个数组下标，情况也是如此。

-4345 The variable variable-name has already had substrings applied to it.

The name that is shown is followed by one substring expression (two numbers in square brackets) and then by another. This is not valid.

Perhaps some punctuation was deleted accidentally in editing the name of another variable. Or if you meant this to be a subscript of a two-dimensional array of character items followed by a substring of the chosen element, the problem is that variable-name has not been defined as an array.

显示的名称后跟一个子字符串表达式（方括号中有两个数字），然后是另一个。这是无效的。

在编辑另一个变量的名称时，可能删除了一些标点符号。或者，如果您的意思是这是一个字符项的二维数组的下标，后跟所选元素的子字符串，那么问题是变量名还没有被定义为数组。

-4346 Subscripts can contain only INTEGER or SMALLINT expressions.

Array subscripts are integer values, and only integer variables can be used to form them. This statement contains a subscript in which a FLOAT, CHAR or some other type of variable is used. No automatic conversion of data types is performed in a subscript expression. Review the subscript expressions in the statement; perhaps you simply entered the wrong variable name. If not, you will have to revise the program to store array subscripts in integer variables only (you might expect that a DECIMAL value with a scale factor of zero would be permitted also,but this is not the case.)数组下标是整数值，只能使用整数变量。该语句包含一个下标，使用 FLOAT、 CHAR 或其他类型的变量。下标表达式不会自动转换数据类型。请查看语句中的下标表达式;也许只是输入了错误的变量名称。如果不是，请修改程序，将数组下标存储在整数变量中（您可能期望一个比例因子为零的 DECIMAL 值也是允许的，但事实并非如此）。

-4347 The variable variable-name is not a record. It cannot reference record elements.

In this statement variable-name appears followed by a dot, followed by another name. This is the way you would refer to a component of a record variable; however, variable-name is not defined as a record.

Either you have written the name of the wrong variable, or else variable-name is not defined the way you intended.

在这个语句中，变量名称后面跟着一个点，后面跟着另一个名称。这是您引用记录变量的组件的方式；但是，变量名称没有被定义为记录。要么是变量名称错误，要么变量名没有按想要的方式定义。

-4348 This type of aggregate must be applied to an expression,not '*'. Only PERCENT and COUNT aggregates use '*'.

An aggregate function in this statement is one of those, such as MIN and SUM, that must be applied to a specific column or to an expression involving specific columns. The asterisk notation in an SQL statement means "the whole row." With an aggregate function, it is useful only when counting entire rows.

此语句中的聚集函数是必须应用于特定列或涉及特定列的表达式的聚合函数之一，如 MIN 和 SUM。

SQL语句中的星号符号表示“整行”。对于聚合函数，它只在计数整行时才有用。

-4349 The PERCENT and COUNT report aggregates cannot be used with an expression.

These aggregate functions simply count entire rows, without regard for the contents of the rows. COUNT returns a count of the rows, and PERCENT returns the count of rows as a percentage of the entire table.

The only permitted parameters of these functions '*' mean "the entire row." They cannot be applied to specific columns or to expressions that involve specific columns.

这些聚集函数只对整行进行计数，而不考虑行的内容。COUNT 返回行计数，PERCENT 返回行计数占整个表的百分比。这些函数的唯一允许参数“*”表示“整行”。它们不能应用于特定列或涉及特定列的表达式。

-4350 The program cannot continue a FOR loop at this time because it is not within a FOR loop.

A CONTINUE FOR statement is not between a FOR statement and its matching END FOR statement. Perhaps the FOR statement has been accidentally deleted, or perhaps you changed to another type of loop such as FOREACH or WHILE.

CONTINUE FOR 语句不在 FOR 语句和其匹配的 END FOR 语句之间。也许 FOR 语句被意外删除了，或者可能更改了另一种类型的循环，比如 FOREACH 或 WHILE。

-4351 The program cannot continue a WHILE loop at this time because it is not within a WHILE loop.

A CONTINUE WHILE statement is not between a WHILE statement and its matching END WHILE statement. Perhaps the WHILE statement has been accidentally deleted, or perhaps you changed to another type of loop such as FOREACH or FOR.

CONTINUE WHILE 语句不在 WHILE 语句和其匹配的 END WHILE 语句之间。也许 WHILE语句被意外删除了，或者可能更改了另一种类型的循环，比如 FOREACH 或 FOR。

-4352 The program cannot continue a FOREACH loop at this time because it is not within a FOREACH loop.

A CONTINUE FOREACH statement is not between a FOREACH statement and its matching END FOREACH statement. Perhaps the FOREACH statement has been accidentally deleted, or perhaps you changed to another type of loop such as WHILE or FOR.

CONTINUE FOREACH 语句不在 FOREACH 语句和其匹配的 END FOREACH 语句之间。

也许 FOREACH 语句被意外删除了，或者可能更改了另一种类型的循环，比如 WHILE 或 FOR。

-4353 The type of this ORDER BY or GROUP item specified for the report is not valid for sorting.

The database server does not support comparison functions on columns of such types as TEXT or BYTE. As a result, columns with such types cannot be used to order or group rows. Use other columns (usually the primary key of the table) for ordering and grouping.

数据库服务器不支持 TEXT 或 BYTE 等类型的列上的比较函数。因此，具有这种类型的列不能用于排序或分组。使用其他列（通常是表的主键）进行排序和分组。

-4354 Aggregate functions cannot be performed with TEXT or BYTE variables.

This statement applies an aggregate function such as SUM to a variable that is defined as BYTE or TEXT. Such variables are not in the domain of the aggregate functions. Review the use of functions in the statement, and make sure that they are applied to the variables you intended.

此语句将 SUM 之类的聚集函数应用于定义为 BYTE 或 TEXT 的变量。这些变量不在集合函数的域中。请检查语句中函数的用法，确保它们应用于您想要的变量。

-4356 A page header has already been specified within this report.

Only one PAGE HEADER control block is allowed in a report. The statements in this control block must be suitable for all pages of the report (except the very first page, for which you may write a FIRST PAGE HEADER block). Find the other PAGE HEADER control blocks, and combine all their statements into one control block.

报告中只允许有一个PAGE HEADER 控制块。该控制块中的语句必须适用于报表的所有页面（除了第一页外，您可以为其写入 FIRST PAGE HEADER 块）。请查找其他 PAGE HEADER控制块，并将所有语句组合到一个控制块中。

-4357 A page trailer has already been specified within this report.

Only one PAGE TRAILER control block is allowed in a report. The statements in this control block must be suitable for all pages of the report. Find the other PAGE TRAILER control blocks, and combine all their statements into one control block.

报表中只允许有一个 PAGE TRAILER 控制块。此控制块中的语句必须适用于报表的所有页面。

查找其他 PAGE TRAILER 控制块，并将其所有语句组合到一个控制块中。

-4358 A first page header has already been specified within this report.

Only one FIRST PAGE HEADER control block is allowed in a report. (After all, only one first page exists.) Find the other FIRST PAGE HEADER control blocks, and combine all their statements into one control block.

报表中只允许有一个 FIRST PAGE HEADER 控制块。（毕竟，只存在一个首页。）找到其他 FIRST PAGE HEADER 控制块，并将它们的语句组合成一个控制块。

-4359 An ON EVERY ROW clause has already been specified within this report.

Only one ON EVERY ROW control block is permitted in a report. Find the other ON EVERY ROW control blocks, and combine their statements into one block.

报表中只允许有一个 ON EVERY ROW 控制块。找到其他 ON EVERY ROW 控制块，并将它们的语句组合成一个控制块。

-4360 An ON LAST ROW clause has already been specified within this report.

Only one ON LAST ROW control block is permitted in a report. Find the other ON LAST ROW control blocks, and combine their statements into one block.

报表中只允许有一个 ON LAST ROW 控制块。找到其他 ON LAST ROW 控制块，并将它们的语句组合成一个控制块。

-4361 Group aggregates can occur only in AFTER GROUP clauses.

The aggregate functions that apply to a group of rows (GROUP COUNT,GROUP PERCENT, GROUP SUM, GROUP AVG, GROUP MIN, and GROUP MAX) can only be used at the point in the report when a complete group has been processed, namely, in the AFTER GROUP control block. Make sure that the AFTER GROUP statement exists and was recognized. If you need the value of a group aggregate at another time (for instance, in a PAGE TRAILER control block), you can save it in a global variable with a LET statement in the AFTER GROUP control block.

适用于一组行的聚集函数（GROUP COUNT、GROUP PERCENT、GROUP SUM、GROUP AVG、GROUP MIN 和 GROUP MAX）只能在处理完整组（即在 AFTER GROUP 控制块中）时在报告中使用。确保 AFTER GROUP 语句存在并已被识别。如果在另一时间需要组聚集的值（例如，在 PAGE TRAILER 控制块中），则可以在 AFTER GROUP 控制块中使用 LET语句将其保存在全局变量中。

-4362 The report cannot skip to the top of page while in a header or trailer.

When SKIP TO TOP OF PAGE is executed, the page trailer clause must be executed (so as to display fixed page-end material) followed by the page header clause. If the statement was allowed in a header or trailer clause, an infinite loop could ensue.

当执行 SKIP TO TOP OF 页面时，必须执行页尾子句（以便显示固定的页尾材料），后面跟着页头部分子句。如果在头部或尾部子句中允许语句，则会产生无限循环。

-4363 The report cannot skip lines while in a loop within a header or trailer.

4GL needs to know how many lines of space will be devoted to the page header and trailer (otherwise it does not know how many detail rows to allow on the page). It cannot predict how many times a loop will be executed, so it has to forbid the use of SKIP statements in loops in the PAGE HEADER, PAGE TRAILER, and FIRST PAGE HEADER sections.

4GL 需要知道有多少行空间将用于页头和页尾（否则它不知道页面上允许多少个明细行）。

它无法预测循环将执行多少次，因此它必须禁止在 PAGE HEADER、PAGE TRAILER 和FIRST PAGE HEADER 部分的循环中使用 SKIP 语句。

-4364 Type of initialization/default expression does not match declared type of the variable/parameter.

The initialization expression for the specified variable does not evaluate to a data type that is compatible with the declared type.

Review the expression, and make it and the declared type agree.

指定变量的初始化表达式不计算为与声明的类型兼容的数据类型。检查表达式，并使其与声明的类型一致。

-4365 Deferments of interrupt or quit may be executed only in the main program.

The statements DEFER INTERRUPT and DEFER QUIT can only appear in the MAIN section of the program. They can appear only once each in a program.

DEFER INTERRUPT 和 DEFER QUIT 语句只能出现在程序的 MAIN 部分。它们只能在程序中出现一次。

-4366 The number of variables does not match the number of database columns in this statement.

There must be a program variable to receive data from or supply data to each column named in the statement. Possibly there is an ambiguity between column names and variable names. When a program variable has the same name as a database column, you can force 4GL to use the database column by prefixing it with the at-sign (@) character or with its tablename.

必须有一个程序变量来接收来自语句中命名的每一列的数据或向其提供数据。列名和变量名之间可能存在歧义。当程序变量具有与数据库列相同的名称时，可以强制 4GL 使用数据库列，方法是在数据库列前面加上 at-符号(@)字符或表名。

-4367 Interrupt has already been deferred once in the main program.

Each main program may defer interrupts only once.

The statements DEFER INTERRUPT and DEFER QUIT can only appear in the MAIN section of the program. They can appear only once each in a program.

DEFER INTERRUPT 和 DEFER QUIT 语句指南出现在程序的 MAIN 部分。它们只能在程序中出现一次。

-4368 Quit has already been deferred once in the main program. Each main program may defer quit only once.

The statements DEFER INTERRUPT and DEFER QUIT can only appear in the MAIN section of the program. They can appear only once each in a program.

DEFER INTERRUPT 和 DEFER QUIT 语句指南出现在程序的 MAIN 部分。它们只能在程序中出现一次。

-4369 The symbol variable-name does not represent a defined variable.

The name shown appears where a variable would be expected, but it does not match any variable name in a DEFINE statement that applies to this context. Check the spelling of the name. If it is the name you intended, look back and find out why it has not yet been defined.

Possibly the GLOBALS statement has been omitted from this source module, or it names an incorrect file. Possibly this code has been copied from another module or another function, but the DEFINE statement was not copied also.

显示的名称出现在预期变量的位置，但它与适用于此上下文的 DEFINE 语句中的任何变量名都不匹配。检查名称的拼写。如果是想要的名称，回顾并找出为何还未定义的原因。可能已从此源模块中省略 GLOBALS 语句，或者它命名了不正确的文件。

可能这个代码已经从另一个模块或另一个函数中复制，但是没有复制 DEFINE 语句。

-4370 The variable variable-name cannot be used in validation.

The VALIDATE statement operates on only simple variables; it cannot accept records or arrays. If you have named a record, you can use asterisk notation or THRU notation as shorthand for a list of the component fields of the record. However, if a record component is itself a record, you must list its components individually as well.

VALIDATE 语句只能对简单变量进行操作；它不能接受记录或数组。如果您已命名了记录，则可以使用星号或 THRU 符号作为记录组件字段列表的简写。但是，如果记录组件本身就是记录，那么也必须单独列出其组件。

-4371 Cursors must be uniquely declared within one program module.

In the statement DECLARE cname CURSOR, the identifier cname can be used in only one DECLARE statement in the source file. This is true even when the DECLARE statement appears inside a function. Although a program variable made with the DEFINE statement is local to the function, a cursor within a function is still global to the whole module.

在 DECLARE cname CURSOR 语句中，标识符 cname 只能在源文件中的 DECLARE语句中使用。即使 DECLARE 语句出现在函数内时也是如此。虽然对于函数来说用 DEFINE语句创建的程序变量是局部的，但对整个模块来说函数中的游标仍然是全局的。

-4372 The cursor cursor-name has not yet been declared in this program module. It must be declared before it can be used.

The name shown appears where the name of a declared cursor or a prepared statement is expected; however, no cursor (or statement) of that name has been declared (or prepared) to this point in the program.

Check the spelling of the name. If it is the name you intended, look back in the program to see why it has not been declared. Possibly the DECLARE statement appears in a GLOBALS file that was not included.

所显示的名称出现在需要声明游标或预备语句的位置；但是，该名称的游标（或语句）尚未在程序中声明（或准备）。请检查名称的拼写。如果是您想要的名称，请在程序中查看它为什么没有被声明。可能 DECLARE 语句出现在未包含的 GLOBALS 文件中。

-4373 A grammatical error has been found on line line-number, character char-number. The construct is not understandable in its context.

This general message shows an inability to parse a 4GL statement. The line and character numbers show the point at which the parser detected a problem. However, this is almost never the point at which the error exists. Start there, and work backward in the program looking for other error messages and for missing punctuation, missing END statements, and other mistakes. If the statement at line-number is END FUNCTION, END MAIN, or END REPORT, one probable cause is the absence of another END, possibly many lines earlier. Usually a missing END IF is the culprit. If the cause for this error is not obvious, concentrate on eliminating any other, more specific error messages, and this one will probably go away also.

此一般消息显示无法解析 4GL 语句。行号和字符号显示解析器检测到问题的点。但是，这几乎从来不是发生错误的地方。从那里开始，并在程序中向后查找其他错误消息、查找缺少的标点符号、缺少的 END 语句和其他错误。如果行号中的语句是 END FUNCTION、END MAIN 或 END REPORT，则可能的原因之一是缺少另一个 END，可能有更多行。通常缺少 END IF 是罪魁祸首。如果造成此错误的原因并不明显，请集中精力消除任何其他更具体的错误消息，这个错误可能也会消失。

-4374 This type of statement can only be used within a MENU statement.

This statement, for example a SHOW OPTION statement, only makes sense within the context of a MENU statement. Review the program in this vicinity to see if an END MENU statement has been misplaced. If you intended to set up the appearance of a menu before displaying it, use a BEFORE MENU block within the scope of the MENU.

该语句（例如 SHOW OPTION 语句）仅在 MENU 语句的上下文中有意义。查看附近的程序，看看END MENU 语句是否放错了位置。如果要在显示菜单之前设置菜单的外观，请使用 MENU 范围内的 BEFORE MENU 块。

-4375 The page length is too short to cover the specified page header and trailer lengths.

Examine the statements in the OUTPUT section and in any HEADER and TRAILER clauses. The total of lines used by these statements must be sufficiently less than the specified page length that some detail rows can be printed.

检查 OUTPUT 部分和 HEADER 及 TRAILER 子句中的语句。这些语句使用的行总数必须足够小于指定的页面长度，以便打印一些详细信息。

-4376 The temporary file filename cannot be created for writing.

Check that your account, on UNIX systems, has permission to create files in the /tmp directory or in the directory named in the DBTEMP environment variable if that is different. Look for other, more explicit, error messages from the operating system. Possibly the disk is full, or you have reached a limit on the number of open files.

检查您的 UNIX 系统上的账户是否有权在 /tmp 目录中创建文件或有权在 DBTEMP 环境变量中指定的目录中创建文件。从操作系统中查找其它更明确的错误消息。可能磁盘已满，或者您打开文件的数量已达到限制。

-4377 The output file filename cannot be created or opened.

On UNIX systems, check that your account has permission to create files in the directory where filename would be created. Look for other, more explicit, error messages from the operating system. Possibly the disk is full, or you have reached a limit on the number of open files.

在 UNIX 系统上，检查您的账户是否有权在要创建文件名的目录中创建文件。从操作系统中查找其他更明确的错误消息。可能磁盘已满，或者您打开文件的数量已达到限制。

-4378 No input file was specified.

You invoked the C-code or the p-code compiler from the command line but did not specify the name of a source file to be edited. Repeat the command, specifying a source file.

您从命令行调用了 C-code 或 p-code 编译器，但没有指定要编辑的源文件的名称。

重复该命令，指定一个源文件。

-4379 The input filename filename cannot be opened.

Either the file does not exist, or, on UNIX, your account does not have permission to read it. Possibly the filename is misspelled, or the directory path leading to the file was specified incorrectly.

该文件不存在，或者在 UNIX 上，您的账户无权读取该文件。可能是文件名拼写错误，或指向文件的目录路径错误。

-4380 The listing file filename cannot be created.

Check that the directory path leading to the file is specified correctly and, on UNIX systems, that your account has permission to create a file in that directory. Look for other, more explicit, error messages from the operating system. Possibly the disk is full, or you have reached a limit on the number of open files.

检查指向文件的目录路径是否正确指定，并且在 UNIX 系统上，您的账户是否有权在该目录中创建文件。查找来自操作系统的其他更明确的错误消息。可能磁盘已满，或者您打开文件的数量已达到限制。

-4381 The input file filename has an invalid extension. The file name must have .4gl as the extension.

You do not need to enter the file extension or suffix of .4gl when you type the name of a program source file. However, if you do type a file suffix it must be .4gl; no other is allowed. If you type the suffix incorrectly, enter the command again omitting the suffix. If the file really has a different suffix, you will have to change it.

当键入程序源文件的名称时不需要输入文件扩展名 .4gl 后缀。但是，如果您确实键入了一个文件后缀，那么它必须是 .4gl；不允许其他文件后缀。如果输入的后缀不正确，请再次输入命令，省略后缀。如果文件确实有不同的后缀，则必须更改它。

-4382 Cannot expand a structure with an array member.

The ".*" and THROUGH notation cannot be used to expand a record with an array member, except in the LET statement. Error -4382 with this meaning is issued by NewEra.

除了 LET 语句之外，“.*”和“THROUCH”表示法不能用于使用数组成员展开记录。

错误 -4382 的这一含义是由 Newera 发布的。

-4382 Record variables that contain array type elements may not be referenced by the ".*" or THROUGH shorthand, or used as a function parameter.

You can define a record that contains an array as one of its components. However, you must always list that component by its full designation of record.part[n]. The asterisk or THRU notation is only shorthand for a list of the names of the components of the record. It cannot produce the bracketed subscript after the name of the array component.

您可以定义一个包含数组作为其组件的记录。但是，必须始终按照 record.part[n] 的完整定义来列出该组件。星号或 THRU 表示法只是记录组件名称列表的简写。它不能在数组组件的名称之后产生括号内的下标。

A record that contains an array component cannot be used as a parameter to a function. However, you can use the array component itself as a function parameter if you spell out its name as record.part. Error -4382 with this meaning is issued by NewEra.

包含数组组件的记录不能用作函数的参数。但是，如果将其名称拼写为 record.part，则可以将数组组件本身用作函数参数。错误 -4382 的这一含义是由 Newera 发布的。

-4383 The elements name-1 and name-2 do not belong to the same parent record.

The two names shown are used where two components of one record are required; however, they are not components of the same record. Check the spelling of both names. If they are spelled as you intended, go back to the definition of the record and see why it does not include both names as component fields.

如果需要记录的两个组件，则使用所示的两个名称；但是，它们不是同一记录的组件。检查两个名称的拼写。如果它们是按照您的意愿拼写的，请返回记录的定义，并了解为什么它不将两个名称都包含在组件字段中。

-4384 The symbol name does not represent the element of any record.

The name shown is used where 4GL expects the name of a record component. Check the spelling of the name. If it is spelled as you intended, go back to the definition of the record variable and see why it does not include name as a component field.

显示的名称用于 4GL 预计记录组件的名称。检查名称的拼写。如果按照您的意图进行拼写，请返回到记录变量的定义，并了解为什么它不将名称包含在组件字段中。

-4385 Report aggregates cannot be nested.

Aggregate functions cannot be nested, primarily because the value of the inner aggregate is not known at the time the outer aggregate is being accumulated. Rewrite aggregate expressions to refer only to columns and simple expressions on columns. In an AFTER GROUP OF clause,you can save the aggregate value from one group of rows in a program variable, so as to use it in computing an aggregate over a subsequent group.

聚集函数不能嵌套，主要是因为在聚集外部聚合时内部聚合的值未知。重写聚集表达式，只引用列和列上的简单表达式。在 AFTER GROUP OF 子句中，可以将一组行中的聚集值保存在程序变量中，以便在计算后续组的聚集时使用它。

-4386 There are too many ORDER BY fields in this report. The maximum number is number.

A limit exists on the number of ordering fields. You will have to redesign the report so that it requires ordering by no more than number columns. Alternatively you can order the data before passing it to the report, and specify the EXTERNAL keyword on the ORDER BY statement in the report body. It is generally more efficient to have the database server produce the rows in the correct order (using SELECT...ORDER BY in the cursor that produces the rows).

排序字段的数量存在限制。您必须重新设计报表，以便它按需要的列数排序。或者，您可以在将数据传递给报表之前对数据进行排序，并在报表正文中的 ORDERBY 语句上指定 EXTERNAL 关键字。让数据库服务器按照正确的顺序生成行通常更有效(在生成行的游标中使用 SELECT.Order by)。

-4387 The right margin must be greater than the left margin.

If the right margin of a report were no greater than the left margin,there would be no room on each line for data. Check both MARGIN statements in the OUTPUT section for reasonable values.

如果报表的右边距不大于左边距，则每行都没有容纳数据的空间。请检查 OUTPUT 部分中的两个 MARGIN 语句，以获取合理的值。

-4388 There is one BEFORE GROUP OF clause and one AFTER GROUP OF clause allowed for each report input parameter.

The report is attempting to define a second BEFORE GROUP OF or AFTER GROUP OF block for a single report parameter. Only one such control block is allowed. Find all the blocks for this parameter, and combine their statements into one.

报表试图为一个报表参数定义第二个 BEFORE GROUP OF 或者 AFTER GROUP OF 块。

只允许一个这样的控制块。找到该参数的所有块，并将它们的语句合并为一个。

-4389 There are too many levels of nesting of IF statements in this report.

You have exceeded the maximum of five levels of nesting of IF statements. Possibly an END IF statement has been omitted. If not,you will have to revise the logic of the report so that decisions are nested less deeply.

已经超过了 IF 语句可以嵌套的五个层级。 END IF 语句可能已被省略。

如果没有，请修改报表的逻辑，减少嵌套。

-4390 Only one BEFORE MENU clause is allowed for each MENU statement.

There can be only one BEFORE block of statements in a MENU. Make sure that the scope of your MENU statements are correctly marked with an END MENU. Then combine all the preparation code for this menu into a single BEFORE MENU block. This error is returned only by 4GL at Version 4.1.

MENU 中只能有一个 BEFORE 语句块。确保您的 MENU 语句的范围用 END MENU 正确标记。

然后将该菜单的所有预备代码合并到一个单独的 BEFORE MENU 块中。此错误仅在 V4.1 中由 4GL 返回。

-4391 When doing INPUT BY NAME or INPUT ARRAY, the BEFORE/AFTER field names can be specified only by the field name suffix. Screen array and screen record elements are not allowed.

Only names of single form fields can be used with a BEFORE or AFTER clause. The name of a field is defined in the ATTRIBUTES section of the form definition; it is often the same as the name of a database column. Here are example lines from an ATTRIBUTES section:只有单个表单字段的名称可以与 BEFORE 或 AFTER 子句一起使用。字段的名称在表单定义的 ATTRIBUTES 部分中定义；它通常与数据库列的名称相同。以下是 ATTRIBUTES 部分的示例行：atag = customer.customer_num,noentry;tag2 = formonly.total,format="#######.##";The names of these fields are customer_num and total, respectively.

这些字段的名称分别为 customer_num 和 total。

In the 4GL statement in question, you have written a name prefixed with another name and a dot. That syntax is used for specifying components of screen records or screen arrays, or database columns of the same name in different tables, but it is not appropriate here.

在 4GL 语句中，已经写了一个以另一个名称和一个点作为前缀的名称。该语法用于指定屏幕记录或屏幕数组的组件，或不同表中的同名数据库列，但这里不适用。

-4392 The 4GL compiler has run out of data space memory to contain the 4GL program symbols. If the program module is very large, dividing it into separate modules may alleviate the situation.

Reorganize your program source as a group of modules that can be compiled separately. Alternatively, revise the program so that fewer unique symbols are required, for instance by replacing many similar variables with an array. This error might also be related to the CONSTRUCT statement. If there is a CONSTRUCT over a large number of fields, moving that statement to a function and putting the function in a different source module might alleviate the problem with no other changes.

将程序源重新组织为可以单独编译的一组模块。或者修改程序，减少唯一符号的数量，例如用数组代替类似的变量。这个错误也可能与 CONSTRUCT 语句有关。如果在大量字段上存在 CONSTRUCT，则将该语句移至某个函数，将该函数放入不同的源模块中可能会缓解该问题，而无需进行其他更改。

-4393 The MENU statement has exceeded the maximum number of selections.

There is a maximum of 25 selections in a menu. Make sure that you have not omitted an END MENU statement, thus combining two menus. If the menu is as you intended it, you will have to revise the program so as not to exceed the limit, for example by creating a hierarchy of menus.

菜单中最多有 25 个选项。确保您没有省略 END MENU 语句，因此组合了两个菜单。

如果菜单您想要的，将不得不修改程序，以免超出限制，例如通过创建菜单层次结构。

-4394 Warning: Formal parameters in informal function headers cannot have initial values. The initial value of this parameter is ignored. If this value is intended as the default parameter, then use formal function headers to specify defaults.

Although parameters in formal (function-prototype-style) definitions can have initial values, those in the informal function definitions cannot. The initial value of this parameter is ignored. If this value is intended as the default parameter, then use the formal definition format that uses function prototypes to specify defaults. Only NewEra returns this error.

虽然正式（函数原型样式）定义中的参数可以具有初始值，但非正式函数定义中的参数不能。

该参数的初始值被忽略。如果此值用作默认参数，则使用使用函数原型的正式定义格式来指定默认值。只有 NewEra 返回此错误。

-4395 There are too many subscripts specified with a database column name.

In this statement the name of a database column is followed by square brackets with several numbers between them. The only valid use for square brackets with a database column is to select a substring from a character column. However, for that use you must write exactly two numbers, the subscripts of the first and last letters of the substring.

Here more than two numbers are used. Check and correct the punctuation.

在这个语句中，数据库列名后跟方括号，它们之间有几个数字。数据库列方括号的唯一有效用法是从字符列中选择子字符串。但是，要使用该方法，您必须准确地写出两个数字，即子字符串的第一个字母和最后一个字母的下标。这里使用了两个以上的数字。检查并更正标点符号。

-4396 The MENU declaration at line line-number is not terminated.

4GL could not identify an END MENU statement to match the MENU statement on the line number shown. Start at that line and work down until you find where the terminating statement should have been, and insert it.

4GL 无法识别 END MENU 语句以匹配显示的行号上的 MENU 语句。从这一行开始工作，直到找到终止语句应该在哪里为止，然后插入它。

-4397 The IF statement at line line-number is not terminated.

4GL could not identify an END IF statement to match the IF statement on the line number shown. Start at that line and work down until you find where the terminating statement should have been, and insert it.

4GL 无法识别 END IF 语句以匹配显示的行号上的 IF 语句。从这一行开始工作，直到找到终止语句应该在哪里为止，然后插入它。

-4398 The CASE statement at line line-number is not terminated.

4GL could not identify an END CASE statement to match the CASE statement on the line number shown. Start at that line and work down until you find where the terminating statement should have been, and insert it.

4GL 无法识别 END WHILE 语句以匹配显示的行号上的 CASE 语句。从这一行开始工作，直到找到终止语句应该在哪里为止，然后插入它。

-4399 The WHILE statement at line line-number is not terminated.

4GL could not identify an END WHILE statement to match the WHILE statement on the line number shown. Start at that line and work down until you find where the terminating statement should have been, and insert it.

4GL 无法识别 END WHILE 语句以匹配显示的行号上的 WHILE 语句。从这一行开始工作，直到找到终止语句应该在哪里为止，然后插入它。

-4400 The FOR statement at line line-number is not terminated.

4GL could not identify an END FOR statement to match the FOR statement on the line number shown. Start at that line and work down until you find where the terminating statement should have been, and insert it.

4GL 无法识别 END FOR 语句以匹配显示的行号上的 FOR 语句。从这一行开始工作，直到找到终止语句应该在哪里为止，然后插入它。

-4401 A concatenation operation has created a string too long to fit in the destination string variable.

This statement concatenates two or more character strings and stores the result in another variable of type CHAR or VARCHAR. However, the result of concatenation was longer than the receiving variable. If the excess length is due to trailing spaces, you can use the CLIPPED function to prevent them from being included in the combined result.

Otherwise you will have to define the length of the receiving variable as at least the sum of the lengths of the input variables.

该语句连接两个或多个字符串，并将结果存储在另一个 CHAR 或 VARCHAR 类型的变量中。

但是，级联的结果比接收的变量长。如果多余的长度是由于尾随空格造成的，则可以使用CLIPPED 函数来防止将它们包含在合并结果集中。否则，必须将接收变量的长度定义为至少输入变量长度的总和。

-4402 In this type of statement, subscripting may be applied only to array variables to select individual array elements.

The statement contains a name followed by square brackets, but the name is not that of an array variable. Check the punctuation of the statement and the spelling of all names. Names that are subscripted must be arrays. If you intended to use a character substring in this statement, you will have to revise the program.

该语句包含一个名称，后面有方括号，但名称不是数组变量的名称。检查语句的标点符号和所有名称的拼写。下标名必须是数组。如果您打算在此语句中使用字符子字符串，则必须修改程序。

-4403 The number of dimensions for the variable variable-name does not match the number of subscripts.

In this statement, the array whose name is shown is subscripted by a different number of dimensions than it was defined to have. Check the punctuation of the subscript. If it is as you intended, then review the DEFINE statement where variable-name is defined.

在此语句中，所显示名称的数组的下标的维数与定义的维数不同。请检查下标的标点符号。

如果它符合您的要求，请查看定义变量名称的 DEFINE 语句。

-4405 The function has exceeded the maximum number of allowed parameters.

This message is not returned by any current GBase 8s product. If the error recurs, note all circumstances and contact GBase Technical Support.

所有当前 GBase 8s 产品都不会返回此消息。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-4406 There is an unmatched quote in the above line.

The source line contains an odd number of quote symbols. Inspect it from left to right and make sure that all literal character strings begin and end with a quote. All literal strings must begin and end on the same logical line. However, you can write long literal strings in two ways. First, you can escape the end of line by making the final character in the line a backslash (however, there is a fixed maximum of 256 characters on the total length of a single quoted string). Second,in the DISPLAY and LET statements, you can concatenate shorter literal strings using the comma. Here are two examples.

源代码行包含奇数个引号符号。从左到右检查它，并确保所有文字字符串以引号开头和结尾。

所有文字字符串必须在同一条逻辑线上开始和结束。但是，可以通过两种方式编写长文字字符串。首先，可以通过将行中的最后一个字符设为反斜线（但是，单引号字符串的总长度最多为 256 个字符）来转义行尾。其次，在 DISPLAY 和 LET 语句中，可以使用逗号连接较短的文字字符串。这里有两个例子。

DISPLAY "abcdefghijkl\mnopqrstuvwxyz"DISPLAY "abcdefghijkl","mnopqrstuvwxyz"Both display the alphabet with no embedded white space.

这两种显示都没有嵌入空格。

-4407 There is an unprintable character in the above line.

This source line contains an unusual character. 4GL suggests that the source file might be corrupt. Edit the file and remove the bad character. If you cannot see or select it with your editor, you may have to delete and retype the line.

此源代码行包含一个不寻常的字符。 4GL 表示源文件可能已损坏。编辑该文件并删除坏字符。

如果无法使用编辑器查看或选择它，则可能需要删除并重新输入该行。

-4408 There is a quoted string that is too long in the above line.

The limit on the length of a literal character string is 256 characters.

However, in the DISPLAY and LET statements you can concatenate shorter literal strings using the comma. See message -4406 for an example.

文字字符串的最大长度为 256 个字符。但是，在 DISPLAY 和 LET 语句中，可以使用逗号连接较短的文字字符串。请参阅消息 -4406。

-4409 There is an invalid character in the above line.

This source line contains some character other than printable text and normal white space. Remove the invalid characters (which may be invisible under normal editing). If you cannot see or select the invalid characters with your editor program, you might have to delete the line and retype it.

该源代码行包含除可打印文本和普通空白以外的其他字符。删除无效字符（在正常编辑下可能不可见）。如果在编辑器程序中看不到或选择无效字符，则可能需要删除该行并重新输入。

-4410 There is a numeric constant in the previous line that is too large or too small.

A numeric constant in this line cannot be processed. Check the digits and punctuation of all literal numbers; for example, make sure that you have not typed a letter for a digit. No number can have more than 50 digits. Depending on the context, numbers might be restricted to one of three ranges.

无法处理此行中的数字常量。检查所有文字数字的数字和标点符号；例如，确保没有为数字键入字母。任何数字都不能超过 50 位数。根据上下文的不同，数字可能被限制在三个范围之一。

SMALLINT:absolute value not exceeding 32,767绝对值不能超过 32,767 INTEGER:absolute value not exceeding 2,147,483,647绝对值不能超过 2,147,483,647 DECIMAL:absolute value from 10 to the 130th power through 10 to the 124th power从10到130次方到10到124次方的绝对值BIGINT/INT8/SERIAL8 :absolute value from -9,223,372,036,854,775,807 to +9,223,372,036,854,775,807-9,223,372,036,854,775,807 到 +9,223,372,036,854,775,807-4411 There is an alphanumeric identifier that is too long in the above line.

No identifier can exceed 50 characters. Check the spelling and punctuation of all identifiers (perhaps two names have run together).

标识符不能超过 50 个字符。检查所有标识符的拼写和标点符号（也许两个名称一起运行）。

-4412 Values from the RUN command can be returned only to INTEGER or SMALLINT variables.

The RUN command only returns the integer return code from the program that was executed. No automatic conversion of data occurs in this case;its result must be assigned to an integer variable.

RUN 命令只返回执行程序的整数返回码。在这种情况下不会自动转换数据；其结果必须分配给一个整数变量。

-4413 The label label-name has already been defined within this function/report.

The name shown appears in two or more LABEL statements. Check the spelling of the name; if it is as you intended, then look back through this function, report, handler, or main program for other LABEL statements and find the one that uses this same name. Change one of them to use a different name. Only NewEra returns this error.

所显示的名称出现在两个或更多 LABEL 语句中。检查名称的拼写；如果它是想要的，那么通过这个函数、报告、处理程序或主程序查找其他 LABEL 语句，并找到使用相同名称的程序。将其中一个更改为使用不同的名称。只有 NewEra 返回此错误。

-4413 The label label-name has already been defined within this program or function .

The name shown appears in two or more LABEL statements. Check the spelling of the name; if it is as you intended, then look back through this function, or main program for other LABEL statements and find the one that uses this same name. Change one of them to use a different name. Only NewEra returns this error.

所显示的名称出现在两个或更多 LABEL 语句中。检查名称的拼写；如果它是想要的，那么通过这个函数或主程序查找其他 LABEL 语句，并找到使用相同名称的程序。将其中一个更改为使用不同的名称。只有 NewEra 返回此错误。

-4414 The label label-name has been used but has never been defined within this function/report.

A GOTO or WHENEVER statement refers to the label shown, but there is no corresponding LABEL statement in the current function, report, handler,or main program. Check the spelling of the label. If it is as you intended it, find and inspect the LABEL statement that should define it. You cannot transfer out of a program block with GOTO; labels must be defined in the same function body where they are used. Only NewEra returns this error.

GOTO 或 WHENEVER 语句引用所显示的标签，但在当前函数、报表、处理程序或主程序中没有对应的 LABEL 语句。检查标签的拼写。如果它是你想要的，找到并检查应该定义它的 LABEL 语句。不能用 GOTO 转出程序块；标签必须在使用它们的同一个函数体中定义。

只有 NewEra 返回此错误。

-4414 The label label-name has been used but has never been defined within the above main program or function.

A GOTO or WHENEVER statement refers to the label shown, but there is no corresponding LABEL statement in the current function, report, handler,or main program. Check the spelling of the label. If it is as you intended it, find and inspect the LABEL statement that should define it. You cannot transfer out of a function with GOTO; labels must be defined in the same function body where they are used. Only 4GL returns this error.

GOTO 或 WHENEVER 语句引用所显示的标签，但在当前函数、报表、处理程序或主程序中没有对应的 LABEL 语句。检查标签的拼写。如果它是你想要的，找到并检查应该定义它的 LABEL 语句。不能用 GOTO 转出程序块；标签必须在使用它们的同一个函数体中定义。只有 NewEra 返回此错误。

-4415 An ORDER BY or GROUP item specified within a report must be one of the report parameters.

The names used in a ORDER BY, AFTER GROUP OF, or BEFORE GROUP OF statement must also appear in the parameter list of the REPORT statement. It is not possible to order or group based on a global variable or other expression. Check the spelling of the names in the statement and compare them to the REPORT statement.

在 ORDER BY、AFTER GROUP OF 或 BEFORE GROUP OF 语句中使用的名称也必须出现在REPORT 语句的参数列表中。不可能基于全局变量或其他表达式来排序或分组。检查语句中拼写的名称，并将它们与 REPORT 语句进行比较。

-4416 There is an error in the validation string: "%s".

Change the appropriate DEFAULT or INCLUDE value in the syscolval table.

更改 syscolval 系统表中的适当 DEFAULT 或 INCLUDE 值。

-4417 This type of statement can be used only in a report.

Statements such as PRINT, SKIP, or NEED are meaningful only within the body of a report function, where there is an implicit report listing to receive output.

只有在报表函数的正文中，PRINT、SKIP 或 NEED 之类的语句才有意义，其中有要接收输出的隐式报表列表。

-4418 The variable used in the INPUT ARRAY or DISPLAY ARRAY statement must be an array.

The name following the words DISPLAY ARRAY or INPUT ARRAY must be that of an array of records. Check the spelling of the name. If it is as you intended, find and inspect the DEFINE statement to see why it is not an array. (If you want to display or input a simple variable or a single element of an array, use the DISPLAY or INPUT statement.)DISPLAY ARRAY 或 INPUT ARRAY 之后的名称必须是记录数组的名称。检查名称的拼写。

如果它符合您的要求，请查找并检查 DEFINE 语句以了解它为什么不是数组。（如果要显示或输入数组的简单变量或单个元素，请使用 DISPLAY 或 INPUT 语句。）-4419 The variable used in the CONSTRUCT statement must be a character variable.

The name following the word CONSTRUCT must be that of a variable defined as CHARACTER or VARCHAR. It ought to be a long variable, since the string it receives may be long. Check the spelling of the name. If it is as you intended, find and inspect the DEFINE statement to see why it is not a character type.

CONSTRUCT 之后的名称必须是定义为 CHARACTER 或 VARCHAR 变量的名称。它应该是一个很长的变量，因为它收到的字符串可能很长。检查名称的拼写。如果它符合您的要求，请查找并检查 DEFINE 语句以了解它为什么不是字符类型。

-4420 The number of lines printed in the IF part of an IF-THEN-ELSE statement of a header or trailer clause must equal the number of lines printed in the ELSE part.

4GL needs to know how many lines will be filled in header and trailer sections (otherwise it could not know how many detail rows to put on the page). Because it cannot tell which part of an IF statement will be executed, it requires that both produce the same number of lines of output.

4GL 需要知道在头部和尾部有多少行会被填充（否则无法知道要在页面上放置多少个明细行）。

因为它不能判断 IF 语句的哪一部分将被执行，所以它要求两者产生相同数量的输出行。

-4421 You may not use an INPUT statement within another INPUT statement or PROMPT statement, even if it is enclosed within a conditional or looping statement.

You can execute an INPUT statement from within another one, or from a PROMPT statement, but in order to do so you must place the INPUT statement in a function and call the function. You cannot embed the text of an INPUT statement within another.

您可以从另一条语句中执行 INPUT 语句，也可以从 PROMPT 语句中执行 INPUT 语句，但为了执行此操作，必须将 INPUT 语句放入函数中并调用该函数。不能将 INPUT 语句的文本嵌入到另一个语句中。

-4422 You may not use a CONSTRUCT statement within another INPUT statement.

This includes situations when CONSTRUCT is enclosed within a conditional or looping statement. You must call a function that executes the CONSTRUCT statement.

可以在 INPUT 语句中执行 CONSTRUCT 语句，但为了这样做，必须将 CONSTRUCT 语句放入函数中并调用该函数。不能在 INPUT 语句中嵌入 CONSTRUCT 语句的文本。

You can execute a CONSTRUCT statement from within an INPUT statement,but in order to do so you must place the CONSTRUCT statement in a function and call the function. You cannot embed the text of a CONSTRUCT statement in an INPUT statement.

可以在 INPUT 语句中执行 CONSTRUCT 语句，但为了执行此操作，必须将 CONSTRUCT 语句放入函数中并调用该函数。不能将 CONSTRUCT 语句的文本嵌入到 INPUT 语句中。

-4423 The CLIPPED and USING options for the DISPLAY statement may not be used when displaying to a form field.

The CLIPPED and USING keywords cannot be used in the DISPLAY TO and DISPLAY BY NAME statements. The display format of a form field is controlled by the attributes of that field, as specified in the form file. Trailing spaces are not displayed in a field. To get the effect of USING, edit the form file and add a USING attribute to the field or fields.

不能在 DISPLAY TO 和DISPLAY BY NAME 语句中使用 CLIPPED 和 USING 关键字。

表单字段的显示格式由该字段的属性控制，如表单文件中指定的那样。在字段中不会显示尾部空格。要获得 USING 的效果，请编辑表单文件并向该字段添加 USING 属性。

-4424 The variable variable-name has not been defined as a record.

The variable shown has been used with an asterisk, or with the THRU or THROUGH keywords. However, it has not been defined as a record. Check the spelling of the name. If it is as you intended, locate the definition of the variable and find out why it was not defined as a record. Only 4GL returns this error.

所显示的变量使用了星号或 THRU 或 THROUGH 关键字。但是，它并没有被定义为一个记录。

检查名称的拼写。如果它是您想要的，找到变量的定义并找出它没有被定义为记录的原因。

只有 4GL 会返回这个错误。

-4425 The variable variable-name has not been defined LIKE the table table-name.

The named variable has been used in the SET clause of an UPDATE statement. However, it was not defined to be LIKE the table being updated. As a result, 4GL cannot associate record components with table columns. You can change the definition of the variable, or you can rewrite the UPDATE statement to show the explicit relationship between column names and record components.

已在 UPDATE 语句的 SET 子句中使用了命名的变量。但是，没有将它定义为 LIKE 正在更新的表。

因此，4GL 不能将记录组件与表列相关联。您可以更改变量的定义，也可以重写 UPDATE 语句，以显示列名和记录组件之间的显式关系。

-4426 The PRINT statement can be used only within reports. If you wish to print without screen positioning, use the DISPLAY statement without any field or screen destination.

The keyword PRINT is used specifically to produce lines of output to a report. The keyword DISPLAY introduces output to the screen. Possibly this statement was accidentally copied from a report body; more likely it was a hasty attempt to display casual output on the screen. In the latter case, simply changing PRINT to DISPLAY is usually enough.

关键字 PRINT 专门用于生成报表的输出行。关键字 DISPLAY 将输出引入屏幕。这条语句可能是从报告主体意外复制的；更可能是，这是一次仓促的尝试。试图在屏幕上显示临时输出。

在后一种情况下，简单地将 PRINT 更改为 DISPLAY 就足够了。

-4427 The COLUMN feature for the DISPLAY statement may be used only when displaying without screen or field destination.

The COLUMN function returns a string of spaces long enough to reach a certain column in the display output. You may use it with unqualified DISPLAY and with DISPLAY AT, but it is not appropriate with DISPLAY TO or DISPLAY BY NAME.

COLUMN 函数返回一串足够长的空格以显示输出中的某一列。您可以将它与未限定的 DISPLAY 和 DISPLAY AT 一起使用，但不适用与 DISPLAY TO 或 DISPLAY BY NAME。

-4428 You may not use a PROMPT statement within an INPUT or PROMPT statement,even if it is enclosed within a conditional or looping statement.

You can execute a PROMPT statement from within another one or from within an INPUT statement, but in order to do so you must place the PROMPT statement in a function and call the function. You cannot embed the text of a PROMPT statement within an INPUT statement or another PROMPT.

您可以从另一条语句中执行 PROMPT 语句，也可以从 INPUT 语句中执行 PROMPT 语句，但为了执行此操作，必须将 PROMPT 语句放入函数中并调用该函数。不能将 PROMPT 语句的文本嵌入到 INPUT 语句中。

-4429 Report and function parameters cannot be arrays.

You cannot pass a whole array as a parameter of a function. You can pass an individual element of the array by using a subscript. Possibly the array that is causing this error is one component of a record variable that is being passed using asterisk notation. Only 4GL returns this error.

不能将整个数组作为函数的参数传递。可以使用下标传递数组的单个元素。可能导致此错误的数组是使用星号符号传递的记录变量的一个组件。只有 4GL 返回此错误。

-4429 Parameters cannot be arrays, records with array members, or constants.

You cannot pass a whole array or a constant as a parameter of a function. You can pass an individual element of an array by using a subscript. Possibly the array that is causing this error is one component of a record variable that is being passed using asterisk notation. Only NewEra returns this error.

不能将整个数组或常量作为函数的参数传递。可以使用下标来传递数组中的单个元素。可能导致此错误的数组是使用星号符号传递的记录变量的一个组件。只有 NewEra 返回此错误。

-4430 Values cannot be RETURNed from within reports.

A report cannot include a RETURN statement because that would return control to the routine that invoked the report. Only NewEra returns this error.

报表不能包含 RETURN 语句，因为这会将控制权返回给调用报告的例程。只有 NewEra 返回此错误。

-4430 Record parameters for a report cannot contain elements that are arrays.

You cannot pass a whole array as a parameter of a function. You can pass an individual element of the array by using a subscript. In this case, a record variable is specified as a parameter using asterisk notation, but one of the components of the record is an array.

不能将整个数组或常量作为函数的参数传递。可以使用下标来传递数组中的单个元素。

在这种情况下，记录变量被指定为使用星号表示法的参数，但记录的其中一个组件是数组。

-4431 The number of expanded report parameters has exceeded the maximum allowed.

This message is not returned by any current GBase 8s product. If the error recurs, note all circumstances and contact GBase Technical Support.

所有当前 GBase 8s 产品都不会返回此消息。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-4432 An element in a GROUP clause must be a member of the ORDER BY clause.

In order to perform grouping, the set of selected rows must be ordered on the same columns. This is the only way to force all the equal values to be found together, as a group. Rewrite the statement so that each selected value that you want to group also appears in an ORDER BY clause. Note that both these clauses allow you to refer to selected values by their position number, as in the following example:为了执行分组，必须在同一列上排序所选行的集合。这是迫使所有同等价值观作为一个群体共同发现的唯一途径。重写该语句，以便要分组的每个选定值也会出现在 ORDER BY 子句中。请注意，这两个子句都允许您按其位置编号引用所选值，如下例所示：SELECT customer_num, month(order_date), avg(ship_weight) FROM orders ORDER BY 1, 2 GROUP BY 1,2-4433 A variable used in the above statement must be of type CHAR or VARCHAR.

The filename in the REPORT TO statement must be given as a character value; and the program name in the REPORT TO PIPE statement must also be given as a character value. In either case, this can be a constant,a variable of either of the types mentioned, or an expression. However,it cannot be a number or other data type; no automatic type conversion occurs in these statements.

REPORT TO 语句中的文件名必须作为字符值给出；并且 REPORT TO PIPE 语句中的程序名称也必须作为字符值给出。在任何一种情况下，这可以是一个常量、所述类型的变量或表达式。

但是，它不能是数字或其他数据类型；在这些语句中不发生自动类型转换。

-4434 The limits of the GBase 8s 4GL Demo Version have been exceeded.

Call GBase for licensing information.

A program compiled using the demonstration version of GBase 8s 4GL can contain only one module with no more than 150 statements. This program either has too many statements, or it refers to a function in another module. Contact your GBase sales representative for information on full development licenses.

使用 GBase 8s 4GL 演示版编译的程序只能包含一个不超过 150 条语句的模块。这个程序要么有太多的语句，要么是引用了另一个模块中的一个函数。请联系您的 GBase 销售代表获取完整开发许可证的信息。

-4435 An acceptable hyphenated key format is CONTROL-X, where X is any letter except A, D, H, L, R, or X.

When a key is trapped by an ON KEY clause, it loses other special functions; for example, if you trap the Escape key, you must use the OPTIONS statement to set up a different Accept key. You are not allowed to use one of the control keys A, D, H, L, R, or X because these keys have editing functions, and there is no method of assigning alternate keys to those functions.

当键被 ON KEY 子句捕获时，它会失去其他特殊功能；例如，如果捕获 Escape 键，则必须使用 OPTIONS 语句来设置不同的 Accept 键。不能使用控制键 A、D、H、L、R 或 X 中的一个，因为这些键具有编辑功能，并且没有为这些功能分配替代键的方法。

-4436 There are too many variables to VALIDATE or INITIALIZE in one statement.

There is a limit of 250 names in the VALIDATE and INITIALIZE statements.

Simply divide this statement into multiple statements so as not to exceed the limit.

VALIDATE 和 INITIALIZE 语句中有 250 个名称的限制。

简单地将此声明分成多个声明，以免超出限制。

-4437 All table names in the SELECT list must be the same as the table name in the FROM clause.

One of the table names used in the list of columns to select does not appear in the FROM clause. Possibly you simply misspelled the name in one of the two places. Or you might have used a table alias in the select-list but forgot to define it in the FROM clause.

在要选择的列列表中使用的表名之一不在 FROM 子句中。可能您只是在两个地方的其中一个地方拼写错了名称。或者您可能在选择列表中使用了表别名，但忘记在 FROM 子句中定义它。

-4438 You cannot SELECT into a substring of a character variable.

Substring notation is not allowed in the INTO clause. You can specify a substring of a column in the list of columns to select and in the WHERE clause. But you have to select into an entire variable. Define a variable to select into, and move the data into the destination substring using a LET statement.

INTO 子句中不允许使用子字符串表示法。您可以在列的列表中指定要选择的列的子字符串，并在 WHERE 子句中指定。但是必须选择一个完整的变量。定义要选择的变量，并使用 LET语句将数据移动到目标子字符串中。

-4439 You cannot SELECT into record record because element name is a record or an array.

The INTO clause can name only simple variables. The use of asterisk or THRU notation is a shorthand for listing all the component fields of a record. The resulting list of fields must consist of simple variables.

In this case, the field name is not simple. Perhaps you have referred to the wrong record. If not, you will have to list the name component separately, specifying one or more of its component parts.

INTO 子句只能命名简单变量。使用星号或 THRU 符号是列出记录的所有组件字段的简写。

结果字段列表必须由简单变量组成。在这种情况下，字段名称并不简单。也许引用了错误的记录。如果不是，则必须单独列出名称组件，并指定一个或多个组件部件。

-4440 The field name1 precedes name2 in the record record-name and must also precede it when used with the THROUGH shorthand.

The THROUGH or THRU shorthand requires you to give the starting and ending fields as they appear in physical sequence in the record. Check the spelling of the names; if they are as you intended, then refer to the DEFINE statement where the record was defined to see why they are not in the sequence you expected. Only 4GL returns this error.

THROUGH 或 THRU 缩写要求您给出开始和结束字段，因为它们在记录中以物理顺序出现。检查名称的拼写；如果它们如您想要的，那么请参阅定义记录的 DEFINE语句，以了解它们为什么不符合您预期的顺序。只有 NewEra 返回此错误。

-4448 Cannot open the file filename for reading or writing.

Verify that the filename is correctly spelled and that your account has permission to read or write to it.

验证 filename 的拼写是否正确，以及您的账户是否具有对它读取或写入的权限。

-4451 The size of the pcode generated from this function/report has exceeded the 32K per function limit.

The function or report will have to be simplified. Extract some portion of its code to a separate function or report, and call that one. Only NewEra returns this error.

函数或报表必须简化。将其代码的某些部分提取到单独的函数或报表中，并调用该函数或报表。

只有 Newera 返回此错误。

-4452 The function (or report) name has already been defined.

No two functions can have the same name. No two reports can have the same name. Change one of the two occurrences of name to a different name. Only NewEra returns this error.

两个函数不能具有相同的名称。两个报表不能具有相同的名称。请更改其中之一的名称。

只有 NewEra 返回此错误。

-4452 The function (or report) name has already been defined. Function and report cannot both have the same name.

Each function (or report, which is similar to a function) must have a unique name within the program. Change the function or report name.

程序中的每个函数（或报表，类似函数）只能具有唯一的名称。更改函数或报表名。

-4453 Too many global identifiers and literal strings in your program.

A table 256K bytes long holds literal strings and identifiers used in the main function and at the global and module levels. The table also holds the identifiers of forms, windows, and cursors. To avoid this error, move some code that uses many literal strings into a separate module or into a function. Alternatively, find a way to initialize character variables without assigning literal strings, for example by reading the initial values from a database or file. Reducing the number of global and module variables will also help.

长度为 256K 字节的表保存主函数以及全局和模块级别中使用的字符串和标识符。该表还包含表单、窗口和光标的标识符。为避免此错误，请将使用多个文字字符串的代码移动到单独的模块或函数中或者，找到一种方法来初始化字符变量而无需分配文字字符串，例如读取数据库或文件中的初始值。减少全局和模块变量的数量也将有所帮助。

-4453 The size of the global string table has exceeded the limit of 32767.

The table is used to hold literal strings and identifiers used in the main function and at the global and module levels. The table also holds the identifiers of forms, windows, and cursors. To avoid this error,move some code that uses many literal strings into a separate module or into a function. Alternatively, find a way to initialize character variables without assigning literal strings, for example by reading the initial values from a database or file. Reducing the number of global and module variables will also help. Only 4GL returns this error.

该表用于保存主函数以及全局和模块层级中使用的字符串和标识符。该表还包含表单、窗口和光标的标识符。为避免此错误，请将使用多个文字字符串的代码移到单独的模块或函数中。或者，找到一种方法来初始化字符变量而无需分配文字字符串，例如通过读取数据库或文件中的初始值。减少全局和模块变量的数量也将有所帮助。只有 4GL 返回这个错误。

-4454 The size of the local string table has exceeded the limit of 32767.

The table is used to hold literal strings and identifiers used in the current function. To avoid this error, split the function into two or more sub-functions. Alternatively, find a way to initialize character variables without assigning literal strings, for example by reading the initial values from a database or file. Only 4GL returns this error.

该表用于保存当前函数中使用的字符串和标识符。为避免此错误，请将该函数拆分为两个或多个子函数。或者，找到一种方法来初始化字符变量而无需分配文字字符串，例如读取数据库或文件中的初始值。只有 4GL 返回这个错误。

-4458 Each dimension for an array must be between 1 and 32767, inclusive.

Array dimensions cannot be less than one or greater than 32,767. If you need a larger array, you must either split the array into multiple arrays, or use multiple dimensions.

数组的维度不能小于 1 或大于 32,767。如果您需要更大的数组，则必须将数组拆分为多个数组或使用多个维度。

-4475 "name" cannot be used as both a function (or report) name and an identifier name.

The name shown has been defined at least two ways. Names at the global or module level must be unique. Locate all the definitions and declarations of this name and change all but one of them. Only NewEra returns this error.

所显示的名字至少有两种定义。全局或模块层级的名称必须唯一。查找此名称的所有定义和声明，改变除了其中一个以外的所有定义和声明。只有 NewEra 返回此错误。

-4475 "name" may not be used as both a function (or report) name and a variable name.

The name shown has been defined at least two ways. Names at the global or module level (function names, report names, and names of global or module variables) must be unique. Locate all the definitions of this name and change all but one of them. Error -4475 is issued with this meaning from 4GL at versions after 4.1.

所显示的名称至少有两种定义。全局或模块级别的名称(函数名、报表名以及全局变量或模块变量的名称)必须是唯一的。查找此名称的所有定义，并更改其中的所有定义。错误 -4475 是从 V4.1 之后的版本中的 4GL 发出的。

-4475 "name" may not be used as both a function (or report) name and an identifier.

所显示的名称至少有两种定义。全局或模块级别的名称必须是唯一的。查找此名称的所有定义，并更改其中的所有定义。错误 -4475 是从 V4.1 之后的版本中的 4GL 发出的。

-4476 Record members may not be used with database column substring. Possible misspelling or usage of undefined host variables.

This statement has a reference of the form name1.name2[...]. This is the form in which you would refer to a substring of a column:table.column[...]. However, the names are not a table and column in the database, so 4GL presumes they refer to a field of a record.

Inspect the statement and determine what was intended: a reference to a column or to a record. If it is a column reference, verify the names of the table and column in the database. If it is a record reference,verify that the record and component are properly defined. If the record has the same name as a table, prefix the name of the table with@ to make it clear you mean the table, not the record.

该语句具有 name1.name2 [...]形式的引用。这是您要引用列的子字符串的形式：table.column [...]。

但是，name 不是数据库中的表和列，因此 4GL 假设它们指向记录的字段。检查语句并确定意图：要引用列或记录。如果是列引用，请验证数据库中表和列的名称。如果是记录引用，请确认记录和组件定义正确。如果记录的名称与表名称相同，则使用 @ 前缀表名，以清楚表示表，而不是记录。

-4479 Warning: non-ANSI comment indicator. Use "--" for ANSI compatibility.

If you want your SQL statements to comply with ANSI standards, you must use the two-dash comment delimiter (- -). The comment delimiters of the number sign (#) and the braces ({ }) are not portable to ANSI-compliant systems. This message is seen because you specified that you wanted warnings issued for constructs that are not ANSI compliant, by means of the -ansi command-line parameter, the DBANSIWARN environment variable,or the DBANSIWARN setting in the GBase 8s.ini file. Only NewEra returns this error.

如果要 SQL 语句符合 ANSI 标准，则必须使用双破折号注释分隔符（- -）。数字符号（＃）和大括号（{}）的注释分隔符不适用于符合 ANSI 标准的系统。由于通过 -ansi 命令行参数，DBANSIWARN 环境变量或 GBase 8s.ini 文件中的 DBANSIWARN 设置向不兼容 ANSI 的构造发出警告，因此可以看到此消息。只有 NewEra 返回此错误。

-4479 Warning: non-ANSI comment indicator. Use "--" for ANSI compatibility.

If you want your SQL statements to comply with ANSI standards, you must use the two-dash comment delimiter (- -). The comment delimiters of the number sign (#) and the braces ({ }) are not portable to ANSI-compliant systems. This message is seen because you specified that you wanted warnings issued for constructs that are not ANSI compliant, by means of the -ansi command-line parameter, or the DBANSIWARN environment variable. Only 4GL returns this error.

如果要 SQL 语句符合 ANSI 标准，则必须使用双破折号注释分隔符（- -）。数字符号（＃）和大括号（{}）的注释分隔符不适用于符合 ANSI 标准的系统。由于通过 -ansi 命令行参数或 DBANSIWARN 环境变量向不兼容 ANSI 的构造发出警告，因此可以看到此消息。只有 4GL 返回此错误。

-4486 TEXT or BYTE variables and wordwrap fields cannot be printed in report headers or trailers.

4GL has to be able to predict how many lines will be used in a report header or trailer. Because the size of a TEXT variable is unpredictable, you cannot display one in these contexts.

4GL必须能够预测在表头或页尾中将使用多少行。由于 TEXT 变量的大小不可预知，因此无法在这些上下文中显示。

-4487 It is not possible to mix parameter and local record definitions where the record contains variables of type TEXT or BYTE. Make a second definition for the local record variable.

In this report body, use separate DEFINE statements for parameters of the report and for local variables of any type.

在此报表内容中，对报表参数和任何类型的局部变量使用单独的定义语句。

-4488 The program cannot CONTINUE or EXIT statement-type at this point because it is not immediately within statement-type statement.

This CONTINUE or EXIT statement is not appropriate in its context.

Possibly the statement is misplaced, or possibly the statement type was specified incorrectly.

此 CONTINUE 或 EXIT 语句在其上下文中不合适。可能语句被错误地放置，或者语句类型被错误地指定。

-4489 The statement above does not allow the use of local variables or report parameters in its expressions.

This statement cannot refer to an argument of the function or to a variable defined in the function. It can use only variables defined at the module level (before the MAIN section) or in the GLOBALS section.

In the case of OUTPUT REPORT TO, the statement takes effect during the execution of a START REPORT statement. At this time, no arguments are passed into the report description, and no report description statements are executed that could initialize a local variable. Change the statement to refer to a variable that can be initialized before the report is started.

该语句不能引用函数的参数或函数中定义的变量。它只能使用在模块级（在 MAIN 部分之前）或 GLOBALS 部分定义的变量。在 OUTPUT REPORT TO 的情况下，该语句在执行 START REPORT 语句期间生效。此时，此时，不向报表描述传递任何参数，也不执行可以初始化局部变量的报表描述语句。将语句更改为引用可在报表启动前初始化的变量。

-4490 You cannot have multiple BEFORE clauses for the same field.

You cannot specify more than one BEFORE clause for the same field.

对于同一字段只能指定一个 BEFORE 子句。

-4491 The parameter name has been changed.

More than one copy of the function prototype has occurred in the current scope, and the one indicated by this message has specified a different name for a formal parameter than that specified by any prototypes already encountered.

在当前范围中发生了多个函数原型副本，此消息所指示的副本已为形参指定了与已遇到的任何原型指定的名称不同的名称。

-4492 Warning: The parameter is assigned a new default value.

More than one copy of the function prototype has occurred in the current scope, and the one indicated by this message has specified a different default value for a formal parameter than that specified by any prototypes already encountered.

在当前范围内发生了多个函数原型副本，此消息所指示的副本已为形参指定了与已遇到的任何原型指定的缺省值不同的值。

-4493 Named parameters are allowed only for formal functions/reports.

The indicated function reference uses named parameters, but the declaration of the function or report used the informal style of parameter declaration, in which only the names are specified in the parameter list and the types are specified in subsequent, subsidiary declarations.

指定的函数引用使用了命名参数，但函数或报表的声明使用了非正式的参数声明，在参数列表中只指定名称，而类型在后续的辅助声明中指定。

-4494 Missing named parameter "name" does not have default value.

The indicated function invocation does not list a value for a parameter, and the declaration for the function does not provide a default value for it. Either add a default value in the declaration, or add a name/value pair here in the invocation.

指定的函数调用没有列出参数的值，函数的声明也没有为其提供缺省值。要么在声明中添加缺省值，要么在调用中添加 name/value 对。

-4495 Duplicate or invalid parameter name.

The name of a parameter specified in the invocation of the function does not match any of the names in the declaration of that function, or it is not a valid NewEra identifier. Check its spelling.

函数调用中指定的参数的名称与该函数声明中的任何名称不匹配，或者它不是有效的 Newera 标识符。检查它的拼写。

-4496 CHAR (*) type is not allowed within records or classes.

The CHAR(*) type is allowed only in function prototypes, as a parameter, not as an element of a record or class.

CHAR(*) 类型仅在函数原型中被允许作为参数，而不是作为记录或类的元素。

-4497 Event "name" is already declared in the class.

Two events in the same class cannot have the same name.

同一类中的两个事件不能具有相同的名称。

-4498 Event/Handler name must be different from intrinsic member function name.

You cannot declare an event or a handler with the same name as an intrinsic member function (!copy(), !derive(), or the name of the class). Change the name of the event or handler.

不能使用与内部成员函数同名的事件或处理程序声明事件或处理程序(!copy()、!derive()或类名)。更改事件或处理程序的名称。

-4499 Member "name" is already declared in the class or in its base class.

Either a member called "name" already exists in the current class, and you have attempted to declare another member with that name, or you are attempting to override an event or a variable. Only member functions can be overridden.

名为“name”的成员已经存在于当前类中，并且试图使用该名称声明另一个成员，或者试图重写事件或变量。只能重写成员函数。

-4500 A numeric conversion error has occurred due to incompatibility between a calling program and its function parameters or between a variable and its assigned expression.

See error -1317, which has replaced this error.

请参阅错误 -1317，它已经替换了此错误。

-4501 A parameter count mismatch has occurred between the calling function and the called function.

See error -1318, which has replaced this error.

请参阅错误 -1318，它已经替换了此错误。

-4502 The 4GL program has run out of runtime data space memory.

See error -1319, which has replaced this error.

请参阅错误 -1319，它已经替换了此错误。

-4503 A function has not returned the correct number of values expected by the calling function.

See error -1320, which has replaced this error.

请参阅错误 -1320，它已经替换了此错误。

-4504 A validation error has occurred as a result of the VALIDATE command.

The type of a VALIDATE variable cannot be converted to the type of the validation values. Only NewEra returns this error.

VALIDATE 变量的类型不能转换为验证值的类型。只有 NewEra 返回此错误。

-4504 A validation error has occurred as a result of the VALIDATE command.

See error -1321, which has replaced this error for products other than NewEra.

请参阅错误 -1321，它已经取代了此 Newera 以外的产品的错误。

-4505 A report output file cannot be opened.

See error -1322, which has replaced this error.

请参阅错误 -1322，它已经替换了此错误。

-4506 A report output pipe cannot be opened.

See error -1323, which has replaced this error.

请参阅错误 -1323，它已经替换了此错误。

-4507 A report output file cannot be written to.

See error -1324, which has replaced this error.

请参阅错误 -1324，它已经替换了此错误。

-4508 PRINT FILE error - cannot open file filename for reading.

See error -1325, which has replaced this error.

请参阅错误 -1325，它已经替换了此错误。

-4509 An array variable has been referenced outside of its specified dimensions.

An array bound has been exceeded, and array-bounds checking has been turned on. Array-bounds checking can be turned on through the compiler switch "-a" or the PRAGMA ARRAY BOUNDS statement. Only NewEra returns this error.

已超出数组边界，并打开了数组边界检查。数组边界检查可以通过编译器开关 “-a”或 PRAGMA ARRAY BOUNDS语句打开。只有 Newera 返回此错误。

-4509 An array variable has been referenced outside of its specified dimensions.

See error -1326, which has replaced this error for products other than NewEra.

请参阅错误 -1326，它已经取代了此 Newera 以外的产品的错误。

-4511 A temporary table needed for a report could not be created in the selected database. The user must have permission to create tables in the selected database.

See error -1328, which has replaced this error.

请参阅错误 -1328，它已经替换了此错误。

-4512 A database index could not be created for a temporary database table needed for a report.

See error -1329, which has replaced this error.

请参阅错误 -1329，它已经替换了此错误。

-4513 Incorrectly formed hexadecimal value.

The hexadecimal digits are a to f and 0 to 9. Possibly you included an illegal character where NewEra expected a hexadecimal value or its sign.

十六进制数字是 a 到 f 和 0 到 9。可能包含一个非法字符，NewEra 期望得到一个十六进制值或符号。

-4513 A number used as a DISPLAY AT location or SCROLL count must be positive.

For a DISPLAY AT statement, see error -1135, which has replaced this error.

对于 DISPLAY AT 语句，请参阅错误 -1135，它已取代此错误。

-4514 A row could not be inserted into a temporary report table.

See error -1330, which has replaced this error.

请参阅错误 -1330，它已经替换了此错误。

-4515 A row could not be fetched from a temporary report table.

See error -1331, which has replaced this error.

请参阅错误 -1331，它已经替换了此错误。

-4516 A character variable has referenced subscripts that are out of range.

See error -1332, which has replaced this error.

请参阅错误 -1332，它已经替换了此错误。

-4517 Strings of length > 512 cannot be returned from function calls.

See error -1333, which has replaced this error.

请参阅错误 -1333，它已经替换了此错误。

-4518 The 4GL program cannot allocate any more space for temporary string storage.

Either the program is attempting to return more than 32,768 bytes of CHAR, VARCHAR, or CHAR(*) values from a function, or the number of bytes of temporary CHAR(*) variables that the program creates implicitly has exceeded 32,768. Only NewEra returns this error.

程序试图从函数中返回超过 32,768 字节的 CHAR、VARCHAR 或 CHAR(*) 值，或者程序创建的临时 CHAR(*) 变量的字节数超过 32,768。只有 NewEra 返回此错误。

-4518 The 4GL program cannot allocate any more space for temporary string storage.

For products other than NewEra, see error -1334, which has replaced this error.

对于 NewEra 以外的产品，请参阅错误 -1334，该错误取代了此错误。

-4527 Undefined opcode in function name.

The p-code file for the program (whose file suffix is .4go) has become corrupted. Recompile at least the module that contains the named function (preferably the whole program) and run it again. If the same error occurs, make sure that you are running both fglpc and fglgo at the identical version level. If you are, refer to the Administrator's Guide or Reference for your database server, for additional diagnostics.

Contact GBase Technical Support with the diagnostic information.

该程序的 p-code 文件（其文件后缀为.4go）已损坏。重新编译至少包含指定函数的模块（最好是整个程序）并再次运行。如果发生相同的错误，请确保您在相同的版本级别上同时运行 fglpc 和 fglgo。如果是，请参阅数据库服务器的“管理员指南”或“参考”以获取其他诊断信息。联系 GBase 技术支持以获取诊断信息。

-4535 Bad store include table syntax "file1" "file2".

An internal error has occurred.

发生了内部错误。

The code that generates the INCLUDE statement, the Application Builder front-end code that generated the INCLUDE statement is out of synchronization with the Application Builder back-end code that handles the insertion and removal of data from the database.

生成 INCLUDE 语句的代码，生成 INCLUDE 语句的 Application Builder 前端代码与处理从数据库插入和删除数据的 Application Builder 后端代码不同步。

An extraordinarily large save in which the filenames exceed 64 kilobytes could also cause this error.

文件名超过 64 KB 的超大型保存也可能导致此错误。

-4536 Database open failed.

The Application Builder could not open the database. A network failure,.NET failure, or an incorrect value in the DBPATH environment variable could cause this error. Check the DBPATH setting, and run SETNET. Also verify that the UNIX host is functioning correctly.

Application Builder 无法打开数据库。网络故障、.NET故障或 DBPATH环境变量中的错误值都可能会导致此错误。检查 DBPATH 设置，并运行 SETNET。还要验证UNIX 主机是否正常工作。

-4538 No database name has been given.

The Application Builder attempted to execute an OPEN DATABASE command without specifying the name of the database. Check the "database=..."line in your GBase 8s.ini file. If you want to use the default database, set the line to "database=syspg4gl".

Application Builder 尝试执行 OPEN DATABASE 命令而不指定数据库的名称。

检查GBase 8s.ini 文件中的“database = ...”行。如果要使用默认数据库，请将该行设置为“database = syspg4gl”。

-4542 Attempt to upgrade the design database failed.

The Application Builder attempted to upgrade an older style database from GBase 8s 4GL to a new style that uses NewEra failed. This process involves creating a series of new tables and modifying and moving the data.

The error might occur because of lack of permissions. The owner of the database should perform the upgrade.

Application Builder 尝试将旧的样式数据库从 GBase 8s 4GL 升级到使用 NewEra 失败的新样式。这个过程涉及创建一系列新表并修改和移动数据。该错误可能是由于缺少权限而发生的。

数据库的所有者执行升级。

The error could be due to a full disk. The upgrade does not erase old information until it has been written and verified, and then only if requested. The amount of free space that an upgrade requires is approximately equal to the amount that the older database uses.

该错误可能是由完整的磁盘导致。升级不会删除旧信息，直到它被写入并验证，然后才会被请求。

升级所需的可用空间量大约等于旧数据库使用的数量。

-4543 Invalid delimiter. Do not use '\', hex digits (0-9, A-F, a-f), or space.

Use a delimiter other than any of the 22 forbidden symbols that are listed here.

使用除此处列出的 22 个禁止符号之外的任何分隔符。

-4555 Variable size cannot exceed 65535 bytes.

You have attempted to create a variable whose total size exceeds 65535.

Arrays can consume space more quickly than you might notice. A simple array A[100,100] of CHAR(6) would consume 10,000 x 7 - 70,000 bytes.

您试图创建总大小超过 65535 的变量。数组占用空间的速度可能比您可能注意到的要快。

CHAR(6) 的简单数组 A[100,100] 将占用 10,000 x 7 - 70,000 字节。

-4556 Object size cannot exceed 65535 bytes.

You have attempted to create an object whose total size exceeds 65535.

Arrays can consume space more quickly than you might notice. A simple array A[100,100] of CHAR(6) would consume 10,000 x 7 - 70,000 bytes.

您已经尝试创建一个总大小超过 65535 的对象。数组占用空间的速度可能比您可能注意到的要快。

一个简单的数组 A[100，100] 的char(6) 将消耗 10，000 x 7-70，000字节。

-4600 No form by specified name found.

The form specified cannot be found as a file named formname.frm.

The system looks in the current directory, and in each directory named in the DBPATH environment variable. Possibly the form name was misspelled, or the form file might have been renamed, or possibly the DBPATH variable is not set correctly.

指定的表单不能作为名为 formname.frm 的文件找到。系统会查看当前目录以及 DBPATH环境变量中指定的每个目录。可能表单名称拼写错误，或者表单文件可能已被重命名，或者可能 DBPATH 变量设置不正确。

-4601 No 4GL module by specified name found.

The source module specified cannot be found as a file module.4gl.

The system looks in the current directory and in directories named in the DBPATH environment variable. Possibly the module name was misspelled, or the file might have been renamed, or possibly the DBPATH variable is not set correctly.

指定的源模块不能作为文件 module.4gl 找到。系统查看当前目录和 DBPATH 环境变量中指定的目录。可能模块名拼写错误，或者文件可能已被重命名，或者 DBPATH 变量设置不正确。

-4602 No 4GL program by specified name found.

The multi-module program specified cannot be found in the program database. Possibly the module name was misspelled.

Possibly, if the DBPATH environment variable has been changed since the program was defined, you are now using a different program database than before.

在程序数据库中找不到指定的多模块程序。可能模块名称拼写错误。可能的话，如果自定义程序后 DBPATH 环境变量已被更改，则您现在正在使用与以前不同的程序数据库。

-4603 No executable 4GL program by specified name found.

The executable program specified cannot be found as a file module.4go. The system looks in the current directory and in directories named in the DBPATH environment variable. Possibly the name was misspelled, or the file might have been renamed, or possibly the DBPATH variable is not set correctly.

指定的可执行程序不能作为文件模块找到。系统查看当前目录和 DBPATH 环境变量中指定的目录。可能名称拼写错误，或者文件可能已被重命名，或者 DBPATH 变量没有正确设置。

-4604 Errors found in 4GL module.

Select the Correct menu choice. You will be shown the module source with error messages included.

选择正确的菜单选项。将向您显示模块源，并包含错误消息。

-4607 The following errors were discovered during compilation.

Errors were found that are not related to specific lines of source code,for example, undefined functions. There may be .err files as well that you can display to see more error messages. Modify the program definition and the source modules as required and recompile.

发现的错误与特定的源代码行无关，例如未定义的函数。可能还有.err文件，您可以显示它以查看更多错误消息。根据需要修改程序定义和源模块并重新编译。

-4608 The compilation of the program was not successful.

There should be other error messages visible, or in a file with a suffix of .err, to explain the lack of success.

应该有其他可见的错误消息，或者在后缀为 .err 的文件中，以解释失败的原因。

-4609 Insufficient memory is available to complete program compilation.

The only practical recourse is to divide the source files into smaller units.

唯一可行的办法是将源文件分成更小的单元。

-4610 Warnings found in 4GL module.

You have compiled with the -ansi command line option, which asks that you be warned about any use of SQL that does not comply with ANSI standard SQL. The compiler did find one or more uses of GBase 8s extensions to standard SQL. Edit the module.err file to see the warning messages.

您已使用 -ansi 命令行选项进行编译，该选项要求警告任何不符合 ANSI 标准 SQL 的 SQL使用。编译器确实发现了对标准 SQL 的 GBase 8s 扩展的一个或多个用法。编辑 module.err文件,查看警告消息。

-4611 There is no 4GL source available for this program.

You have requested that a program be compiled, but the system cannot locate one of the module source files. It is looking for files with the suffix .4gl and having the names shown in the program source list. It looks in the current directory and in directories named in the DBPATH environment variable. Check that the program is correctly defined, and locate the source modules. Make sure that the DBPATH environment variable is correctly set.

您已请求编译程序，但系统找不到其中一个模块源文件。它正在查找后缀为 .4gl 的文件，并在程序源列表中显示名称。它在当前目录和 DBPATH 环境变量中指定的目录中查找。

检查程序是否正确定义，并找到源模块。确保 DBPATH 环境变量设置正确。

-4612 Data validation table does not currently exist for this database.

The program uses a statement such as VALIDATE or INITIALIZE that requires input from the syscolval table; however that table does not exist in the current database. Possibly it has not been created (using the Column Attributes Dictionary utility in Windows or the upscol utility in DOS and UNIX); possibly it was inadvertently dropped from the database; or possibly the database now being used is not the one you expected, owing to a change in the value of the DBPATH environment variable.

该程序使用如 VALIDATE 或 INITIALIZE 的语句，它需要从 syscolval 表中的输入；但是该表在当前数据库中不存在。可能它尚未创建（使用 Windows 中的列属性字典实用程序或 DOS 和 UNIX 中的 upscol 实用程序）；可能它是无意中从数据库中删除的；或者可能由于 DBPATH 环境变量的值发生变化，现在正在使用的数据库不是您所期望的数据库。

-4613 Screen display attribute table does not currently exist for this database.

The program uses a statement that requires input from the syscolatt table; however that table does not exist in the current database.

Possibly it has not been created (using the Column Attributes Dictionary utility in Windows or the upscol utility in DOS and UNIX); possibly it was inadvertently dropped from the database; or possibly the database now being used is not the one you expected,owing to a change in the value of the DBPATH environment variable.

该程序使用需要从 syscolatt 表输入的语句；但是该表在当前数据库中不存在。

可能它尚未创建（使用 Windows 中的列属性字典实用程序或 DOS 和 UNIX 中的upscol 实用程序）；可能它是无意中从数据库中删除的；或者可能由于 DBPATH环境变量的值发生变化，现在正在使用的数据库不是您所期望的数据库。

-4614 A program already exists by this name.

You have specified as a new program one that already appears in the program database. Programs must have unique names. Choose a different name.

您已经指定了一个已经出现在程序数据库中的新程序。程序必须具有唯一的名称。选择一个不同的名字。

-4615 Invalid program name.

You have specified an unacceptable name for a new program. The name may be too long (at most 10 characters in some operating systems, at most 8 in others). If not, make sure that it starts with a letter and contains only letters, digits, and underscore characters.

您为新程序指定了不可接受的名称。名称可能太长（某些操作系统最多 10 个字符，其他最多 8 个）。

如果不是，请确保它以字母开头，并且只包含字母、数字和下划线字符。

-4616 The 4GL program database does not exist. Create via PROGRAM section.

In UNIX, the program database, named syspgm4gl, is not accessible.

If you select the Program menu option you will be asked if you want to create it. If you think that this database ought to exist already (for instance, if you have previously defined multi-module programs),then exit the Programmer's Environment and check the value of the DBPATH environment variable. It determines which databases are visible (if you are using the GBase 8s SE). If it is correct, or if you are using an OnLine database server, then the program database either never existed or has been dropped.

在 UNIX 中，名为 syspgm4gl 的程序数据库不可访问。如果您选择程序菜单选项，系统会询问您是否要创建它。如果您认为该数据库应该已经存在（例如，如果以前定义了多模块程序），则退出编程环境并检查 DBPATH 环境变量的值。它确定哪些数据库可见（如果正在使用 GBase 8s SE）。如果它是正确的，或者如果正在使用 OnLine 数据库服务器，那么程序数据库不存在或已被删除。

-4617 You may not edit a program located on a different device.

You cannot specify a pathname to a source file in a directory that is not on the device that holds your current directory. Use a system utility to copy the source file to your current directory (or to a directory on the current device).

不能为不在保存当前目录的设备上的目录中的源文件指定路径名。使用系统实用程序将源文件复制到当前目录(或当前设备上的目录)。

-4618 An error has occurred in accessing the requested file.

Something prevented the program from reading the file you specified. Look for other messages including operating system messages that might give more details.

有些东西阻止程序读取您指定的文件。查找其他消息，包括可能提供更多详细信息的操作系统消息。

-4620 GBase 8s ESQL/C is not installed on the system.

In order to use ESQL/C modules (source files with a .ec suffix) in a program definition, you must have GBase 8s ESQL/C installed in your system. If you believe it has been installed, review the installation procedure, because the product is not visible in the directory named in the GBS_HOME environment variable.

为了在程序定义中使用 ESQL/C 模块（具有 .ec 后缀的源文件），必须在系统中安装GBase 8s ESQL/C。如果确信已安装，请查看安装过程，因为在 GBS_HOME 环境变量中指定的目录中看不到产品。

-4621 Error occurred while writing to output file filename.

While writing to the named file the operating system reported an error. The problem may be a full disk or a hardware failure. Look for operating system error messages that give more information.

在写入指定文件时，操作系统报告了错误。问题可能是磁盘已满或硬件故障。

查找提供更多信息的操作系统错误消息。

-4622 No runable 4GL program by specified name found.

The program you asked to run is not accessible as a file named program.4go. 4GL looks in the current directory and in directories named in the DBPATH environment variable. Check the spelling of the program name. If it is as you intended, check the existence of the file and the setting of DBPATH. Possibly you need to compile the program before running it.

您要求运行的程序不能作为一个名为 Program.4go 的文件访问。4GL 查找当前目录和 DBPATH环境变量中指定的目录。检查程序名的拼写。如果是您想要的，请检查文件的存在和 DBPATH的设置。可能您需要在运行程序之前编译它。

-4623 memory allocation error.

It has proven impossible to allocate memory for a small work area of fixed size needed by a print function such as USING or ASCII. The amount of memory needed is small; almost any reduction in program size should avoid the error.

事实证明，要为打印函数所需的固定大小的小工作区分配内存是不可能的，比如 USING 或 ASCII。

所需的内存量很小；几乎任何程序大小的缩小都应该避免错误。

-4624 Owner name identifier has exceeded 8 characters in length.

The name shown appears in this statement where an owner name is expected, for example preceding the name of a table: identifier.table.

However, the name exceeds eight characters, and the database server only allows eight-character owner names. Review the punctuation of the statement and the spelling of the identifier.

显示的名称显示在此语句中，其中需要所有者名称，例如表名称之前的名称：identifier.table。

但是，名称超过 8 个字符，而且数据库服务器只允许 8 个字符的所有者名称。检查语句的标点符号和标识符的拼写。

-4625 FIXTIME FAILED.

This is an internal error. If the error recurs, note all circumstances and contact the GBase Technical Support.

这是一个内部错误。如果错误再次出现，请记下所有情况并联系 GBase 技术支持。

-4626 Could not open file filename.

Either the file does not exist, or your account does not have permission to access it, or some hardware failure occurred while it was being opened. Verify that the file exists; if it does, look for operating system error messages for more information.

文件不存在，或者您的账户没有权限访问它，或者在打开时发生某些硬件故障。

验证文件是否存在；如果存在，请查找操作系统错误消息以获取更多信息。

-4627 The program cannot exit an INPUT statement at this point because it is not within an INPUT statement.

The current statement is EXIT INPUT but it is not in the context of an INPUT statement. Inspect the source module backward from this point to determine what happened to the INPUT statement. Perhaps the current statement was misplaced, or perhaps an END INPUT statement was inserted at an earlier point.

当前语句是 EXIT INPUT，但它不在 INPUT 语句的上下文中。从此处开始检查源模块以确定INPUT 语句发生了什么。也许当前语句被放错了位置，也可能是在早期插入了 END INPUT 语句。

-4628 The program cannot exit a DISPLAY ARRAY statement at this point because it is not within a DISPLAY ARRAY statement.

The current statement is EXIT DISPLAY but it is not in the context of an DISPLAY statement. Inspect the source module backward from this point to determine what happened to the DISPLAY statement.

Perhaps the current statement was misplaced, or perhaps an END DISPLAY statement was inserted at an earlier point.

当前语句是 EXIT DISPLAY，但它不在 DISPLAY 语句的上下文中。从此处开始检查源模块以确定 DISPLAY 语句发生了什么。也许当前语句被放错了位置，也可能是在早期插入了END DISPLAY 语句。

-4629 Load from file filename failed.

The LOAD statement failed, either because of an error reading the named file, or because of an error converting data from one form to another. Look for other messages from 4GL or the operating system for more information.

LOAD 语句失败，原因要么是读取指定文件时出错，要么是由于将数据从一种形式转换到另一种形式的错误。有关更多信息，请查找来自 4GL 或操作系统的其他消息。

-4630 Unload to file filename failed.

The UNLOAD statement failed, either because of a problem with the SELECT statement or because of an error producing the output file.

Look for other messages from 4GL or the operating system for more information.

UNLOAD 语句失败，这可能是因为 SELECT 语句有问题，或者是由于生成输出文件时出错。

有关更多信息，请查找来自 4GL 或操作系统的其他消息。

-4631 Startfield of DATETIME or INTERVAL qualifiers must come earlier in the time-list than its endfield.

The qualifier for a DATETIME or INTERVAL consists of start TO end,where the start and end are chosen from this list:DATETIME 或 INTERVAL 的限定符包括开始 TO 结束，其中从此列表中选择开始和结束：YEAR MONTH DAY HOUR MINUTE SECOND FRACTION The keyword for the start field must come earlier in the list than, or be the same as, the keyword for the end field. For example, qualifiers of DAY TO FRACTION and MONTH TO MONTH are valid but one of MINUTE TO HOUR is not.

开始字段的关键字必须位于列表结束字段的关键字的前面，或者与结束字段的关键字相同。

例如，DAY TO FRACTION 和 MONTH TO MONTH 的限定符是有效的，但 MINUTE TO HOUR中的条件则不是。

-4632 Parenthetical precision of FRACTION must be between 1 and 5. No precision can be specified for other time units.

In a DATETIME qualifier only the FRACTION field may have a precision in parentheses, and it must be a single digit from 1 to 5.

Check the DATETIME qualifiers in the current statement; one of them violates these rules. The first field of an INTERVAL qualifier may also have a parenthesized precision from 1 to 5. Consult the SQL reference material for the distinction between DATETIME and INTERVAL.

在 DATETIME 限定符中，只有 FRACTION 字段可能具有括号中的精度，并且它必须是从 1 到 5 之间的一位数字。检查当前语句中的 DATETIME 限定符；其中一个违反了这些规则。INTERVAL 限定符的第一个字段也可能具有从 1 到 5 之间的括号精度。有关 DATETIME 和 INTERVAL 间的区别，请参阅 SQL参考资料。

-4633 DATETIME units can only be YEAR, MONTH, DAY, HOUR, MINUTE,SECOND, and FRACTION.

In the current statement there is an error of some sort either in the qualifier of a DATETIME or INTERVAL value, or in the argument of the UNITS function. The only valid precision keywords for these uses are listed in the message. Possibly a keyword has been misspelled, or possibly some other syntax error has prevented 4GL from recognizing the keywords.

在当前语句中，DATETIME 或 INTERVAL 值的限定符或 UNITS 函数的参数中存在某种错误。

消息中列出了这些用法唯一有效的精度关键字。可能是关键字拼写错误，或者可能是其他语法错误阻止了 4GL 识别关键字。

-4634 Symbol name must be a SQL database item name -- either a database name, a tablename or a column name.

The name shown is used in a context that suggests you intend to name a database or an item in a database. However, there is nothing of that name in the current database. Check the spelling of name. If it is as you intended, then make sure that the current database is the one you meant to use.

所显示的名称用于表示要在数据库中命名数据库或项的上下文。但是，当前数据库中没有这个名称。

检查名称的拼写。如果它是您想要的，那么确保当前的数据库是您打算使用的数据库。

-4635 Cannot create temporary file filename to contain a blob variable.

A TEXT or BYTE variable has been located in a temporary file using the LOCATE statement. The current statement assigns a value into that variable, so 4GL attempted to create the temporary file, but an error occurred. Possibly there is no disk space, or possibly your account does not have permission to create a temporary file. 4GL creates a temporary file in the directory specified by the DBTEMP environment variable. Look for operating system error messages that might give more information. Check the value of DBTEMP.

已使用 LOCATE 语句将 TEXT 或 BYTE 变量定位在临时文件中。当前语句为该变量赋值，因此 4GL 试图创建临时文件，但发生错误。可能没有磁盘空间，或者您的账户可能没有创建临时文件的权限。 4GL 在由 DBTEMP 环境变量指定的目录中创建一个临时文件。

查找可能提供更多信息的操作系统错误消息。检查 DBTEMP 的值。

-4638 The maximum size for varchar must be between 1 and 255.

To store strings longer than 255 characters you must use the CHAR data type.

要存储大于 255 个字符的字符串必须使用 CHAR 数据类型。

-4639 Real column name cannot be specified here. The symbol "*" is expected instead.

When defining a RECORD LIKE a table you may not write the name of a single column. Use an asterisk to mean all columns.

当定义 RECORD LIKE 表时，您可能不会写入单个列的名称。使用星号表示所有列。

-4640 Table name is expected here.

When defining a variable or record LIKE a table you must specify a table that exists in the current database (the database selected by the first DATABASE statement in the source file). Only tables in that database can be named in a LIKE definition. Review the spelling of the name and the choice of databases.

当定义变量或记录 LIKE 表时，指定的表必须在当前数据库（源文件中的第一个 DATABASE语句选择的数据库）中存在。只有该数据库中的表可以在 LIKE 定义中命名。

检查名称的拼写和数据库的选项。

-4641 Column name is expected here.

When defining a variable LIKE a column you must specify a table and column. The name here is not a column that appears in the current database (the database selected by the first DATABASE statement in the source file). Review the spelling of the name and the choice of databases.

当定义变量 LIKE 列时，必须指定表和列。此处的名称不是显示在当前数据库中的列（由源文件中第一个 DATABASE 语句选择的数据库）。检查名称的拼写和数据库的选项。

-4642 Subscripting is NOT allowed here.

This message is not returned by any current GBase 8s product. If the error recurs, note all circumstances and contact the GBase Technical Support Department.

此消息不由任何当前 GBase 8s 产品返回。如果出现错误，请注意所有情况，并联系 GBase 技术支持部门。

-4643 A field in the INTERVAL qualifier is out of range. The acceptable ranges are from YEAR to MONTH and from DAY TO FRACTION.

An INTERVAL may specify a period of years and/or months, or a period of days and/or parts of days. However, an interval value may not mix months and days. The qualifier for an INTERVAL may use fields from YEAR and MONTH, or fields from DAY through FRACTION, but it may not have fields from both sets.

INTERVAL 可以指定年和/或月，或者几天和/或几天的部分。但是，间隔值不会混淆几个月和几天。INTERVAL 的限定符可能使用 YEAR 和 MONTH 中的字段，或者 DAY 到 FRACTION 中的字段，但它们可能没有来自两个集合的字段。

-4644 The HELP and ATTRIBUTE clauses each can be specified only once.

Within the scope of an INPUT or DISPLAY ARRAY statement, only one of each of these clauses may be given. Search backward in the source module from this statement; locate all the statements of this type, and reconcile them into one.

在 INPUT 或 DISPLAY ARRAY 语句的范围内，可能只给出这些子句中的一个。从这个语句的源模块中向后搜索；找到该类型的所有语句，并将它们调和成一个。

-4645 4GL does not support returning a blob variable.

The RETURN statement may not name either a BYTE or a TEXT value.

The only way to return such a value from a function is through a global variable.

RETURN 语句可能不会命名 BYTE 或 TEXT 值。从函数返回这样一个值的唯一方法是通过一个全局变量。

-4646 The specified WORDWRAP RIGHT MARGIN value is out of range. It must be greater than or equal to the current column and less than or equal to the report's right margin.

Modify this PRINT statement to specify a right margin for the WORDWRAP function that does not exceed the report right margin.

The report right margin is set in the OUTPUT section of the report.

修改此 PRINT 语句，为 WORDWRAP 函数指定不超过报表右边距的右边距。

报表右边距在报表的 OUTPUT 部分中设置。

-4647 Cannot open file filename to read a TEXT variable value.

This PRINT statement refers to a file or to a TEXT variable has been located in a file using the LOCATE statement. When 4GL attempted to open the file to fetch the value an error occurred. Possibly the file does not exist; possibly your account does not have permission to access it; possibly there was a hardware error. Verify that the file exists and is spelled as shown; then look for operating system messages giving more details.

此 PRINT 语句引用文件或 TEXT 变量，该 TEXT 变量已使用 LOCATE 语句定位于文件中。当 4GL 试图打开文件来获取值市，发生了错误。可能文件不存在；可能您的账户没有权限访问它；可能存在硬件错误。验证文件是否存在，并按照显示拼写；然后查找提供更多详细信息的操作系统消息。

-4648 I/O error while running the 4GL C or p-code compiler.

The compiler received an unexpected operating system error code while opening an input or an output file (a source file, a listing file,an error file etc.) Look for operating system errors that may give more information.

编译器在打开输入或输出文件（源文件、列表文件、错误文件等）时收到意外的操作系统错误代码。

查找可能提供更多信息的操作系统错误。

-4649 I/O error while running fglc: %s.

This messages is not returned by any current GBase 8s product. If it appears, see the discussion of error -4648. If the error recurs,note all circumstances and contact the GBase Technical Support.

所有当前的 GBase 8s 产品不会返回此消息。如果出现，请参阅错误 -4648 的描述。

如果错误再次出现，请注意所有情况并联系 GBase 技术支持。

-4650 Cannot find Runner runner.

Either the normal program runner or the debugger could not be found in the directory named by the GBS_HOME environment variable. Check the setting of the environment variable.

无法在 GBS_HOME 环境变量所指定的目录中找到程序运行程序或调试程序。检查环境变量的设置。INTERVAL 可以指定年和/或月，或者几天和/或几天的部分。但是，间隔值不会混合几个月和几天。INTERVAL 的限定符可能使用 YEAR 和 MONTH 中的字段，或者 DAY 到 FRACTION 中的字段，但它们可能没有来自两个集合的字段。

-4651 The p-code compiler is not contained in your path.

The source module or program cannot be compiled because the compiler cannot be executed. It should be located in the bin directory pointed to by the GBS_HOME environment variable;however, that directory also must be listed in the PATH environment variable before the program can be called.

源模块或程序无法编译，因为编译器无法执行。它应该位于 GBS_HOME 环境变量指向的 bin 目录中；但是，在调用该程序之前，该目录也必须列在 PATH环境变量中。

-4652 The function function name can only be used within an INPUT or CONSTRUCT statement.

The function shown is being used outside of an INPUT or CONSTRUCT statement. However, it returns a result that is only meaningful in the context of INPUT or CONSTRUCT. Review the code to make sure that an END INPUT or END CONSTRUCT statement has not been misplaced. Review the operation and use of the function to make sure you understand it.

显示的函数在 INPUT 或 CONSTRUCT 语句之外使用。然而，它返回的结果只有在输入或构造的上下文中才有意义。检查代码，以确保 END INPUT 或 END CONSTRUCT 语句没有被错误放置。检查该函数的操作和使用情况，以确保您理解它。

-4653 No more than one BEFORE or AFTER INPUT/CONSTRUCT/MENU clause can appear in an INPUT/CONSTRUCT/MENU statement.

There may be only one BEFORE block of statements to initialized each of these statement types. Make sure that the scope of all your INPUT, CONSTRUCT and MENU statements is correctly marked with END statements. Then combine all the preparation code into a single BEFORE block for each one.

可能只有一个 BEFORE 语句块可以初始化这些语句类型中的每一个。确保所有 INPUT、CONSTRUCT 和 MENU 语句的范围用 END 语句正确标记。然后将所有准备代码合并到一个单独的 BEFORE 块中。

Note: Error -4653 with this meaning is issued by 4GL after Version 4.1.

注意：带有这个含义的错误 -4653 由 V4.1之后的 4GL 发布。

-4654 CHAR size should be in the range of 1 to 32766.

The program has declared a variable of type CHAR with a size that is out of the acceptable range.

程序已经声明了一个 CHAR 类型的变量，其大小超出了可接受的范围。

-4655 Invalid range specified for VARCHAR.

The declaration of the fort VARCHAR (maximum, reserved) has incorrectly specified a value for reserved that is not between 0 and maximum,inclusive.

fort VARCHAR（最大值，保留）的声明错误地指定了一个不在 0 和最大值之间的值。

-4656 CANCEL INSERT can only be used in the BEFORE INSERT clause of an INPUT ARRAY statement.

The CANCEL INSERT statement is being used outside of BEFORE INSERT clause of an INPUT ARRAY. Review the code to make sure that CANCEL INSERT has not been used anywhere else except in the BEFORE INSERT clause.

在 INPUT ARRAY 的BEFORE INSERT 子句之外使用 CANCEL INSERT 语句。

查看代码，以确保除 BEFORE INSERT 子句之外，没有任何其它地方使用 CANCEL INSERT 。

-4657 CANCEL DELETE can only be used in the BEFORE DELETE clause of an INPUT ARRAY statement.

The CANCEL DELETE statement is being used outside of BEFORE DELETE clause of an INPUT ARRAY. Review the code to make sure that CANCEL DELETE has not been used anywhere else except in the BEFORE DELETE clause.

在 INPUT ARRAY 的 BEFORE DELETE 子句之外使用 CANCEL DELETE 语句。

查看代码，以确保除 BEFORE DELETE 子句之外，没有任何其它地方使用 CANCEL DELETE 。

-4658 Constants are not allowed as cursor names.

Identifiers that are used for dynamic cursor names must be variables.

用于动态游标名称的标识符必须是变量。

-4659 The CHAR (*) type is not allowed for report parameters.

A formal argument cannot accept a character data type of unspecified length, such as CHAR(*).

形参不能接受未指定长度的字符数据类型，如 char(*)。

-4660 Report parameters cannot take object references.

A formal argument cannot specify a class name (or FOREIGN) as its data type.

形参不能指定类名（或 FOREIGN）作为其数据类型。

-4661 Access control restrictions are not allowed for this intrinsic member function.

The intrinsic member functions !copy() and !derive() must have PUBLIC access control, which is the default access control for member functions.

内部成员函数 !copy() 和 !derive() 必须具有 PUBLIC 访问控制权限，这是成员函数的默认访问控制权限。

-4663 ODBC error from engine - "text".

The -useccl compiler switch has been used. An ODBC error, shown here as"text", has been detected.

已使用 -useccl 编译器开关。已检测到ODBC错误，此处显示为“text”。

-4664 CCL class declarations are required with the "-useccl" switch. Add INCLUDE SYSTEM "ixstmt.4gh" to your module.

To compile a REPORT or the MAIN program block with the -useccl switch,the user needs to include ixstmt.4gh.

要用 -useccl 开关编译报表或主程序块，用户需要包含 ixstmt.4gh。

This statement has calls to functions nested within the parameter lists of other function calls, to a level exceeding four. A maximum level of four is supported, as in the following expression:Afun(2-Bfun(3+Cfun(4*Dfun(5))))该语句将调用嵌套在其他函数调用参数列表中的函数，其级别超过 4。支持的最大级别为 4，如下表达式所示：Afun(2-Bfun(3+Cfun(4*Dfun(5))))Rewrite the expression to store the result of the innermost function calls in a variable, and use the variable in the expression.

重写表达式以将最内部函数调用的结果存储在变量中，并在表达式中使用该变量。

-4665 Warning: Report page header or trailer output must end with a newline,so a newline will be automatically appended.

A report header or trailer contained a semicolon (;) at the end of the line. In the body of the report, a trailing semicolon suppresses the creation of a new line. The header and trailer must end with a new-line character to perform properly. The compiler has ignored the semicolon.

To prevent this warning message from appearing, remove the semicolon from the source code.

报表头或尾部在行尾包含一个分号（;）。在报表的正文中，尾部的分号会抑制新行的创建。

头部和尾部必须以换行符结束才能正常执行。编译器忽略了分号。为防止出现此警告消息，请从源代码中删除分号。

-4666 Problem encountered in populating the repository.

For a detailed description of the problem, see the repold.log file in either $GBS_HOME\temp or the current directory.

有关该问题的详细说明，请参阅 $GBS_HOME\temp 或当前目录中的 repold.log文件。

-4667 Class name is only forward declared in this file.

Updating the repository with a forward-declared class is discouraged.

不鼓励用前向声明的类更新存储库。

-4668 The report output, specified by a START REPORT statement, is not any of file, pipe, screen, printer,pipe in line mode, or pipe in form mode.

The output of a report can be sent only to any of file,pipe (in form or line modes), screen, or printer.

报表的输出只能发送到文件、管道（表单或线路模式）、屏幕或打印机中。

-4669 The function fgl_setcurrline can only be used in INPUT/DISPLAY ARRAY block.

The function is being used outside of an INPUT/DISPLAY ARRAY block. Review the code to make sure that fgl_setcurrline has not been used anywhere else except in the INPUT/DISPLAY ARRAY block.

该函数在 INPUT/DISPLAY ARRAY 块之外使用。检查代码，以确保除了在INPUT/DISPLAY ARRAY 块中之外，没有在任何其他地方使用 FGL_setcurrline。

-4670 Multiple INTO clauses cannot be used inside SQL...END SQL block.

Only one INTO clause can be used inside the SQL...

END SQL block. Review the code to make sure that more than one INTO clause has not been used.

在 SQL ... END SQL 块中只能使用一个 INTO 子句。查看代码以确保没有使用多个 INTO 子句。

-4671 Missing END SQL after semicolon(;) in SQL...END SQL block.

A optional semicolon(;) can be used to mark the end of an SQL statement inside the SQL...END SQL block. The program has encountered a semicolon(;) but could not find END SQL immediately after that. Review the code to make sure that the END SQL directive appears immediately after the semicolon(;).

可以使用可选的分号（;）来标记 SQL ... END SQL 块内的 SQL 语句的结束。该程序遇到了分号（;），但在此之后无法立即找到 END SQL。

查看代码以确保 END SQL 指令立即出现在分号（;）后面。

-4701 The -V option must be used on its own with no other arguments.

The -V option requests that the program display the version number and then terminate. No other options are allowed with this option. To display the version number, repeat the command, but with only the -V option.

-V 选项要求程序显示版本号，然后终止。此选项不允许与其他选项一起使用。

要显示版本号，请重复该命令，但仅使用 -V 选项。

-4702 No program was specified.

The command cannot be executed because you did not specify the program name. Repeat the command with the name of a NewEra program as an argument.

该命令无法执行，因为您没有指定程序名称。以 NewEra 程序的名称作为参数重复该命令。

-4703 Invalid option name.

You specified an option that the program does not recognize. For the valid options of this command, refer to your documentation. Repeat the command, using only valid options.

您指定了该程序无法识别的选项。有关此命令的有效选项，请参阅您的文档。重复该命令，仅使用有效的选项。

-4704 Option name requires an argument.

You specified an option that the program does not recognize. For the valid options of this command, refer to your documentation. Repeat the command, using only valid options.

您指定了该程序无法识别的选项。有关此命令的有效选项，请参阅您的文档。重复该命令，仅使用有效的选项。

-4801 Only 1, 2 or 3 can be used with WITH DIMENSIONS.

The syntax for declaring a dynamic array is DEFINE arrname DYNAMIC ARRAY [with n dimensions] OF TYPE.

The value of n can be 1,2, or 3. If not specified, a default of 1 is assumed.

声明动态数组的语法是 DEFINE arrname DYNAMIC ARRAY [n] OF TYPE。

n 的值可以是1、2 或 3。如果未指定，则默认为 1。

-4802 Dynamic array of a record with BLOB as one of the members is not allowed.

A dynamic array of records cannot have a BLOB or TEXT data type as one of its members.

动态记录数组不能将 BLOB 或 TEXT 数据类型作为其成员之一。

-4803 The variable used in ALLOCATE/DEALLOCATE/RESIZE ARRAY statement can only be a variable of the DYNAMIC ARRAY type.

The subject of an ALLOCATE, DEALLOCATE, or RESIZE statement must be a variable of type DYNAMIC ARRAY. The variable can be a dynamic array of any simple type or a 4GL RECORD type.

ALLOCATE、DEALLOCATE 或 RESIZE 语句的主体必须是 DYNAMIC ARRAY 类型的变量。

该变量可以是任何简单类型或 4GL RECORD 类型的动态数组。

-4804 Subscripting cannot be applied to the variable "%s"because it is not an array variable.

Only variables of the type ARRAY or DYNAMIC ARRAY can have subscripts applied to them. If the compiler encounters a subscript operation on a variable of some other type, it generates this error.

只有 ARRAY 或 DYNAMIC ARRAY 类型的变量应用下标。如果编译器在其他类型的变量上遇到下标操作，则会生成此错误。

-4805 The variable on which ALLOCATE/DEALLOCATE/RESIZE ARRAY statement is to act must be a dynamic array.

A variable of the type DYNAMIC ARRAY can be the subject of ALLOCATE, DEALLOCATE, or RESIZE statements. The variable can be a dynamic array of any simple type or a 4GL RECORD type.

DYNAMIC ARRAY 类型的变量可以是 ALLOCATE、DEALLOCATE 或 RESIZE语句的主体。该变量可以是任何简单类型或 4GL RECORD 类型的动态数组。

-4806 The dynamic array has been allocated already.

The array has been allocated using an ALLOCATE statement.

Use DEALLOCATE before trying to ALLOCATE it again, or use RESIZE to change the extent sizes.

该数组已使用 ALLOCATE 语句进行分配。在尝试再次分配之前使用 DEALLOCATE，或者使用 RESIZE 更改盘区大小。

-4807 Accessing elements of a dynamic array that has not been allocated is not allowed.

The dynamic array has not been allocated. Allocate a dynamic array with the ALLOCATE DYNAMIC ARRAY statement. The syntax is ALLOCATE ARRAY[extent information] See the 4GL Reference Manual for more details.

尚未分配动态数组。使用 ALLOCATE DYNAMIC ARRAY 语句分配一个动态数组。

语法为 ALLOCATE ARRAY＆lt; arrayname> [范围信息]有关更多详细信息，请参见 4GL 参考手册。

-4808 RECORD nesting is not allowed when DYNAMIC ARRAY OF RECORD is involved.

You cannot define a RECORD element where the top level record is a DYNAMIC ARRAY type. Replace the top level DYNAMIC ARRAY OF RECORD with an ARRAY type.

不能定义顶级记录是 DYNAMIC ARRAY 类型的 RECORD 元素。将 DYNAMIC ARRAY OF RECORD替换为 ARRAY 类型。

-4809 DEALLOCATE ARRAY statement can only have the array name. It cannot have subscripts.

You deallocate a dynamic array only by using the array name without subscripts. You cannot use a statement like the one below, with a subscript:DEALLOCATE ARRAY dynarr[10]Instead, use the statement as follows:DEALLOCATE ARRAY dynarr仅通过使用数组名称而不使用下标来释放动态数组。不能像下面的语句那样使用下标：DEALLOCATE ARRAY dynarr[10]相反，如下所示地使用语句：DEALLOCATE ARRAY dynarr-4810 Subscript was missing on the dynamic array variable "%s" for ALLOCATE/RESIZE.

The ALLOCATE and RESIZE statements need the (new)size. If the subscripts are missing, then this error is generated.

Example:ALLOCATE ARRAY dynarr[10]ALLOCATE 和 RESIZE 语句需要（新）的尺寸大小。如果丢失了下标。则会发生此错误。

示例：ALLOCATE ARRAY dynarr[10]-4811 DYNAMIC ARRAY in a DYNAMIC ARRAY OF RECORD is not allowed.

You cannot have a DYNAMIC ARRAY inside a DYNAMIC ARRAY of RECORD.

Replace it with an ARRAY type.

在 RECORD 的 DYNAMIC ARRAY 中不能有 DYNAMIC ARRAY。将其替换为 ARRAY 类型。

-4813 Dynamic array ALLOCATE/RESIZE parameters must be positive and non zero.

Check your RESIZE or ALLOCATE statement. Subscript values must be positive and non zero.

请检查您党的 RESIZE 或 ALLOCATE 语句。下标值必须是非零的正整数。

-4814 Dynamic arrays passed/returned should be of similar characteristics.

A dynamic array passed to functions or returned from a function:a. Must be of the same type as the function passed/returned b. Must have the same number of extents for both functions c. If it is a dynamic array of record, must have both records the same size传递给函数或从函数返回的动态数组：a.必须与传递/返回的函数的类型相同。

b.对于这两个函数，必须有相同数量的 extent。

c.如果它是一个动态记录数组，则记录必须具有相同的大小。

-4815 Only dynamic arrays can be used for fgl_isdynarr_allocated or fgl_dynarr_extentsize.

Use a DYNAMIC ARRAY only as an argument for the fgl_isdynarr_allocated function and as the first argument for the fgl_dynarr_extentsize function.

The dynamic array name should be used without any subscripts.

仅将 DYNAMIC ARRAY 用作 fgl_isdynarr_allocated 函数的参数，并将其作为fgl_dynarr_extentsize 函数的第一个参数。动态数组名称应该没有任何下标。

-4816 Dynamic array used in fgl_dynarr_extentsize function should be in ALLOCATEd state.

The function can be used only with a dynamic array that has been allocated. Use the ALLOCATE ARRAY statement before the fgl_dynarr_extentsize function is called.

该函数只能与已分配的动态数组一起使用。在调用 FGL_dynarr_extentsize函数之前使用 ALLOCATE ARRAY 语句。

-4817 The dynamic array for which fgl_dynarr_extentsize(dynarr, n)is being used does not have the 'n'th dimension.

The array for which fgl_dynarr_extentsize function has been called does not have the nth dimension. Look at the array definition in the DEFINE DYNAMIC ARRAY statement and find out how many dimensions it has.

调用 fgl_dynarr_extentsize 函数的数组不具有第 n 维。查看 DEFINE DYNAMIC ARRAY语句中的数组定义，并找出它的维度。

-4818 Delimiter should be comma, when format is CSV. It should be a newline when format is TEXT.

When the format specified is CSV (Comma Separated Values), the delimiter must be Comma. Similarly if the format specified is text, the delimiter must be new-line.

Change the Delimiter accordingly.

当指定格式为 CSV（逗号分隔值）时，分隔符必须是逗号。同样，如果指定的格式是文本，分隔符必须是换行。相应地更改分隔符。

-4819 Only LOAD, CSV and TEXT formats are supported.

The formats that can be specified are LOAD, CSV(Comma Separated values) and TEXT.

Specify the format of the file as either LOAD, CSV or TEXT.

可以指定的格式是 LOAD、CSV（逗号分隔值）和TEXT。指定文件的格式为 LOAD、CSV 或 TEXT。

-4820 Delimiter should be set only when format is specified.

The delimiter must be set only when format of the file is specified.

Specify the format of the file to either LOAD, CSV or TEXT and then specify the delimiter.

只有在指定了文件的格式时，才能设置分隔符。指定文件的格式为 LOAD、CSV 或 TEXT，然后指定分隔符。

-4821 The file file_name cannot be created or opened.

Accompanying OS message : OS_Message.

Check that your username, has permission to create files in the specified directory.

Look for the accompanying error messages from the operating system. Possibly the disk is full, or you have reached a limit on the number of open files.

检查您的用户名是否有权在指定的目录中创建文件。从操作系统中查找伴随的错误消息。

可能磁盘已满，或者您打开文件的数量已达到限制。

-4822 The file file_name cannot be closed.

Accompanying OS message : OS_Message.

The file cannot be closed. Look for the accompanying error messages from the operating system. Possibly the file is not opened, or the file descriptor specified may not be correct.

该文件不能关闭。从操作系统中查找附带的错误消息。可能文件未打开，或者指定的文件描述符可能不正确。

-4823 The file associated with the file descriptor may not be opened.

The file descriptor specified may not be associated with a file. Possibly the file may already be closed or the file descriptor may be changed in the program.

Revisit the program logic.

指定的文件描述符不能与文件关联。可能文件已经关闭，或者文件描述符可能在程序中被更改。

重新检查程序逻辑。

-4824 The file "%s" cannot be read.

Accompanying OS message : "%s".

The file cannot be read. Check that your username, has permission to read the file.

Look for the accompanying error messages from the operating system. Possibly, the file is already closed, or the disk is full, or a hardware failure occurred.

该文件无法读取。检查您的用户名是否有权读取文件。从操作系统中查找附带的错误消息。

可能该文件已关闭，或磁盘已满，或发生硬件故障。

-4825 Seek on file file_name cannot be done.

Accompanying OS message : OS_Message.

Seek on the file cannot be done. Look for the accompanying error messages from the operating system. Possibly the file may already be closed or the file descriptor may be changed in the program.

无法对文件进行查找。从操作系统中查找附带的错误消息。可能文件已经关闭，或者文件描述符可能在程序中被更改。

-4826 The file file_name cannot be written.

Accompanying OS message : OS_Message.

The file cannot be written. Check that your username, has permission to write to the file. Look for the accompanying error messages from the operating system.

Possibly, the file is already closed, or the disk is full, or a hardware failure occurred.

该文件无法写入。检查您的用户名是否有权读取文件。从操作系统中查找附带的错误消息。

可能该文件已关闭，或磁盘已满，或发生硬件故障。

-4827 The string in the file file_name is too long to fit in the variable.

The length of the variable is less than the length of the string read from the file.

The String cannot be stored in the variable. Increase the size of the variable.

变量的长度小于从文件中读取的字符串的长度。字符串不能存储在变量中。增加变量的大小。

-4828 The field to be read from the file file_name should not be greater than 4096 bytes.

The length of the string read from the file exceeds 4096 bytes. Check the field in the file.

Possibly, the file delimiter is misplaced.

从文件中读取的字符串长度超过 4096 字节。检查文件中的字段。可能，文件分隔符被放错位置。

-4829 Memory allocation error.

It has proven impossible to allocate memory for a small fixed size structure needed by a File IO function such as Open or Close. The amount of memory needed is small; almost any reduction in program size should avoid the error.

事实证明，不可能为文件 IO 函数所需的小型固定大小结构（如打开或关闭）分配内存。

所需的内存量很小；几乎任何程序大小的减少都应该避免错误。

-4830 The variable var_name is not of type INTEGER or SMALLINT. It cannot be used as a file descriptor.

The variable used as a file descriptor must be an integer type. Specify a different variable, or redefine the one named.

用作文件描述符的变量必须是整数类型。指定一个不同的变量，或重新定义一个指定的变量。

-4831 The variable var_name is not of type INTEGER or SMALLINT. It cannot be used to store offset bytes returned from the seek operation.

The variable used to store the offset bytes returned from the seek operation must be an integer type. Specify a different variable, or redefine the one named.

用于存储从查找操作返回的偏移字节的变量必须是整数类型。指定一个不同的变量，或重新定义一个指定的变量。

-4850 Insufficient space for formatted INTERVAL value.

The INTERVAL value could not be accommodated within the allocated buffer.

无法在分配的缓冲区中容纳 INTERVAL 值。

-4851 Invalid INTERVAL value.

The INTERVAL value has an invalid character.

The syntax of an INTERVAL value must begin with the character 'P'.

INTERVAL 值具有一个无效的字符。

INTERVAL 值的语法必须使用字符‘P’开头。

-4852 Invalid INTERVAL value.

The INTERVAL value has an invalid character.

Any hours, minutes, or seconds in the durationmust begin with 'T''.

INTERVAL 值具有一个无效的字符。

任何小时、分钟或秒的持续时间必须以 'T' 开头。

-4853 Extra (non-blank) characters at the end of a interval value.

Only spaces can follow an INTERVAL literal. Inspect the INTERVAL values.

只有空格可以遵循 INTERVAL 文字。检查 INTERVAL 值。

-4854 Invalid INTERVAL value.

An Invalid character is used as a marker in an INTERVAL value.

Valid markers are YMDTHMS.

无效字符作为 INTERVAL 值的标记。有效标记是 YMDTHMS。

-4855 Invalid INTERVAL value.

A Valid marker is used incorrectly in an INTERVAL value.

Review the markers used for INTERVAL qualifiers like YMDTHMS to ensure they are used at the right place in the value.

INTERVAL值中有效标记的使用不正确。查看用于 INTERVAL 限定符（如 YMDTHMS ）的标记，以确保它们在值中的正确位置使用。

-4856 No digits where digits required in INTERVAL value.

Review the INTERVAL value to ensure it is not missing a field.

In an INTERVAL literal, the first field is a count and can have as many digits as the qualifier specifies.

检查 INTERVAL 值以确保它没有丢失字段。

在 INTERVAL 文字中，第一个字段是一个计数，并且可以有限定符指定的位数。

-4857 Too many digits in field of INTERVAL value.

The first field of an INTERVAL literal must contain either 1 or 2 digits(if it is not a YEAR) or 2 or 4 digits (if it is a YEAR).

Review the INTERVAL literals in this statement and correct them as necessary.

INTERVAL 文字的第一个字段必须包含 1 或 2 个数字（如果不是 YEAR）或 2 或 4 个数字（如果它是YEAR）。查看该语句中的 INTERVAL 值并根据需要进行更正。

-4858 Invalid INTERVAL value.

The INTERVAL value has repeated mark letters. An INTERVAL value can specify either a period of years and/or months, or a period of days and/or parts of days.

It cannot specify both years and/or months and days and/or parts of days.

The INTERVAL value must follow the first to last format and cannot have the same units repeated.

INTERVAL 值具有重复的标记字母。INTERVAL 值可以指定年份和/或月份的时间段，或者指定几天和/或几天的时间段。它不能指定年份和/或月份，日期和/或部分天数。

INTERVAL 值必须遵循第一个到最后一个格式，并且不能重复相同的单位。

-4859 Invalid INTERVAL value.

The INTERVAL value has an invalid sequence of mark letters.

An INTERVAL value can contain either a year-month interval or a day-time interval.

An INTERVAL value must follow the first to last format l. The qualifier for an INTERVAL can specify fields from YEAR and MONTH, or fields from DAY through FRACTION,but it can not specify fields from both sets.

INTERVAL 值具有无效的标记字母序列。INTERVAL 值可以包含年份间隔或日间间隔。一个INTERVAL 值必须遵循第一个到最后一个格式 l。INTERVAL 的限定符可以指定 YEAR 和MONTH 中的字段，或从 DAY 到 FRACTION 的字段，但不能指定两个集合中的字段。

-4860 Invalid INTERVAL value.

Fraction only allowed in seconds in INTERVAL value and decimal point should be between second and fraction.

Review the literal qualifier for missing or misplaced punctuation.

在 INTERVAL 值中分数只允许以秒为单位，小数点应在秒和分数之间。检查文字限定符是否丢失或错位标点符号。

-4861 Output buffer not big enough to hold the DATETIME value.

This error is returned when the function is called and the address space for the output buffer is null or smaller than the format-string length.

当函数被调用并且输出缓冲区的地址空间为空或小于格式字符串长度时，将返回此错误。

-4862 Invalid DATETIME format.

The XSD format of a DATETIME value is not supported.

DATETIME 值不支持 XSD 格式。

-4863 Invalid DATETIME format.

The DATETIME value does not match the required format.

DATETIME值与所需的格式不匹配。

The DATETIME value is missing at least one field, or repeating a field value, or has a missing, misplaced, or repeated delimiter,or has improper Markers in the xsd DATETIME value.

DATETIME 值至少缺少一个字段，或者重复了一个字段值，或者丢失、放错位置或重复了分隔符，或者在 xsd DATETIME 值中包含不正确的标记。

-4864 Invalid character in DATETIME value.

The form of a DATETIME literal is very limited and can contain only decimal digits and the following delimiters: the hyphenbetween year, month, and day numbers; the space between day and hour;the colon between hour, minute, and second; and the decimal point between second and fraction.

DATETIME 文字的格式非常有限，只能包含十进制数字和以下分隔符：年，月和日之间的连字符；日间和小时之间的空格；小时、分钟和秒之间的冒号；以及秒和分数之间的小数点。

Any error is returned if Any other characters or any of the allowed characters are used in the wrong order.

如果任何其他字符或任何允许的字符以错误的顺序使用，则返回任何错误。

-4865 Field value out of acceptable range in DATETIME value.

The DATETIME value contains at least one incorrect field or is missing at least one field.

DATETIME 值至少包含一个不正确的字段或至少缺少一个字段。

Possible errors include: Using zero for the year; using numbers other than 1 to 12 for the month, 1 to 31 for the day, 0 to 23 for the hour,or 0 to 59 for the minute or second; using an inappropriate number for the month; and using a fraction with too many digits for the specified precision.

可能的原因为：年使用零；月份使用了除 1 至 12 的数字，天使用了除 1 至 31 的数字，小时使用了除 0 至 23 之外的数字，或分钟或秒使用了 0 至 59 之外的数字；使用了一个不合适的月份数；并使用指定精度的位数过多的分数。

-4866 Invalid DATETIME format .

The Field value is too wide for an xsd DATETIME value.

字段值对于 xsd DATETIME 值来说太宽了。

-4986 Communication between fgld daemon and application server was closed.

Connection between fgld daemon and application server was interrupted,check if application server is able to send request to fgld daemon running.

fgld 守护程序和应用程序服务器之间的连接中断，请检查应用程序服务器是否能够将请求发送到正在运行的 fgld 守护程序。

-4987 The supplied argument does not match with a function definition Match the supplied argument with the function definition described in the WSDL file and correct the argument either in the configuration file or in the 4GL client application.

将提供的参数与 WSDL 文件中描述的函数定义匹配，并在配置文件或 4GL 客户端应用程序中更正参数。

-4988 The number of environment values received is different from the number expected The client has not provided the sufficient number of environment values.

Ensure that the client application correctly processes the GBASEDBTSERVER, CLIENT_LOCALE, and DB_LOCALE in the code.

客户端没有提供足够数量的环境值。确保客户端应用程序正确处理代码中的GBASEDBTSERVER、CLIENT_LOCALE 和 DB_LOCALE。

-4989 A client is attempting to invoke a web service that does not exist Match the SERVICENAME in the subscriber configuration file with the web service name in the WSDL file.

将订阅服务器配置文件中的 SERVICENAME 与 WSDL 文件中的Web服务名称匹配。

-4990 Unrecoverable error in application server The application server encountered an unrecoverable error.

Note the scenario and contact GBase Technical Support.

应用程序服务器遇到不可恢复的错误。

请注意场景并联系 GBase 技术支持。

-4991 Operation failed while converting data from the XSD format to the SQL format Ensure that input values match the input parameter types in WSDL file.

确保输入值与 WSDL 文件中的输入参数类型匹配。

-4992 Message protocol error Note the scenario and contact GBase Technical Support.

请注意场景并联系 GBase 技术支持。

-4993 Supplied service name or operation name (%s) cannot be found The given web-service name or the operation cannot not be found.

Match the SERVICENAME in the subscriber configuration file with the web service name in the WSDL file. Or, match the [FUNCTION]...NAME that follows the SOAP_NAME tag in the subscriber configuration file with the operation name in the WSDL file.

给定的 Web 服务名称或操作无法找到。将订阅配置文件中的 SERVICENAME 与 WSDL 文件中的 Web 服务名称相匹配。或者，将订阅服务器配置文件中 SOAP_NAME 标记后面的[FUNCTION] ... NAME 与 WSDL 文件中的操作名称匹配。

-4994 The number of inputs received does not match the number of inputs defined in the web service Match the supplied input argument(s) with the input argument(s)function definition described in the WSDL file and correct the argument either in the configuration file or in the 4GL client application.

将提供的输入参数与 WSDL 文件中描述的输入参数(s)函数定义匹配，并在配置文件或 4GL客户端应用程序中更正参数。

-4995 The number of outputs received does not match the number of outputs defined in the web service Match the supplied output argument(s) with the output argument(s)function definition described in the WSDL file and correct the argument either in the configuration file or in the 4GL client application.

将提供的输出参数与 WSDL 文件中描述的输出参数函数定义匹配，并在配置文件或 4GL客户端应用程序中更正该参数。

-4996 Unknown host name or port number Ensure that the web service publisher has:1. Set the environment variables FGLD_HOSTNAME and FGLD_PORTNUMBER 2. Run the fgld on the FGLD_PORTNUMBER specified 3. Run Axis2C on the same terminal where fgld is running确保 Web 服务发布者具有：1）设置环境变量 FGLD_HOSTNAME 和 FGLD_PORTNUMBER 2）在指定的 FGLD_PORTNUMBER 上运行 fgld 3）在运行 fgld 的同一终端上运行Axis2C-4997 Port number (%s) must be in the range 1024 - 65535 The port number set in the FGLD_PORTNUMBER environment variable is not in the valid range 1024 - 65535.

FGLD_PORTNUMBER 环境变量中设置的端口号不在有效范围 1024 - 65535 内。

-4998 Operation failed while converting data from the SQL format to the XSD format Ensure that output values match the output parameter types in WSDL file.

确保输出值与 WSDL 文件中的输出参数类型匹配。

-5000 CSM error: A CSM (Communications Support Module), in the database server or in the client, detected an error.

在数据库服务器或客户端中，CSM(通信支持模块)检测到错误。

This error code is a general CSM error code. It can be used by individual CSMs to reflect different error conditions. The text provides clues about the possible cause of the error.

此错误代码是一般的 CSM 错误代码。它可以用于单个 CSMS，以反映不同的误差情况。

文中提供了错误的可能原因的线索。

If the confidentiality option is enabled for a particular CSM, you might see the following example of this error code: "CSM error: CSM: received message of unexpected type." This implies that the CSM on the user's side(either database server side or client application side) cannot interpret the messages it receives. Make sure that the confidentiality option is set for both the database server and the client application.

如果为特定的 CSM 启用了保密性选项，您可能会看到此错误代码的以下示例：“CSMCSM error: CSM: received message of unexpected type”。

这意味着用户端(数据库服务器端或客户端应用程序端)上的 CSM 无法解释接收到的消息。确保为数据库服务器和客户端应用程序设置了保密性选项。

Check your sqlhosts file and CSS configuration file. Check the error message on the other side (either database server side or client application side) for more clues about the possible cause of the error.

检查 sqlhost 文件和 CSS 配置文件。检查另一端(数据库服务器端或客户端应用程序端)的错误消息，以获得有关错误可能原因的更多线索。

Also make sure that the CSM you are using is supported by the database server or the client SDK. If the problem persists, contact GBase Technical Support or the CSM vendor. Have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

还要确保数据库服务器或客户端 SDK 支持您使用的 CSM。如果问题仍然存在，请与 GBase 技术支持部门或 CSM 供应商联系。请提供以下信息：客户端和数据库服务器的 CSS 配置文件和 sqlhost 信息。

-5001 CSM: memory allocation error.

A CSM (Communications Support Module), in the database server or in the client, could not acquire memory for processing.

Make sure that the system configuration makes sufficient memory available for dynamic allocation. If that fails, contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

数据库服务器或客户端中的 CSM（通信支持模块）无法获取要处理的内存。

确保系统配置为动态分配提供足够的内存。如果失败，请联系 GBase 技术支持或 CSM 供应商，并提供以下信息：客户端和数据库服务器的 CSS 配置文件和 sqlhosts 信息。

-5002 CSM: memory de-allocation error.

A CSM (Communications Support Module), in the database server or in the client, could not deallocate memory. This error message arises only when some form of memory corruption has occurred.

数据库服务器或客户端中的 CSM（通信支持模块）无法取消分配内存。只有发生某种形式的内存损坏时才会出现此错误消息。

Contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

请联系 GBase 技术支持或 CSM供应商，并提供以下信息：客户端和数据库服务器的 CSS配置文件和 sqlhosts 信息。

-5003 CSM: file I/O error.

A CSM (Communications Support Module), in the database server or in the client, could not complete a file read or write operation successfully.

This error can occur only during use of a CSM.

数据库服务器或客户端中的 CSM（通信支持模块）无法成功完成文件读取或写入操作。

该错误只能在使用 CSM 期间发生。

Validate that all files that the CSM requires for operation are available for read and write access by the user in the client or by user GBase 8s in the database server. If that fails, contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

验证CSM要求操作的所有文件都可供用户在客户端或数据库服务器中的用户 Gbasedbt 进行读取和写入访问。如果失败，请联系 GBase 技术支持或 CSM 供应商，并提供以下信息：客户端和数据库服务器的 CSS 配置文件和 sqlhosts 信息。

-5004 CSM: invalid context.

A CSM (Communications Support Module), in the database server or in the client, detected a context that contains invalid data or that is inconsistent with the current operation or CSM state. This error normally occurs during input or output message processing (as opposed to context establishment).

数据库服务器或客户端中的 CSM（通信支持模块）检测到包含无效数据或与当前操作或 CSM状态不一致的上下文。这种错误通常发生在输入或输出消息处理期间（与上下文建立相反）。

Contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

请联系 GBase 技术支持或 CSM 供应商，并提供以下信息：客户端和数据库服务器的 CSS配置文件和 sqlhosts 信息。

-5005 CSM: unsupported feature.

A CSM (Communications Support Module), in the database server or in the client, found either a global or connection parameter specification that the current version of the CSM does not support. The CSM could also find that the peer CSM, through the internal CSM-to-CSM protocol, indicated the use of an option that this CSM instance does not support.

CSM（通信支持模块）在数据库服务器或客户端中找到了 CSM 当前版本不支持的全局或连接参数规范。

CSM 还可以发现对等 CSM 通过内部 CSM-to-CSM 协议指示使用该 CSM 实例不支持的选项。

Remove any option that the CSM does not support or upgrade the CSM to one that supports the option. Install and activate matching versions of the CSMs in the client and database server. If the problem recurs, contact GBase Technical Support or the CSM vendor and have the following Information available: CSS configuration files and sqlhosts information for both the client and the database server.

删除 CSM 不支持的选项或将 CSM 升级到支持该选项。在客户端和数据库服务器上安装并激活CSM 的匹配版本。如果问题再次出现，请联系 GBase 技术支持或 CSM 供应商，并提供以下信息：客户端和数据库服务器的 CSS 配置文件和 sqlhosts 信息。

-5006 CSM: invalid global options.

A CSM (Communications Support Module) found a global option that the current version of the CSM does not support. The global option string is specified in the CSS configuration file.

CSM（通信支持模块）找到了当前版本的 CSM 不支持的全局选项。全局选项字符串在 CSS 配置文件中指定。

Remove any options that the CSM does not support from the global option specification or upgrade the CSM to one that supports the options. If the problem recurs,contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

从全局选项规范中删除 CSM 不支持的选项，或将 CSM 升级到支持该选项。如果问题再次出现，请联系 GBase 技术支持或 CSM 供应商，并提供以下信息：客户端和数据库服务器的 CSS 配置文件和 sqlhosts 信息。

-5007 CSM: invalid context options: A CSM (Communications Support Module), in the database server or in the client, found a CSM connection option specification that the current version of the CSM does not support. The connection options string is specified in the CSS configuration file, and the csm option field in the sqlhosts file. The text in the error message shows any options that the CSM does not support.

数据库服务器或客户端中的 CSM（通信支持模块）找到了 CSM 当前版本不支持的 CSM 连接选项规范。连接选项字符串在 CSS 配置文件中指定，CSM 选项字段在 sqlhost 文件中指定。错误消息中的文本显示 CSM 不支持的任何选项。

Remove any options that the CSM does not support from the CSM connection option specification or upgrade the CSM to one that supports the options.

If the problem recurs, contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

从 CSM 连接选项规范中删除 CSM 不支持的任何选项，或者将 CSM 升级到支持该选项。

如果问题再次出现，请联系 GBase 技术支持或 CSM 供应商，并提供以下信息：客户端和数据库服务器的 CSS 配置文件和 sqlhosts 信息。

-5008 CSM: peer disconnected.

A CSM (Communications Support Module), in the database server or in the client, received a message from the peer CSM (using their private CSM-to-CSM protocol) to initiate an orderly tear-down of their respective CSM contexts. This CSM responded by returning to the caller (CSS and its caller) with this message. This message might not be an error, but might actually be part of the protocol. A typical event that might trigger this disconnection is the expiration of a credential (such as an old Kerberos ticket, an association that is too long if the CSM functionality includes placing limits on the duration of SQL sessions, or an expired X.509 certificate). This error can occur only during use of a CSM.

数据库服务器或客户端中的 CSM（通信支持模块）接收到来自对等 CSM 的消息(使用它们的私有 CSM-to-CSM 协议)，从而启动对各自 CSM 上下文的有序拆卸。此 CSM 的响应是将此消息返回给调用方(CSS 及其调用方)。此消息可能不是错误，但实际上可能是协议的一部分。可能触发此断开连接的一个典型事件是凭据的过期(例如旧 Kerberos 票证、如果 CSM 功能包括限制SQL会话持续时间的关联或过期的 X.509 证书)。此错误只能在使用 CSM 时发生。

If the disconnection seems unexpected and the problem persists, contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

如果断开连接是个意外并且问题仍然存在，请联系 GBase 技术支持或 CSM 供应商，并提供以下信息：客户端和数据库服务器的 CSS 配置文件和 sqlhosts 信息。

-5009 CSM: authentication error.

A CSM (Communications Support Module) that performs principal authentication either in the database server or in the client failed to authenticate the principal.

在数据库服务器或客户端执行主体认证的 CSM（通信支持模块）无法认证主体。

If this error occurs during session establishment, the connection establishment fails. Otherwise, the connection is dropped.

如果在会话建立期间发生此错误，则连接建立失败。否则，连接将被删除。

A common cause for this error is that an invalid password is given or the desired database server does not consider the client computer or your user ID trusted.

导致此错误的常见原因是给出了无效的密码，或者所需的数据库服务器任务客户端计算机或您的用户 ID 是不可信。

Provide a correct password as required by the authentication. Or ask the system administrator to include the client computer as a trusted host and/or your user ID as a trusted user in the /etc/hosts.equiv file on the database server computer or in the .rhosts file in your home directory on the database server computer. For more information, see the UNIX manual pages on HOSTS.EQUIV(5).

根据认证要求提供正确的密码。或者要求系统管理员将客户端计算机作为受信任的主机，并/或将您的用户 ID 作为受信任的用户包括在数据库服务器计算机上的 /etc/hosts.equv 文件中，或者在数据库服务器计算机上的主目录中的 .rhost 文件中。有关更多信息，请参阅 HOSTS.EQUIV(5)上的 UNIX 手册页。

If the problem recurs, contact GBase Technical Support and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

如果问题再次出现，请联系 GBase 技术支持或 CSM 供应商，并提供以下信息：客户端和数据库服务器的 CSS 配置文件和 sqlhosts 信息。

-5010 CSM: internal processing error.

A CSM (Communications Support Module), in the database server or in the client, detected an internal processing error and is incapable of self-diagnosing it to provide additional information. This error can occur only during use of a CSM and normally represents an internal processing error, but could be caused by an undetected protocol error.

数据库服务器或客户端中的 CSM（通信支持模块）检测到内部处理错误，无法自行诊断和提供附加信息。此错误只能在使用 CSM 期间发生，并且通常表示内部处理错误，但可能是由未检测到的协议错误引起的。

If this error occurs during context setup (that is, at connection time),the connection establishment fails. If this error occurs after establishment of the connection, the connection is dropped.

如果在上下文设置过程中（即连接时）发生此错误，则连接建立失败。如果在建立连接后发生此错误，则连接将被删除。

Contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

请联系 GBase 技术支持或 CSM 供应商，并提供以下信息：客户端和数据库服务器的 CSS 配置文件和 sqlhosts 信息。

-5011 CSM: protocol error.

A CSM (Communications Support Module), in the database server or in the client, received a message that is not consistent with the CSM's protocol formats, with its internal state, or with both. The usual cause of this error is an internal message inconsistency, which indicates the receipt of a protocol data unit with an unknown format. This error can occur only during use of a CSM, and the cause can be a communications error, the use of incompatible versions of the CSM in the client and the database server, or inconsistent configurations of the client and database server CSMs.

在数据库服务器或客户端中，CSM (通信支持模块)接收到的消息与 CSM 的协议格式、内部状态或两者都不一致。造成此错误的通常原因是内部消息不一致，这表示接收到了格式未知的协议数据单元。此错误只能在使用 CSM 时发生，其原因可能是通信错误、客户端和数据库服务器中使用不兼容版本的 CSM 或客户端和数据库服务器 CSMS 的配置不一致。

If this error occurs during context setup (that is, at connection time),the connection establishment fails. If this error occurs after establishment of the connection, the connection is dropped.

如果在上下文设置过程中（即连接时）发生此错误，则连接建立失败。

如果在建立连接后发生此错误，则连接将被丢弃。

Make sure that the release levels of the CSMs types match, and the configurations of client and database server CSMs match. If the problem recurs,contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

确保 CSM 类型的发行版本与客户端和数据库服务器 CSM 的配置匹配。

如果问题再次出现，请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件和用于客户端和数据库服务器的 sqlhost 信息。

-5012 CSM: received message of unexpected type.

A CSM (Communications Support Module), in the database server or in the client, received a message with a type that is inconsistent with the protocol formats and/or internal state. This message is more specific than message -5011 because in this case the protocol data unit that is internally consistent might be carrying a message type that the receiver cannot handle. This error can occur only if a CSM is used. It can be caused by a communications error, by the use of incompatible versions of the CSM in the client and the database server, or by inconsistent configurations of the client and database server CSMs.

CSM（通信支持模块）在数据库服务器或客户端中接收到与协议格式和/或内部状态不一致的类型的消息。此消息比消息 5011 更具体，因为在这种情况下，内部一致的协议数据单元可能承载了接收方无法处理的消息类型。只有在使用 CSM 时才会发生此错误。它可能是由通信错误引起，客户端和数据库服务器中使用不兼容版本的 CSM 或客户端和数据库服务器 CSMS 的配置不一致。

If this error occurs during context setup (that is, at connection time),The connection establishment fails. If this error occurs after Establishment of the connection, the connection is dropped.

如果在上下文设置过程中（即连接时）发生此错误，则连接建立失败。如果在建立连接后发生此错误，则连接将被删除。

Make sure that the release versions of the CSMs types match, and the configurations of client and database server CSMs match. If the problem recurs,contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

确保 CSM 类型的发行版本与客户端和数据库服务器 CSM 的配置匹配。如果问题再次出现，请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件和用于客户端和数据库服务器的 sqlhost 信息。

-5013 CSM: cannot obtain credential: authentication error.

A CSM (Communications Support Module), in the database server or in the client, cannot obtain a credential to proceed in an authentication exchange. For example, a user did not provide a password, or a credential request to an external authentication service returned an error. This error can only occur during context setup (that is, at connection time).

数据库服务器或客户端中的 CSM（通信支持模块）无法获得在身份验证交换中进行的凭据。

例如，用户没有提供密码，也没有向外部身份验证服务提供凭据请求返回错误。此错误只能在上下文设置期间(即连接时)发生。

The connection establishment fails.

连接建立失败。

When a CSM is configured to require a password for authentication, a valid password must be provided. Do not configure the database server to use CSM in such a way that password input is required when you first bring up the database server. Bring the database server up and let it build system tables. Bring the database server down, and reconfigure it to use the CSM as you desire.

当 CSM 被配置为需要密码进行身份验证时，必须提供有效的密码。不要将数据库服务器配置为使用 CSM 时，在第一次打开数据库服务器时需要输入密码。启动数据库服务器，让它构建系统表。关闭数据库服务器，并根据需要重新配置它以使用 CSM。

Provide the password credential, or perform the operations that the external authentication service provider requires in advance (for example, Kerberos klogin).

提供密码凭证，或提前执行外部认证服务提供商要求的操作（例如，Kerberos klogin）。

-5030 CSM: crypto library error: .

A CSM (Communications Support Module), in the database server or in the client, received an error indication from its cryptographic service provider (or crypto library). This error can occur only during use of a CSM and normally represents an internal processing error, but an undetected protocol error could cause this error as well. Additional text, crypto-library return codes, or both might follow the error message.

在数据库服务器或客户端中，CSM (通信支持模块)从其密码服务提供者(或密码库)接收错误指示。此错误只能在使用 CSM 时发生，并且通常表示内部处理错误，但未检测到的协议错误也可能导致此错误。其他文本、密码库返回代码，或者两者都可能出现错误消息。

If this error occurs during context setup (that is, at connection time),the connection establishment fails. If this error occurs after establishment of the connection, the connection is dropped.

如果在上下文设置过程中（即连接时）发生此错误，则连接建立失败。

如果在建立连接后发生此错误，则连接将被删除。

Contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

请联系 GBase 技术支持或 CSM 供应商，并提供以下信息：客户端和数据库服务器的 CSS配置文件和 sqlhosts 信息。

-5848 A row with constraint violations exists.PROBLEM The transaction mode setting for constraints cannot be changed because there is a row with constraint violations, possibly due to deferred constraints.

不能更改约束的事务模式设置，因为有可能是由于延迟约束而出现了与约束冲突的行。

-5849 The sub-query flattening settings for the query plan and the current value of NO_SUBQF environment variable do not match.

.PROBLEM The query plan was created with a different value of the NO_SUBQF environment variable than the current value of the NO_SUBQF environment variable.

创建查询计划时，NO_SUBQF 环境变量的值与 NO_SUBQF 环境变量的当前值不同。

.ACTION Change the value of the NO_SUBQF environment variable or run UPDATE STATISTICS to recreate the routine query plan.

更改 NO_SUBQF 环境变量的值或运行 UPDATE STATISTICS 以重新创建常规查询计划。

-5851 Invalid value specified to SUBSTRING function.

The length argument specified to the SUBSTRING function cannot have a negative value.

指定给 SUBSTRING 函数的长度参数不能具有负值。

-5852 Invalid date.

One of the arguments specified to the function must be a DATETIME type.

Check the values of the arguments that you are passing to the function.

函数指定的参数之一必须是 DATETIME 类型。请检查要传递给该函数的参数的值。

-5853 The format element: (element_name) does not have an equivalent in GBase 8s.

The format specified is not supported and therefore cannot be converted to an GBase 8s format.

指定的格式不受支持，因此不能转换为 GBase 8s 格式。

-5854 Unrecognized format element: (element_name).

The format element specified is unrecognized. It is probably not a legal Oracle format element.

指定的格式元素不可识别。它可能不是一个合法的 Oracle 格式元素。

-5855 The target string is not long enough to contain the converted format.

The target string is not long enough to contain the converted format. You need to allocate more space for the target string.

目标字符串的长度不足以包含转换的格式。您需要为目标字符串分配更多的空间。

-5856 You specified invalid precision for FLOAT.

Maximum precision value for FLOAT data type must be between 1 and 16.

Note: SQL ignores any specified precision.

FLOAT 数据类型的最大精度值必须在 1 到 16 之间。

注意：SQL 忽略任何指定的精度。

-5857 Using NULL in the RANGE or STEP expression is not possible.

A RANGE or STEP expression included NULL.

RANGE 或 STEP 表达式包括空。

Replace NULL with another value in the RANGE or STEP expression and retry the statement.

用RANGE 或 STEP 表达式中的另一个值替换空，然后重试该语句。

-7000 Error error-number from the optical subsystem. Consult your appropriate subsystem manual.

Check the error number in the documentation for the subsystem that you are using.

检查您正在使用的子系统的文档中的错误号。

-7202 Database was created without NLS functionality.

You attempted to create an NCHAR (or NVARCHAR) column or declare an NCHAR (or NVARCHAR) variable, in a non-NLS database.

您试图在非 NLS 数据库中创建 NCHAR（或 NVARCHAR）列或声明 NCHAR（或 NVARCHAR）变量。

-7203 DBNLS is not set or LC_COLLATE must be category-value.

You might receive this message when you try to access an external database that has a different locale than the current database. In order to use this NLS database, you must set the DBNLS environment variable to 1 or 2 and the LC_COLLATE environment variable to the specified category-value.

当您尝试访问与当前数据库具有不同区域设置的外部数据库时，可能会收到此消息。要使用此 NLS 数据库，必须将 DBNLS 环境变量设置为 1 或 2，并将 LC_COLLATE 环境变量设置为指定的类别值。

-7204 LANG or LC_COLLATE environment variable is invalid.

Either the LANG or the LC_COLLATE environment variable setting is invalid. Set either or both variables to the values that your system supports.

LANG 或 LC_COLLATE 环境变量设置无效。将其中一个或两个变量设置为系统支持的值。

-7205 DBNLS is not set or LC_CTYPE must be set to category-value.

You might receive this message when you try to access an external database that has a different locale than the current database. In order to access this NLS database, you must set the DBNLS environment variable to 1 or 2 and the LC_CTYPE environment variable to the specified category-value.

当您尝试访问与当前数据库具有不同区域设置的外部数据库时，可能会收到此消息。为了访问这个 NLS 数据库，必须将 DBNLS 环境变量设置为 1 或 2，并将 LC_CTYPE 环境变量设置为指定的类别值。

-7206 LANG or LC_CTYPE environment variable is invalid.

Either the LANG or the LC_CTYPE environment variable setting is invalid. Set either or both variables to the values that your system supports.

LANG 或 LC_CTYPE 环境变量设置无效。将其中一个或两个变量设置为系统支持的值。

-7207 LANG or LC_MONETARY environment variable is invalid.

Either the LANG or the LC_MONETARY environment variable setting is invalid. Set either or both variables to the values that your system supports.

LANG 或 LC_MONETARY 环境变量设置无效。将其中一个或两个变量设置为系统支持的值。

-7208 LANG or LC_NUMERIC environment variable is invalid.

Either the LANG or the LC_NUMERIC environment variable setting is invalid. Set either or both variables to the values that your system supports.

LANG 或 LC_NUMERIC 环境变量设置无效。将其中一个或两个变量设置为系统支持的值。

-7209 LANG or LC_TIME environment variable is invalid.

Either the LANG or the LC_TIME environment variable setting is invalid.

Set either or both variables to the values that your system supports.

LANG 或 LC_TIME 环境变量设置无效。将其中一个或两个变量设置为系统支持的值。

-7210 This server does not have NLS capability.

You tried to access an NLS database from a non-NLS-ready database server. This database server does not support NLS. Contact GBase for a version that does support NLS.

您尝试从非 NLS 就绪数据库服务器访问 NLS 数据库。此数据库服务器不支持 NLS 。

请与 GBase 联系，以获得支持 NLS 的版本。

-7211 Cannot reference an external NLS database.

If your current database is not an NLS database, you cannot access an NLS database on another database server or on the same database server. However, if the NLS environment variables are set correctly,you can drop an external NLS database even if your current database is not an NLS database.

如果当前数据库不是 NLS 数据库，则无法访问其他数据库服务器或同一数据库服务器上的 NLS 数据库。但是，如果 NLS 环境变量设置正确，即使当前数据库不是 NLS 数据库，也可以删除外部 NLS 数据库。

-7350 Attempt to update a stale version of a row An attempt was made to update a stale copy of a row. This caused an optimistic concurrancy failure.

尝试更新行的陈旧副本。这导致乐观并发失败。

This error can occur when using updatable secondary and the current version of the row has not yet been replicated to the secondary on which the client application is connected.

当使用可更新的辅助程序且该行的当前版本尚未复制到连接客户端应用程序的辅助版本时，可能会发生此错误。

This error code is also returned when table schema at secondary server doesn't match with the table schema at primary server.

当辅助服务器上的表架构与主服务器上的表架构不匹配时，也会返回此错误代码。

-7351 Connection between secondary and primary has been lost The connection between the secondary and the primary has been lost. This will prevent the updates on secondary until connectivity has been reestablished.

次级和主级之间的连接已丢失。这将防止在重新建立连接之前对辅助设备进行更新。

-7352 Operation can not be run on secondary node There was an attempt to run an operation on a secondary node which can only be successfully run on the primary. You will need to perform the operation on the current primary node有人试图在辅助节点上运行一个只能在主节点上成功运行的操作。

-7353 The transaction cannot continue on the new primary server.

The transaction was started at a secondary server. While processing the transaction, the original primary server to which the secondary server was connected went off-line and another server became the new primary server.

There was an error recreating the transaction state at the new primary server.

事务在辅助服务器上启动。在处理事务时，连接到辅助服务器的原始主服务器脱机，另一台服务器成为新的主服务器。在新的主服务器上重新创建事务状态时出错。

-7400 Invalid API argument .

Verify the arguments to the DataBlade API calls.

验证 DataBlade API 调用的参数。

-7401 Invalid API usage .

A DataBlade API call used an invalid argument or was made in an incorrect context. The value of one or more arguments might be invalid, the sequence of DataBlade API calls might be incorrect, or the call might have been made from within a callback function where the call is invalid.

DataBlade API 调用使用无效的参数或在不正确的上下文中进行。一个或多个参数的值可能无效，DataBlade API 调用的序列可能不正确，或者调用可能是在调用无效的回调函数中进行的。

Check that the values of individual arguments are valid in the API call and that the combination of all argument values is correct. Also check the sequence of your DataBlade API calls. If the API call named in the error message is made from within a callback function, move the call or remove it.

检查各个参数的值在 API 调用中是否有效，并且所有参数值的组合是否正确。还检查DataBlade API 调用的顺序。如果错误消息中命名的 API 调用是在回调函数中进行的，则移动或删除该调用。

-7402 Internal error.

If this error occurs, note all circumstances and contact GBase Technical Support.

如果发生此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-7403 File protocol error. Expected message_packet_name.

This is an internal error. If it recurs, note all circumstances and contact GBase Technical Support.

这是内部错误。如果再次发生，请注意所有情况，并与 GBase 技术支持部门联系。

-7404 File protocol error. Reported by client.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果此错误再次发生，请注意所有情况，并与 GBase 技术支持部门联系。

-7406 Operation operation_name not supported outside execution.

This is an internal database server error. If it recurs, note all circumstances and contact GBase Technical Support.

这是内部错误。如果再次发生，请注意所有情况，并与 GBase 技术支持部门联系。

-7411 Error loading locale object for client locale.

Probably an error occurred either while reading a registry or reading a conversion object file. Locale file details are missing from the registry file. Make sure the locale you are trying to load is compatible with the locale that was specified when the database was created.

可能在读取注册表或读取转换对象文件时发生错误。注册表文件中缺少区域设置文件详细信息。确保要加载的区域设置与创建数据库时指定的区域设置兼容。

-7412 Error loading code-set conversion object for converting to client codeset.

-7413 Error loading locale object for server processing locale.

-7420 Argument argument_name is invalid.

Verify the arguments to the DataBlade API calls.

验证 DataBlade API 调用的参数。

-7421 The specified column position is invalid.

Check the arguments to the DataBlade API calls that require column numbers. DataBlade API calls use column numbers 0 to number of columns minus one.

检查需要列号的 DataBlade API 调用的参数。DataBlade API 调用使用列号 0 至列号减1。

-7422 Cannot issue SAPI function in a secondary PDQ thread. You need to define the user-defined routine as non-parallelizable.

A user-defined routine that was defined as parallelizable has issued a SAPI function that is not PDQ thread-safe. Only nonparallelizable user-defined routines can call such a SAPI function.

定义为可并行化的用户定义例程发出了一个不是 PDQ 线程安全的 SAPI 函数。只有不可并行的用户定义例程才能调用这样的 SAPI 函数。

Drop the routine and redefine it as nonparallelizable. To define a routine as nonparallelizable, reissue the CREATE FUNCTION, CREATE PROCEDURE, or CREATE ROUTINE statement without the WITH (PARALLELIZABLE) class. Or you can use the following statement to make a routine nonparallelizable:删除例程并将其重新定义为不可并行。若要将例程定义为不可并行性，请重新发出CREATE FUNCTION、CREATE PROCEDURE 或 CREATE ROUTINE 语句，而不使用 WITH(PARALLELIZABLE) 类。或者可以使用以下语句使例程不可并行：ALTER ROUTINE routine-name WITH (DROP PARALLELIZABLE)-7423 An invalid argument is specified. Either the return type buffer is empty or the length of the buffer is not valid.

Verify arguments to DataBlade API calls.

验证 DataBlade API 调用的参数。

-7424 A Cursor can only be defined for a prepared SELECT statement.

Prepare your SELECT statement before you define the cursor.

在定义游标之前准备好 SELECT 语句。

-7425 Invalid statement handle.

Verify arguments to DataBlade API calls. The statement handle used was invalid or improperly modified.

验证 DataBlade API 调用的参数。使用的语句句柄无效或修改不当。

-7426 There is no active query on this connection.

Verify the logic in the user-defined routine. You cannot retrieve or query results without an active query.

验证用户定义例程中的逻辑。如果没有活动查询，则无法检索或查询结果。

-7427 Argument is not a valid argument_name.

An argument to a DataBlade API is invalid. Verify the arguments used in each call to the DataBlade API.

DataBlade API 的参数无效。验证每次调用 DataBlade API 时使用的参数。

-7428 Saveset is corrupted.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-7429 Out of memory allocating save set.

Check with your system administrator or database administrator.

与系统管理员或数据库管理员进行检查。

-7430 Out of memory allocating save set element.

Check with your system administrator or database administrator.

与系统管理员或数据库管理员进行检查。

-7431 Invalid save set type type_name.

Verify that your type name is spelled correctly. If it is a user-defined type, ensure that it has been defined correctly in your database.

验证您的类型名拼写正确。如果它是用户定义的类型，请确保它已在数据库中正确定义。

-7432 Command is not yet complete.

Feature is not yet implemented. Review your release notes.

特性尚未实现。回顾您的发版说明。

-7433 Command not a DML.

A SELECT, INSERT, UPDATE or DELETE statement was expected. Review the SQL statement in the user-defined routine.

需要 SELECT、INSERT、UPDATE 或 DELETE 语句。检查用户定义例程中的 SQL 语句。

-7434 Parameter information not supported for SELECTS.

Feature is not implemented.

特性未实现。

-7435 This statement references a table that is used in the parent queries.

Subqueries or queries invoked by nested user-defined routines cannot reference tables used by parent queries or calling user-defined routines. Restructure your query to avoid this situation.

子查询或嵌套用户定义例程调用的查询不能引用父查询或调用用户定义例程使用的表。重组查询以避免这种情况。

-7436 Inappropriate statement for parameter information.

You requested parameter information calls for a non-DML statement.

Parameter information can be obtained only for DML statements.

您请求了非 DML 语句的参数信息调用。只能为 DML 语句获取参数信息。

-7438 Unsupported data type.

The data type you are using is not supported. Verify the type definition.

不支持所使用的数据类型。验证类型定义。

-7442 The statement must be opened before this operation can be performed.

An attempt was made to fetch or close a prepared statement that is not open. Ensure that a mi_open_prepared_statement call was successfully completed prior to calling mi_fetch_statement or mi_close_statement.

试图获取或关闭未打开的已准备语句。确保在调用 mi_fetch_statement 或mi_close_statement 之前成功地完成了 mi_open_prepared_statement 调用。

-7443 The statement must be closed before it can be reopened or executed.

An attempt was made to open or execute a prepared statement that is already open. A statement must be closed before it can be reopened with a mi_open_prepared_statement call or executed with a mi_exec_prepare_statement call.

尝试打开或执行已打开的准备语句。必须关闭语句，然后才能使用mi_open_prepared_statement 调用重新打开该语句，或者使用mi_exec_prepare_statement 调用执行该语句。

-7469 Calling %s is not supported from compare function.

Compare() functions cannot call strings.

Compare() 函数不能调用字符串。

-7470 Invalid connection connection_handle.

Verify arguments to DataBlade API calls. The connection handle used was NULL, not opened, invalid, or improperly modified.

验证 DataBlade API 调用的参数。使用的连接句柄为空、未打开、无效或修改不当。

-7471 Internal error: Invalid user-defined routine context/state (state)If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-7472 Out of memory allocating internal user-defined routine connection state.

Check disk space on your computer. For more help, call your system administrator or database administrator. If these checks do not resolve the problem, and this error recurs, note all circumstances and contact GBase Technical Support.

检查计算机上的磁盘空间。有关更多帮助，请致电系统管理员或数据库管理员。如果这些检查不能解决问题，并且出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-7473 Internal error: Bad install of user-defined routine-language manager callback.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-7474 Out of memory allocating server user-defined routine connection.

Check disk space on your computer. For more help call your system administrator or database administrator. If this error recurs,note all circumstances and contact GBase Technical Support.

-7475 Cannot close a connection from outside of its own parent statement.

Check the logic in your user-defined routine. You must open and close connections within the scope of the user-defined routine.

检查用户定义例程中的逻辑。必须在用户定义例程的范围内打开和关闭连接。

-7476 Cannot close a session-duration connection within an UDR.

A session-duration connection has the scope of the session to which it is associated. Such a connection cannot be closed within an UDR. See the GBase 8s DataBlade API Programmer's Guide and the GBase 8s DataBlade API Function Reference for further details.

会话持续时间连接具有与其关联的会话的作用域。这样的连接不能在 UDR 中关闭。有关详细信息，请参阅 GBase 8s DataBlade API 程序员指南和 GBase 8s DataBlade API 函数参考。

-7490 Cannot open trace output file file_name.

Check permissions on the file and its directory. For more help, call your system administrator or database administrator.

检查文件及其目录的权限。有关更多帮助，请致电系统管理员或数据库管理员。

-7491 Cannot read trace system table table_name.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-7492 Write to trace output file failed.

Check permissions on the file and its directory. Check disk space on your computer. For more help, call your system administrator or database administrator. If this error recurs, note all circumstances and contact GBase Technical Support.

检查文件及其目录的权限。检查计算机上的磁盘空间。有关更多帮助，请致电系统管理员或数据库管理员。如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-7493 Cannot create internal map to trace classes.

Check disk space on your computer. For more help call your system administrator or database administrator. If this error recurs,note all circumstances and contact GBase Technical Support.

检查计算机上的磁盘空间。有关更多帮助，请致电系统管理员或数据库管理员。如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-7494 Cannot create internal trace message list.

Check disk space on your computer. For more help call your system administrator or database administrator. If this error recurs,note all circumstances and contact GBase Technical Support.

检查计算机上的磁盘空间。有关更多帮助，请致电系统管理员或数据库管理员。如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-7500 Invalid multibyte character in syserrors catalog table for sqlstate SQLSTATE_value.

An invalid multibyte character has entered the syserrors catalog table. Possibly, the syserrors.locale is not the actual locale used for syserrors.message. This table is normally populated with DataBlade messages or possibly messages from user-defined routines.

一个无效的多字节字符已进入 syserror 目录表。可能，syserrors.locale 不是用于syserrors.Message 的实际区域设置。此表通常由 DataBlade 消息或用户定义例程中的消息填充。

-7503 The BLOB or CLOB data size provided differs from the client file size.

The size of the BLOB or CLOB data that was provided in a load command is not the same as the actual size of the smart large object client file.

Verify that the data size provided in the load command is correct or check if the smart large object client file is incomplete or corrupted.

LOAD 命令中提供的 BLOB 或 CLOB 数据的大小与智能大对象客户端文件的实际大小不相同。请验证 LOAD 命令中提供的数据大小是否正确，或者检查智能大对象客户端文件是否不完整或损坏。

-7510 API use not valid in callback ().

You cannot call this routine in the callback.

您不能在回调中调用此例程。

For information on the use of callbacks, see the "DataBlade API Programmer's Manual."有关回调使用的信息，请参阅“DataBlade API 程序员手册”。

-7514 MI_EVENT_END_XACT callback can only be registered inside a transaction.

Move the end-of-transaction callback inside your transaction.

在事务内部移动事务处理的端到端回叫。

-7520 Argument argument_name is NULL.

Verify arguments to DataBlade API calls. NULL was passed but not expected.

验证 DataBlade API 调用的参数。NULL 被传递，但没有预料到。

-7521 GLS internal error encountered within API: error_code.

Verify your CLIENT_LOCALE. If this error recurs, note all circumstances and contact GBase Technical Support.

验证您的 CLIENT_LOCALE。如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-7522 Incomplete locale information for conversion between client and server formats Verify your CLIENT_LOCALE. If this error recurs, note all circumstances and contact GBase Technical Support.

验证您的 CLIENT_LOCALE 。如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-7530 Missing parenthesis in the signature specified for user-defined routine lookup.

Verify signature for routine specified for fastpath execution.

验证 fastpath 执行指定的例程的签名。

-7531 Invalid user defined routine type: must be function or procedure.

Specified user-defined routine must be a function or a procedure.

Verify name and definition of routine to be called.

指定的用户定义例程必须是函数或过程。验证要调用的例程的名称和定义。

-7532 Error converting type in string format to id format Verify spelling and definition of types used in the routine signature.

验证例程签名中使用的类型的拼写和定义。

-7533 Error in user-defined-routine lookup: Specified user-defined routine not found.

Verify spelling and definition of user-defined routine.

验证用户定义例程的拼写和定义。

-7534 Error initializing user-defined-routine sequence for execution.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-7535 Invalid MI_FPARAM pointer returned.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-7536 Error unlinking function descriptor from connection, not previously linked.

Verify arguments to Blade API calls. The connection handle used was NULL, not opened, invalid or improperly modified.

验证 Blade API 调用的参数。使用的连接句柄为空，未打开，无效或修改不当。

-7537 Error setting default arguments for execution of user-defined routine.

Review arguments to user-defined routine.

查看用户定义例程的参数。

-7538 Error converting default arguments to C style values.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-7539 Error performing fastpath execution of UDR from API.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-7540 Routine's return value ID is out of range.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-7542 Cast user-defined-routine lookup failed.

Verify spelling and definition of types used in the routine signature.

If this error recurs, note all circumstances and contact GBase Technical Support.

验证例程签名中使用的类型的拼写和定义。如果再次出现此错误，请注意所有情况，并与GBase 技术支持部门联系。

-7546 Unknown routine type , routine type must be one of 'f'or 'p'.

You used an invalid routine type when using mi_create_signature() to create a function or procedure.

在使用 mi_create_signature() 创建函数或存储过程时，使用了无效的例程类型。

Specify either 'f' or 'p' as the routine type.

指定“f”或“p”作为例程类型。

-7547 Routine name is missing in call to mi_create_signature.

Verify that you included all required parameters in your call to the mi_create_signature() function. For the complete syntax of mi_create_signature(), refer to the DataBlade API Function Reference.

验证在调用 mi_create_signature() 函数时是否包含了所有必需的参数。有关mi_create_signature() 的完整语法，请参考 DataBlade API 函数引用。

-7549 Cannot use mi_funcmap_get on remote routines.

This routine must be used with functions that are in the local database.

此例程必须与本地数据库中的函数一起使用。

Remove references to routines on remote databases from mi_funcmap_get().

从 mi_functionmap_get() 中删除对远程数据库上例程的引用。

-7580 Invalid attempt to call routine: this routine may only be called from an am_check routine.

You tried to call the specified routine from a UDR other than a VTI/VII am_check routine. Outside of am_check routines, use mi_db_error_raise to report messages and errors.

您尝试从 UDR 调用指定的例程，而不是从 VTI/VII am_check 例程调用。在 am_check例程之外，使用 mi_db_error_raise 报告消息和错误。

-7590 Cannot read past the end of stream marker.

After a call to mi_stream_eof() would have returned MI_TRUE, indicating the end of the file or stream, another read operation was attempted. You cannot read past the end-of-stream marker.

调用 mi_stream_eof() 将返回 MI_TRUE，指示文件或流的结束后，尝试进行另一次读取操作。您不能通过流结束标记读取。

Once the mi_stream_eof() function returns MI_TRUE, terminate read operations to avoid this error.

一旦 mi_stream_eof() 函数返回 MI_TRUE，则终止读取操作以避免此错误。

-7591 This is a generic mi_stream failure.

An unspecified mi_stream error occurred. The cause is not clearly known.

发生了未指定的mi_stream错误。原因尚不清楚。

Check the stream-type documentation for any details.

有关任何细节，请查看流类型文档。

-7592 The mi_stream function being called is not implemented.

An attempt was made to execute an unimplemented mi_stream operation, such as mi_stream_read(), mi_stream_write(), or mi_stream_seek(). Not all mi_stream types support all mi_stream functions.

尝试执行未实现的 mi_stream 操作，例如 mi_stream_read()、mi_stream_write()或 mi_stream_find()。并非所有 mi_stream 类型都支持所有 mi_stream 函数。

Check the functional definition for the stream being used to ensure that the function that returns this status has been implemented.

请检查用于确保返回此状态的函数已经实现的流的函数定义。

-7593 During an mi_stream operation a Send side failure has occurred.

During an mi_stream operation, the send side of a data transfer encountered problems, and the data transfer failed. This status is usually associated with Enterprise Replication (ER) operations.

在 mi_stream 操作期间，数据传输的发送端遇到问题，数据传输失败。此状态通常与企业复制（Enterprise Replication，ER）操作相关联。

Check the log files for any additional information.

检查日志文件以获得任何其他信息。

-7594 During an mi_stream operation a Receive side failure has occurred.

During an mi_stream operation, the receive side of a data transfer encountered problems, and the data transfer failed. This status is usually associated with Enterprise Replication (ER) operations.

在 mi_stream 操作期间，数据传输的接收端遇到问题，数据传输失败。此状态通常与企业复制（Enterprise Replication，ER）操作相关联。

-7595 An error has occurred during the conversion or manipulation of the ifx_int8 involved with an mi_stream operation.

A conversion operation for ifx_int8 values failed.

ifx_int8 值的转换操作失败。

Check the values being used to verify that they match the types required and are set with valid data.

请检查用于验证它们是否符合所需类型并使用有效数据设置的值。

-7596 An mi_stream seek has occurred using a bad whence value.

A call to mi_stream_seek() received a seek parameter that is in error.

对 mi_stream_seek() 的调用接收到错误的查找参数。

Use one of the following values:使用下列值之一：MI_LO_SEEK_SET or SEEK_SET MI_LO_SEEK_CUR or SEEK_CUR MI_LO_SEEK_END or SEEK_END-7597 An attempt to determine the shared library module ID for an mi_stream operation has failed.

An mi_stream function address lookup failed. The shared-library module handle is set to NULL to indicate that no shared library is currently loaded.

mi_stream 函数地址查找失败。共享库模块句柄设置为 NULL，以指示当前没有加载共享库。

Check the log files for any errors that might have occurred when an attempt was made to load the library. Common load problems include an incorrect library path and a library that does not exist at the designated location.

检查日志文件，以查看在尝试加载库时可能发生的任何错误。常见的加载问题包括不正确的库路径和指定位置不存在的库。

-7598 The mi_stream function symbol lookup in a shared library failed.

An mi_stream function symbol name was not found in the given shared-library module.

在给定的共享库模块中找不到 mi_stream 函数符号名。

Check that the spelling of the function symbol name is correct.

请检查函数符号名的拼写是否正确。

-7599 The mi_stream function address lookup in a shared library failed.

An mi_stream function address could not be resolved using the function name provided. The function handle could not be mapped to a real executable address.

无法使用提供的函数名解析 mi_stream 函数地址。函数句柄无法映射到实际的可执行地址。

Check the log files for any errors that might have occurred when an attempt was made to load the library. Check the spelling of the function name.

请检查日志文件，以查看在尝试加载库时可能发生的任何错误。检查函数名的拼写。

-7601 Bad cursor action: Subquery collections only support cursor action MI_CURSOR_NEXT.

A cursor action other than MI_CURSOR_NEXT was used on a subquery collection.

子查询集合中使用了一个游标操作，而不是 MI_CURSOR_NEXT 。

Remove any invalid cursor actions. For subquery collections, use only the MI_CURSOR_NEXT cursor action or open the subquery collection without the flags MI_COLL_NOSCROLL and MI_COLL_READONLY.

请删除所有无效的游标操作。对于子查询集合，只使用 MI_CURSOR_NEXT 游标操作或打开子查询集合，而不使用 MI_COLL_NOSCROLL 和 MI_COLL_READONLY 标志。

-7602 Internal error: Invalid field count for a row.

This is an internal error.

这是一个内部错误。

If it recurs, note all circumstances and contact GBase Technical Support.

如果它再次出现，请注意所有情况，并与 GBase 技术支持部门联系。

-7607 Invalid row literal value.

A row literal should be well-formed with respect to its syntax and the type of objects contained in the literal. For a description of the syntax and semantics of Literal Row, refer to the GBase 8s Guide to SQL: Syntax.

行文字应该在语法和包含在文本中的对象类型方面形成良好的格式。有关 Literal Row的语法和语义的描述，请参阅 GBase 8s SQL 指南：语法。

-7610 Invalid collection literal value.

Your collection value is not well-formed.

您的集合值格式不正确。

See the documentation for a description of the construction of collection literal values.

有关集合文字值的构造的说明，请参阅文档。

-8001 The number of newlines specified for TOP MARGIN, FIRST PAGE HEADER(PAGE HEADER), PAGE TRAILER, and BOTTOM MARGIN must leave enough room on the page for the printing of the ON EVERY RECORD clause.

The total number of lines that are defined for all the above statements exceeds the page length. Check that you entered the desired number of lines in each statement in the OUTPUT section and in the header and trailer specifications of the FORMAT section.

为所有上述语句定义的总行数超过页长。检查在 OUTPUT 部分中的每个语句以及 FORMAT部分的标头和拖尾中输入了所需的行数。

-8002 The ACE report specification is too complex or large to be properly compiled. The number of instructions needed to implement this specification is greater than the space that is allocated in the instruction tables for the compiler.

Reduce the size of the report. Because you cannot divide a report into parts to compile separately, you must find a way to simplify the report.

缩小报告的大小。因为不能将报表分成要单独编译的部分，所以必须找到简化报表的方法。

-8003 A SMALLINTEGER constant may not be larger than 32767.

The allowable range of values for a SMALLINT constant is -32,767 through 32,767. Only whole numbers are allowed, with only digit characters.

SMALLINT 常数的允许值范围为 -32，767 至 32，767。只允许整数，只有数字字符。

-8004 Illegal FLOAT constant.

The FLOAT constant is not written correctly. The exponent might be too small or too large (the allowable range of exponents depends on your computer and operating system but is the same as your C compiler allows for the DOUBLE data type), or incorrect punctuation or a nondigit character other than e might be present.

浮点常量写得不正确。指数可能太小或太大（指数的允许范围取决于计算机和操作系统，但与 C 编译器允许的 DOUBLE 数据类型相同），或者可能存在不正确的标点符号或 e以外的非数字字符。

-8005 Too many user variables, parameters, or functions have been defined.

You cannot define any more than number in an ACE specification.

The total number of identifiers that are defined for ASCII fields,parameters, and variables cannot exceed the number that is shown. You must simplify the report.

为 ASCII 字段、参数和变量定义的标识符总数不能超过所显示的数目。您必须简化报告。

-8006 A quoted string may not exceed 80 characters in length.

You must reduce the quoted string to a maximum of 80 characters. In a PRINT statement, simply divide the string into shorter parts, and separate the parts with commas.

必须将引用的字符串减少到最多 80 个字符。在 PRINT 语句中，只需将字符串划分为较短的部分，并用逗号分隔这些部分。

-8007 There is an unmatched quote in a quoted string.

This line of the report specification contains an odd number of quote(") symbols. A quoted string cannot include a new-line character; all quoted strings must be complete in one line. In order to print a longer string, store its parts in variables and list them all in a PRINT statement.

报表规范的这一行包含了奇数的引号(“)符号。引号字符串不能包含新行字符；所有引号字符串必须在一行中完成。为了打印更长的字符串，将其部件存储在变量中，并将它们全部列出在 PRINT 语句中。

-8008 The file filename could not be opened. The operating system was asked to open it for reading.

Check the spelling of the filename. Make sure that the file exists and that your account name has read access to it. If the file is in a directory other than the current directory, you might have to enter a complete pathname.

检查文件名的拼写。确保该文件存在，并且您的账户名具有对它的读取访问权限。如果文件位于当前目录以外的目录中，则可能必须输入完整的路径名。

-8009 A memory allocation error has occurred. The ACE report specification is probably too large.

The ACE compiler could not allocate memory that it needed. Try reducing the size of the report specification.

ACE 编译器无法分配所需的内存。尝试缩小报表规范的大小。

-8010 The file filename could not be opened. The operating system was asked to open it for writing. It is possible that a file by the same name already exists, but the user has no permission to write over it, or, if -o is used,the destination directory does not exist.

Ensure that filename is spelled correctly and that your account name has write access to the directory where it will be stored. (That directory might be the one that the environment variable DBTEMP names.)If a file of that name already exists, either erase it or make sure that your account has write access to it.

确保文件名拼写正确，并且您的账户名对存储它的目录具有写访问权限。（该目录可能是环境变量 DBTEMP 命名的目录。）如果该名称的文件已经存在，请将其删除或确保您的账户对其具有写访问权。

-8011 The user function called name has not yet been defined by the user.

A call was made to a function with the name shown. ACE assumes that it is an external C function. However, external functions must be defined in the DEFINE section of the report using FUNCTION funcname statements,and this name is not defined. If name was intended as the name of an external function, insert a FUNCTION statement for it.

调用一个函数，其名称如图所示。ACE 假定它是一个外部 C 函数。但是，必须使用FUNCTION funcname 语句在报表的 DEFINE 部分中定义外部函数，并且没有定义此名称。

如果名称被用作外部函数的名称，则为其插入一个 FUNCTION 语句。

-8013 An error occurred when an attempt was made to open the listing file filename. Be certain that the user has write permissions in the current directory.

Ensure that your account has write access to the current directory. If a file filename already exists, check that your account has write access to it.

确保您的账户对当前目录具有写访问权限。如果文件名已经存在，请检查您的账户是否有写访问权。

-8014 Usage: SACEPREP [-q][-o output_directory] input_filename (etc.)Something in the command line that you entered was not acceptable to saceprep. Read the message to remind yourself of the syntax of the various options and then retype the command line.

您输入的命令行中的某些内容对于 saceprep 来说是不可接受的。阅读这条消息，提醒自己各种选项的语法，然后重新键入命令行。

-8015 An open comment symbol, {, was found inside an already open comment on line line-number, character char-number. This could be due to a failure to closethe previously opened comment, which was begun on line lnum,character cnum.

You cannot nest comments. Insert a close-comment symbol where appropriate in the report specification.

不能嵌套注释。在报表规范中适当插入一个关闭注释符号。

-8016 A comment has been opened but not closed. The last comment begun was opened on line line-number, character char-number.

Insert a close-comment symbol where appropriate in the report specification.

在报表规范中适当插入一个关闭注释符号。

-8017 An illegal (invisible, control) character has been found on line line-number, character char-number. It has been replaced by a blank in the listing, but it is still in the source (input) file, and should be removed before attempting to compile again.

Using a word-processing editor in document mode instead of text mode,striking nonprinting keys while you are editing the file, or data corruption can introduce illegal characters into files.

使用“文档”模式中的字处理编辑器而不是文本模式，在编辑文件时敲击非打印键，或数据损坏可能会将非法字符导入文件中。

-8018 A grammatical error has been found on line line-number, character char-number. The construct is not understandable in its context.

A syntax error exists in the source file. A keyword might be misspelled or misplaced in the file. Check the spelling of the keyword or the sequence of control blocks within the report-specification file.

源文件中存在语法错误。关键字可能拼写错误或在文件中放置错误。检查关键字的拼写或报表规范文件中控制块的顺序。

-8019 Cannot open temporary file filename for reading of a TEXT column.

For each TEXT column that is selected for the report, ACEGO prepares a temporary file in the directory that the DBTEMP environment variable names. This message indicates that the file was created and loaded with a copy of a TEXT value, but now it cannot be read. Look for operating-system error messages that might give more details. If the error recurs, note all circumstances and contact GBase Technical Support.

对于为报表选择的每个文本列，ACEGO 在 DBTEMP 环境变量名称的目录中准备一个临时文件。此消息表示文件已创建并加载文本值的副本，但现在无法读取。查找可能提供更多详细信息的操作系统错误消息。如果错误再次发生，请注意所有情况，并与 GBase 技术支持部门联系。

-8021 The source file filename cannot be opened. This is probably because the file does not exist.

Check the spelling of filename. Check that the report-specification file exists in your current directory, or if it is in another directory, check that you provided the correct pathname. If this information is correct, verify that your account has read permission on the file.

检查文件名的拼写。检查报表规范文件是否存在于当前目录中，或者如果它位于另一个目录中，则检查是否提供了正确的路径名。如果此信息是正确的，请验证您的账户对该文件具有读取权限。

-8022 This identifier exceeds the maximum length for identifiers, which is 50.

You must devise a shorter identifier.

您必须设计一个较短的标识符。

-8025 The comment close symbol, }, has been found on line line-number,character char-number, even though no comment has been opened.

Unless comment symbols are enclosed in quotes, they must be balanced.

Probably the open-comment symbol was accidentally deleted during editing. Change the file so that comments are properly delimited.

除非注释符号用引号括起来，否则它们必须是平衡的。可能在编辑过程中，打开的注释符号被意外删除了。更改文件，以便正确地分隔注释。

-8030 A typographical error has been found on line line-number, character char-number.

The single character at the location that is shown is not syntactically correct; it cannot be interpreted as part of a report specification.

所显示的位置上的单个字符不是句法上的。它不能被解释为报表规范的一部分。

-8033 The source file name filename exceeds the maximum length of 10.

The form compiler imposes a limit on the length of source-file identifiers. You must rename the file before you use it. In DOS systems, filenames can be a maximum of 8 characters plus a 3-character extension.

表单编译器对源文件标识符的长度施加了限制.在使用该文件之前，必须重命名它。在DOS 系统中，文件名最多可以是 8 个字符加上 3 个字符的扩展。

-8034 An unknown option option was found on the command line.

ACEPREP supports the following command-line options:ACEPREP支持以下命令行选项：* -s to suppress messages* -s 将禁止消息* -o to name an output destination* -o 输出目的地名称* -ansi to test for ANSI compliance* -ansi 测试 ANSI 的符合性ACEGO supports the following command-line options:ACEGO 支持以下命令行选项：* -s to suppress messages* -s 抑制消息* -d to name a database* -d 命名数据库-8051 The LEFT MARGIN must be no less than zero and no greater than the RIGHT MARGIN.

Revise the left and right MARGIN statements in the OUTPUT section to reasonable margin values.

将 OUTPUT 部分中的 MARGIN 语句修改为合理的边距值。

-8052 There is insufficient space in the compiler string table for the storage of CHAR variables.

Reduce the length or number of character variables in the report specification.

减少报表规范中字符变量的长度或数量。

-8053 Neither the PAGE LENGTH, TOP MARGIN, nor BOTTOM MARGIN is allowed to be less than zero.

Revise the statements in the OUTPUT section to have reasonable values.

修改 OUTPUT 部分中的语句，使其具有合理的值。

-8054 The string string does not fit into remaining space in the compiler's string table.

Reduce the length or number of strings in the report specification.

Identical strings are stored only once.

减少报表规范中字符串的长度或数目。相同的字符串只存储一次。

-8055 This constant causes the constant table in ACEPREP to overflow.

Reduce the number of numeric constants that the report-specification file uses.

减少报表规范文件使用的数值常量。

-8056 Skipping lines inside of WHILE or FOR loops is not allowed within PAGE HEADER or TRAILER.

ACEPREP needs to determine how many lines of space to devote to the page header and trailer (otherwise, it does not know how many detail rows to allow on the page). It cannot predict how many times a loop will be executed, so it has to forbid the use of SKIP statements in loops in these sections.

ACEPREP 需要确定用于页面标题和预告片的多少行空间（否则，它不知道页面上允许多少详细行）。它无法预测一个循环将执行多少次，因此必须禁止在这些部分的循环中使用SKIP 语句。

-8057 Only user variables of type CHARACTER may be subscripted or have lists in the LET statement.

You can use a subscript (two numbers in square brackets, used to extract a substring of characters) with names of character variables only. In a LET statement, you can assign multiple strings, separated by commas, to a character variable only. Variables of other types can receive only single values.

您可以使用下标（方括号中的两个数字，用于提取字符的子字符串），其中只包含字符变量的名称。在 LET 语句中，可以将多个字符串（用逗号分隔）分配给字符变量。其他类型的变量只能接收单个值。

-8058 The ASCII field field-name has already been defined.

A field name can be defined only once. Field names must be unique in the DEFINE section, that is, a name cannot be used for both a PARAM and a field.

字段名只能定义一次。字段名在 DEFINE 部分必须是唯一的，也就是说，名称不能同时用于 PARAM 和字段。

-8059 The limit for IF statement nesting has been exceeded. There are too many IF statements within IF statements for ACE to properly compile this specification.

You have exceeded the maximum levels of nested IF statements. You must simplify the logic of the report.

您已经超过了嵌套 IF 语句的最大级别。您必须简化报告的逻辑。

-8060 An end-of-file has been prematurely found in the report specification.

ACEPREP encountered the end of the report-specification file while it still expected input. Possibly you omitted an END statement. A minimal FORMAT section that contains at least an EVERY ROW statement is required, and any control block must contain at least one statement.

ACEPREP 遇到了报告规范文件的末尾，而它仍然期望输入。可能您漏掉了一条结束语句。

至少需要一个包含每个行语句的最小格式部分，并且任何控制块都必须包含至少一个语句。

-8061 This report contains a READ statement but no ASCII record definition has been specified.

In order to use the READ statement, you must use the ASCII statement in the DEFINE section to define the expected fields of the ASCII file.

为了使用 READ 句，必须使用 DEFINE 部分中的 ASCII 语句来定义 ASCII 文件的预期字段。

-8062 This report contains a SELECT statement, but a READ statement should be used instead because an ASCII record definition has be specified.

You can base a report on an ASCII file or on database rows, but not on both. The ASCII statement in the DEFINE section means that file input will be used, and a READ statement is used to read the file. If you want to base the report on database rows, retain the SELECT statement and delete the ASCII statement.

您可以将报表建立在 ASCII 文件或数据库行的基础上，但不能两者兼而有之。 DEFINE部分中的 ASCII 语句意味着将使用文件输入，并使用读取语句读取文件。如果要将报表基于数据库行，请保留 SELECT 语句并删除 ASCII 语句。

-8102 There may be only one AFTER or BEFORE GROUP OF clause for any single column specified in the ORDER BY command.

The report contains more than one AFTER GROUP OF clause for a certain column or more than one BEFORE GROUP OF clause. Only one of each can name a given column. However, you can combine the statements from the multiple clauses into a single clause.

报告包含某一列的多个 AFTER GROUP OF 子句或一组 BEFORE GROUP OF 子句。每个列中只有一个可以命名给定的列。但是，可以将多个子句中的语句组合为一个子句。

-8103 In order for the BEFORE or AFTER GROUP OF clause to function properly,the column specified in the clause must also have been specified as a sort column in the ORDER BY command. If the sort column is subscripted, the column in the BEFORE or AFTER GROUP OF clause must be also.

Make sure that the control columns are specified identically in both the ORDER BY statement and the GROUP OF clauses.

确保控件列按 ORDER BY 语句和 GROUP OF 子句的相同方式指定。

-8104 Group aggregates can only be used in an AFTER GROUP OF clause.

Aggregate values over a group are accumulated while the rows of the group are being processed, so they are not available until the end of the group is seen. Therefore, the report cannot refer to them except in an AFTER GROUP OF clause.

组上的聚合值是在处理组的行时累积的，因此在看到组结束之前它们是不可用的。因此，报告除在 AFTER GROUP OF 语句外，不能提及它们。

-8105 Aggregates may not be used within another aggregate. Nor may aggregates be used within the WHERE clause of another aggregate.

Aggregate functions cannot be nested, primarily because the value of the inner aggregate is not known while the outer aggregate is being accumulated. Rewrite aggregate expressions to refer only to columns and simple expressions on columns. In an AFTER GROUP OF clause, you can save the aggregate value from one group of rows in a variable in order to use it to compute an aggregate over a subsequent group.

聚合函数不能嵌套，主要是因为外部聚合正在累积时不知道内部聚合的值。重写聚合表达式，仅引用列和列上的简单表达式。在 AFTER GROUP OF 子句中，可以从变量中的一组行中保存聚合值，以便使用它计算后续组上的聚合。

-8107 A user variable or parameter has been defined by the user more than once.

You can define a name only once in a DEFINE section. You used a name more than once in the ASCII, PARAM, or VARIABLE statements.

只能在定义节中定义名称一次。您在 ASCII、PARAM 或 VARIABLE 语句中多次使用名称。

-8108 A user variable or parameter must have a length which is greater than zero.

Make sure that every CHAR and VARCHAR field in the DEFINE section has a nonzero length specification.

确保 DEFINE 部分中的每个 CHAR 和 VARCHAR 字段都有一个非零长度规范。

-8109 Wordwrap may not be used within PAGE HEADERS or TRAILERS.

ACEPREP needs to know how many lines will be filled in header and trailer sections (otherwise, it does not know how many detail rows to put on the page). However, printing with the WORDWRAP function can fill a variable number of lines, depending on the words. Therefore, it is not allowed in page header or trailer sections.

ACEPREP 需要知道标头和拖尾部分将填充多少行（否则，它不知道要在页面上放置多少详细行）。但是，使用 WORDWRAP 函数打印可以填充可变的行数，这取决于单词。因此，它不允许在页眉或拖尾部分。

-8110 The user variable called name has not yet been defined.

The variable, parameter, or field name was not defined in the DEFINE section. If name is spelled correctly, it must be defined.

变量、参数或字段名未在 DEFINE 部分中定义。如果名称拼写正确，则必须定义名称。

-8111 User variables and run-time parameters may not be used in an ORDER BY statement.

Only names of columns can be used in an ORDER BY clause. Check the spelling of the column names or display labels in the clause. You cannot request ordering by the contents of defined variables,parameters, or ASCII fields.

只有列的名称可以按 ORDER BY 子句使用。检查列名的拼写或在子句中显示标签。不能根据定义的变量、参数或 ASCII 字段的内容请求排序。

-8112 Within an IF-THEN-ELSE statement of a header or trailer clause, the number of lines printed in the IF part must equal the number of lines printed in the ELSE part.

ACEPREP needs to know how many lines will be filled in header and trailer sections (otherwise, it does not know how many detail rows to put on the page). Because it cannot tell which part of an IF statement will be executed, it requires that both produce the same number of lines of output.

ACEPREP 需要知道标头和拖尾部分将填充多少行（否则，它不知道要在页面上放置多少详细行）。因为它不能判断 IF 语句的哪一部分将被执行，所以它要求两者产生相同的输出行数。

-8113 SKIP TO TOP OF PAGE is not allowed in any header or trailer clause.

When SKIP TO TOP OF PAGE is executed, the page-trailer clause must be executed (to display fixed page-end material), followed by the page-header clause. If the statement was allowed in a header or trailer clause, an infinite loop could ensue.

当执行 SKIP TO TOP OF PAGE 时，必须执行 page-trailer 子句（以显示固定的页尾材料），然后执行 page-header 子句。如果在 header 或 trailer 子句中允许该语句，则会产生无限循环。

-8114 The number of lines to be printed in the top and bottom margins plus the lines to be printed in the page header and trailer clauses exceeds or equals the page length.

Examine the statements in the OUTPUT section and in any HEADER and TRAILER clauses. The total of lines that these statements use must be sufficiently less than the specified page length that some detail rows can be printed.

检查 OUTPUT 部分中的语句以及任何 HEADER 和 TRAILER 子句中的语句。这些语句使用的行总数必须小于指定的页长，以便可以打印一些详细信息行。

-8115 There may be no more than 8 sort columns specified in the ORDER BY command.

ACEGO limits the number of columns that can be ordered. You must reduce the number of columns that are listed following ORDER BY.

ACEGO 限制可以排序的列数。必须减少按以下 ORDER BY 列出的列数。

-8116 Illegal subscripting in ORDER BY command.

You can only subscript a character field. Check the subscripts. No negative numbers are allowed; the numbers must fall within the length of the character column; and the first number must be less than or equal to the second number.

只能下标字符字段。检查下标。不允许负数；数字必须在字符列的长度之内；第一个数字必须小于或等于第二个数字。

-8121 The specified WORDWRAP RIGHT MARGIN value is out of range. It must be greater than or equal to the current column and less than or equal to the report's right.

The right margin of a WORDWRAP clause is used to set a narrower right margin than the one that applies to the report as a whole. The effective left margin of a WORDWRAP display is the current column when WORDWRAP is processed. The right margin must fall between the current column and the report margin.

WORDWRAP 子句的右边距用于设置比整个报表更窄的右边距。处理 WORDWRAP 时，WORDWRAP 显示的有效左边框是当前列。右边距必须介于当前列和报表边距之间。

-8122 NEED n LINES may not be used in PAGE HEADER or PAGE TRAILER clauses.

The PRINT statements in a page header or trailer establishes its size.

To set a larger size, use PRINT statements with no parameters.

页眉或拖尾中的 PRINT 语句确定其大小。若要设置较大的大小，请使用没有参数的PRINT 语句。

-8123 The PRINT FILE command is not allowed within the FIRST PAGE HEADER,PAGE HEADER, or PAGE TRAILER clauses.

ACEPREP needs to know how many lines will be filled in header and trailer sections (otherwise, it does not know how many detail rows to put on the page). Because the size of a file cannot be predicted when the report is compiled, the PRINT FILE command is not allowed. You must use PRINT statements to produce the data.

ACEPREP 需要知道标头和拖尾部分将填充多少行（否则，它不知道要在页面上放置多少详细行）。因为在编译报表时无法预测文件的大小，因此不允许使用 PRINT FILE 命令。

必须使用 PRINT 语句生成数据。

-8124 A user variable used in the above query has not been defined in the DEFINE section.

A variable that is named in the SELECT statement is not defined in the DEFINE section of the report. Check that all names in the SELECT statement are the ones that you intended and that you have not misspelled any column or variable names.

在 SELECT 语句中命名的变量未在报表的 DEFINE 部分中定义。检查 SELECT 语句中的所有名称是否都是您想要的名称，并且您是否拼写错了任何列名或变量名。

-8125 The keyword END was found more than once inside the SELECT section.

Within the SELECT section, use semicolons to separate SQL statements. Use the keyword END only after the final SELECT.

Review the contents of the SELECT section to make sure that each SELECT statement except the last one ends in a semicolon and that the last one is followed by an END statement. Perhaps you omitted the FORMAT statement at the beginning of that section.

检查 SELECT 部分的内容，以确保每个 SELECT 语句（最后一个语句除外）都以分号结尾，最后一个语句后面跟着一个 END 语句。也许您在这一节的开头省略了 FORMAT语句。

-8126 PARAM[0] may not be defined.

The first parameter that you can define in the PARAMETER statement is number 1. In some host-operating systems, the zeroth parameter is preset to the program name, but this value is not available within a report.

可以在 PARAMETER 语句中定义的第一个参数是数字 1。在某些主机操作系统中，zeroth 参数被预置到程序名，但该值在报表中不可用。

-8127 You cannot use more than one REPORT TO statement in a report specification.

The entire report is directed to one destination, which is chosen with the REPORT TO statement in the OUTPUT section. The report cannot be divided between multiple destinations, so remove all REPORT TO statements after the first. If you want to produce separate report files for different sets of data, perform one of the following steps:整个报告指向一个目标，该目标与 OUTPUT 部分中的 REPORT TO 语句一起选择。报告不能在多个目的地之间划分，因此在第一个目标之后移除所有的 REPORT TO语句。如果要为不同数据集生成单独的报表文件，请执行下列步骤之一：* Write a separate report for each set of data (the specifications should differ only in their SELECT statements).

* 为每一组数据分别编写一份报告（规范只应在其 SELECT 语句中有所不同）。

* Produce a full report, but with sets of data on separate pages,and use operating-system utilities and tools to separate the files afterward.

* 生成完整的报告，但在单独的页面上有一组数据，然后使用操作系统实用程序和工具来分离文件。

* Use parameter variables in the SELECT statements so that you can choose a subset of data dynamically, when you run the report, and use REPORT TO PRINT so that you can set the DBPRINT variable to control the output destination before you start the report.

* 在 SELECT 语句中使用参数变量，以便在运行报表时动态选择数据子集，并使用报表打印，以便在启动报表之前设置 DBPRINT 变量以控制输出目的地。

-8128 Minimum length of a VARCHAR variable must be smaller than the maximum size.

A VARCHAR variable is defined with the two numbers name(n,r), where n is the maximum length of the variable and r is the reserved length. The reserved length is meaningful only in the context of a database table definition, although it is allowed when you define a report variable.

If you specify it, you must write a number for r that is less than or equal to the size, n.

VARCHAR 变量定义为两个数字名(n，r)，其中 n 是变量的最大长度，r 是保留长度。

保留长度仅在数据库表定义的上下文中有意义，尽管在定义报表变量时允许保留长度。如果指定它，则必须为 r 编写小于或等于 n 大小的数字。

-8129 Specified page length length is too short for default report.

A report page cannot fit in the number of lines that are specified.

Allow more lines per page or revise the report specification to use fewer lines (for instance, by changing the top or bottom margins).

报表页不能与指定的行数相匹配。允许每页增加行数或修改报表规范，以减少行数（例如，通过更改顶部或底部边距）。

-8130 An INTEGER constant may not be larger than 2147483647.

This statement specifies a value that cannot be contained in an integer. Either use a smaller value or a different data type (for example, DECIMAL).

此语句指定不能包含在整数中的值。要么使用较小的值，要么使用不同的数据类型(例如，DECIMAL )。

-8200 User does not have DBSECADM authority.

User does not have the necessary permission to perform the operation;only DBSECADM has the authority to perform this operation. Contact the DBSECADM to perform this operation.

用户没有执行该操作所需的权限；只有 DBSECADM 有权执行此操作。请与 DBSECADM 联系以执行此操作。

-8201 The security label component already exists.

The security label component to be created is already defined in the database. For RENAME SECURITY LABEL COMPONENT, a security label component with the specified new name already exists. Verify that you have specified the correct component name and that you are in the correct database.

要创建的安全标签组件已在数据库中定义。对于 RENAME SECURITY LABEL COMPONENT，已存在具有指定新名称的安全标签组件。验证您已经指定了正确的组件名称，并且您在正确的数据库中。

-8202 The security label component element is already defined.

The security label component element was specified more than once in the list of security label component elements. For TREE security label component, the security label component element is already defined as ROOT or UNDER some other element. Specifying the element more than once on the left side of UNDER clause is not allowed. Verify that you have specified the correct component element name.

安全标签组件元素在安全标签组件元素列表中多次指定。对于 TREE 安全标签组件，安全标签组件元素已经定义为 ROOT 元素或 UNDER 其他元素。不允许在 UNDER 子句左侧多次指定元素。验证是否指定了正确的组件元素名称。

-8203 The security label component element exceeds 32 bytes.

The security label component element specified exceeds its limit length of 32 bytes. Specify a shorter name.

指定的安全标签组件元素超过了其 32 字节的限制长度。指定较短的名称。

-8204 The security label component has too many elements.

A security label component can have no more than 64 elements.

Your statement exceeded this limit. Specify a smaller number of elements within the limit.

安全标签组件不能有超过 64 个元素。您的声明超过了这个限制。在限制范围内指定较小数量的元素。

-8205 The security label component element is not yet defined.

This error can have any of the following causes:此错误可能有下列任何原因：* The element is used on the right side of the UNDER clause in CREATE or ALTER SECURITY LABEL COMPONENT statement but has not yet been defined as being ROOT or being UNDER some other element. Define the object as ROOT or as being UNDER some defined element.

* 元素在 CREATE 或 ALTER SECURITY LABEL COMPONENT 语句中 UNDER 子句的右侧使用，但尚未被定义为根元素或其他元素下的元素。将对象定义为根或位于某个已定义元素下。

* The element is used on the right side of BEFORE or AFTER clause of ALTER SECURITY LABEL COMPONENT has not yet been defined. Specify a defined or existing element name.

* 元素使用在尚未定义的 ALTER SECURITY LABEL COMPONENT 组件的“前”或“后”子句的右侧。指定已定义或现有的元素名称。

-8206 The security policy already exists.

The security policy to be created is already defined in the database.

For RENAME SECURITY POLICY, a security policy with the specified new name already exists. Verify that you have specified the correct policy name and that you are in the correct database.

要创建的安全策略已在数据库中定义。对于 RENAME SECURITY POLICY，已存在具有指定新名称的安全策略。验证您已指定正确的策略名称，并且您位于正确的数据库中。

-8207 The security label component was specified more than once.

The security label component was duplicated in the list of components of a security policy or a security label. Verify that you have specified the security label component name correctly. Remove any duplicates from the list of security label components.

安全标签组件在安全策略或安全标签的组件列表中重复。验证是否正确指定了安全标签组件名称。从安全标签组件列表中删除任何副本。

-8208 The security label component does not exist.

The specified security label component does not exist in the database.

Verify that you have specified the correct security label component name, and that you are in the correct database.

数据库中不存在指定的安全标签组件。验证您已指定了正确的安全标签组件名称，并且您位于正确的数据库中。

-8209 The maximum number of components in security policy has been exceeded.

A security policy can have a maximum of 16 components. You have exceeded the number of component allowed to make up a security policy.

安全策略最多可以有 16 个组件。您已经超过了允许组成安全策略的组件的数量。

-8210 The security policy does not exist.

The specified security policy does not exist in the database. Verify that you have specified the correct security policy name, and that you are in the correct database.

数据库中不存在指定的安全策略。验证您已指定了正确的安全策略名称，并且您位于正确的数据库中。

-8211 The security label already exists.

The security label to be created is already defined in the database.

For RENAME SECURITY LABEL, a security label with the specified new name already exists. Verify that you have specified the correct label name and that you are in the correct database.

要创建的安全标签已在数据库中定义。对于重命名安全标签，已存在具有指定新名称的安全标签。验证您已指定了正确的标签名，并且您位于正确的数据库中。

-8212 The security label component is not defined in the security policy.

Security labels can only contain values for those components that are defined in the security policy of which the label is a part. The specified security label component is not part of the security policy, so the component cannot be used in that security label. Verify that you have specified the correct component name and that you are in the correct database.

安全标签只能包含标签是其一部分的安全策略中定义的组件的值。指定的安全标签组件不是安全策略的一部分，因此不能在该安全标签中使用该组件。验证您已经指定了正确的组件名称，并且您在正确的数据库中。

-8213 The element is not defined in the security label component.

The component element does not exist in the definition of the security label component. If you get this error when executing the scalar function SECLABEL_BY_COMP(), then check the security label string to make sure that the values are listed in the same order that the components are listed in the security policy.

组件元素在安全标签组件的定义中不存在。如果在执行标量函数 SECLABEL_BY_COMP() 时获得此错误，则检查安全标签字符串，以确保这些值按与安全策略中列出的组件相同的顺序列出。

-8214 Two or more elements are specified for the security label component .

A security label cannot have multiple elements for a component of type ARRAY. Specify only one element for the security label component.

类型数组的组件的安全标签不能有多个元素。只为安全标签组件指定一个元素。

-8215 The security label component element was specified more than once.

The security label component element was duplicated in the list of elements of a security label component. Verify that you have specified the security label component element name correctly. Remove any duplicates from the list of security label component elements.

安全标签组件元素在安全标签组件的元素列表中重复。验证您是否正确指定了安全标签组件元素名称。从安全标签组件元素列表中删除所有重复项。

-8216 The access rule does not exist in the rule set used by the security policy.

The access rule specified in the GRANT EXEMPTION or REVOKE EXEMPTION statement is not part of the LBAC rule set that is used by the security policy. Specify an access rule that is part of the rule set used by the specified security policy.

在 GRANT EXEMPTION 或 REVOKE EXEMPTION 语句中指定的访问规则不是安全策略使用的 LBAC 规则集的一部分。指定一个访问规则，该规则集是指定的安全策略使用的规则集的一部分。

-8217 Cannot specify PUBLIC or a role name.

GRANT or REVOKE SECURITY LABEL or EXEMPTIONS to or from PUBLIC or a role is not allowed. Specify an individual user name.

不允许 GRANT or REVOKE SECURITY LABEL 或 EXEMPTIONS to or from PUBLIC or a role 。指定一个单独的用户名。

-8218 A DBSECADM cannot grant a privilege, security label or exemption to self.

DBSECADM is not allowed to grant a privilege, security label, or exemption to self. Ask another DBSECADM to perform this operation.

DBSECADM 不允许将权限、安全标签或豁免授予自己。请另一个 DBSECADM 执行此操作。

-8219 A DBSECADM cannot revoke a privilege, security label or exemptions from self.

DBSECADM is not allowed to revoke a privilege, security label, or exemption from self. Ask another DBSECADM to perform this operation.

DBSECADM 不允许由自己撤回权限、安全标签或豁免。请另一个 DBSECADM 执行此操作。

-8220 User does not hold this privilege, security label,or exemption.

The specified user does not hold this privilege, security label, or exemption, so the revoke operation failed.

指定的用户不拥有此权限、安全标签或豁免，因此撤消操作失败。

-8221 The security label does not exist for the security policy.

The specified security label does not exist for the security policy.

Verify that you have specified the correct security label name and security policy name and that you are in the correct database.

安全策略不存在指定的安全标签。验证您是否指定了正确的安全标签名称和安全策略名称，并且您位于正确的数据库中。

-8222 User already has a security label for READ access.

Each user can have at most one security label for READ access and at most one for WRITE access. A security label has already been granted to the user for READ access. If you want to change the user's security label for READ access, you must first use the REVOKE SECURITY LABEL statement to revoke the security label from the user.

每个用户最多可以有一个用于读访问的安全标签，最多一个用于写访问。已将安全标签授予用户进行读取访问。如果要更改用户的安全标签以进行读取访问，则必须首先使用REVOKE 安全性标签语句从用户撤消安全标签。

-8223 User already has a security label for WRITE access.

Each user can have at most one security label for READ access and at most one for WRITE access. A security label has already been granted to the user for WRITE access. If you want to change the user's security label for WRITE access, you must first use the REVOKE SECURITY LABEL statement to revoke the security label from the user.

每个用户最多可以有一个用于读访问的安全标签，最多一个用于写访问。已将安全标签授予用户进行写访问。如果要更改用户的安全标签以进行写访问，则必须首先使用REVOKE 安全性标签语句从用户撤消安全标签。

-8224 The security label conflicts with the existing granted security label.

If the user is granted two distinct labels, one for READ access and another for WRITE access, they must satisfy the following rules:如果授予用户两个不同的标签，一个用于读访问，另一个用于写访问，则它们必须满足以下规则：* For security label components of type ARRAY, the value must be the same in both security labels.

* 对于 ARRAY 类型的安全标签组件，两个安全标签中的值必须相同。

* For security label components of type SET, the values given in the security label used for WRITE access must be a subset of the values given in the security label used for READ access.

* 对于 SET 类型的安全标签组件，用于写访问的安全标签中给定的值必须是用于读取访问的安全标签中给定值的子集。

* For security label components of type TREE, either the values must be the same, or the values given in the security label used for WRITE access must be one of the sub tree values of the security label used for READ access.

* 对于 TREE 类型的安全标签组件，要么值必须相同，要么用于写访问的安全标签中给定的值必须是用于读取访问的安全标签的子树值之一。

-8225 The security label component is currently in use.

The security label component cannot be dropped because one or more security policies refer to it. The following query can be used find all the security policies that refer to this security label component:安全标签组件不能删除，因为一个或多个安全策略引用它。可以使用以下查询查找引用此安全标签组件的所有安全策略：SELECT SECPOLICYNAME FROM SYSSECPOLICIES WHERE SECPOLICYID = (SELECT SECPOLICYID FROM SYSSECPOLICYCOMPONENTS WHERE COMPID = (SELECT COMPID FROM SYSSECLABELCOMPONENTS WHERE COMPNAME = ""))-8226 The security label <policy-name.label-name> is currently in use.

The security label could not be dropped because:无法删除安全标签，因为：* It is granted to one or more users. Revoke this security label from all users who have been granted this security label for this security policy. The following query can be used to find all the users who have been granted with this security label.

* 它被授予一个或多个用户。从为此安全策略授予此安全标签的所有用户中撤消此安全标签。以下查询可用于查找所有已授予此安全标签的用户。

SELECT GRANTEE FROM SYSSECLABELAUTH WHERE READSECLABELID = (SELECT SECLABELID FROM SYSSECLABELNAMES WHERE SECLABELNAME = "" AND SECPOLICYID = (SELECT SECPOLICYID FROM SYSSECPOLICIES WHERE SECPOLICYNAME = "")) OR WRITESECLABELID = (SELECT SECLABELID FROM SYSSECLABELNAMES WHERE SECLABELNAME = "" AND SECPOLICYID = (SELECT SECPOLICYID FROM SYSSECPOLICIES WHERE SECPOLICYNAME = ""))* It is being used to protect one or more columns. For all the tables that use this security label to protect a column, either alter the table to drop this column protection or drop the table.

The following query can be used to find all protected tables and all the columns that are protected with this security label.

* 它用于保护一个或多个列。对于使用此安全标签保护列的所有表，要么更改表以删除该列保护，要么删除该表。下面的查询可用于查找所有受保护的表和所有受此安全标签保护的列。

SELECT TABNAME, COLNAME FROM SYSCOLUMNS, SYSTABLES WHERE SYSCOLUMNS.TABID = SYSTABLES.TABID AND SECLABELID = (SELECT SECLABELID FROM SYSSECLABELNAMES WHERE SECLABELNAME = "" AND SECPOLICYID = (SELECT SECPOLICYID FROM SYSSECPOLICIES WHERE SECPOLICYNAME = ""))-8227 The security policy is currently in use.

The security policy could not be dropped because:无法取消安全策略，因为：* It is being used to protect one or more tables. For all the tables that use this security policy, either alter the table to drop this table protection or drop the table. The following query can be used to find all the tables protected by this policy:* 它用于保护一个或多个表。对于使用此安全策略的所有表，要么更改表以删除此表保护，要么删除表。以下查询可用于查找受此策略保护的所有表：SELECT TABNAME FROM SYSTABLES WHERE SECPOLICYID= (SELECT SECPOLICYID FROM SYSSECPOLICIES WHERE SECPOLICYNAME = "" )* There are one or more security labels that use it. Drop all the security labels that are part of this security policy. The following query can be used find all security labels that belong to this security policy:* 有一个或多个安全标签使用它。删除作为此安全策略一部分的所有安全标签。可以使用以下查询查找属于此安全策略的所有安全标签：SELECT SECLABELNAME FROM SYSSECLABELS WHERE SECPOLICYID=(SELECT SECPOLICYID FROM SYSSECPOLICIES WHERE SECPOLICYNAME = "" )* There are one or more exemptions granted on one or more of its rules. Revoke all exemptions granted for this security policy from all users. The following query can be used to find all users that have been granted exemptions for this policy:* 它的一项或多项规则有一项或多项豁免。撤消所有用户对此安全策略授予的所有豁免。以下查询可用于查找已为此策略授予豁免的所有用户：SELECT GRANTEE, EXEMPTION FROM SYSSECPOLICYEXEMPTIONS WHERE SECPOLICYID=(SELECT SECPOLICYID FROM SYSSECPOLICIES WHERE SECPOLICYNAME = "")-8228 Cannot GRANT or REVOKE SETSESSIONAUTH privilege to or from PUBLIC.

To grant or revoke SETSESSIONAUTH privilege to or from PUBLIC is not allowed. Specify an individual user or role name.

授予或撤销 SETSESSIONAUTH 特权是不允许的。指定单个用户或角色名称。

-8229 User does not have SETSESSIONAUTH privilege.

Only users holding SETSESSIONAUTH privilege can perform SET SESSION AUTHORIZATION operation. Ask the DBSECADM to grant the privilege.

只有拥有 SETSESSIONAUTH 权限的用户才能执行 SET SESSION AUTHORIZATION 权限设置操作。请求 DBSECADM 授予该权限。

-8230 User does not have the authority to grant or revoke DBSECADM.

Only the DBSA has the authority to grant or revoke DBSECADM privilege.

Contact the DBSA to perform this operation.

只有 DBSA 有权授予或撤销 DBSECADM 权限。请与 DBSA 联系以执行此操作。

-8231 DBSECADM cannot be granted to user .

The GRANT statement attempted to grant DBSECADM to an authorization name that is not allowed to receive that authority. The DBSECADM authority can only be granted to an individual user.

GRANT 语句试图将 DBSECADM 授予不允许接收该权限的授权名称。DBSECADM 权限只能授予单个用户。

-8232 The element already exists in the security label component.

During ALTER SECURITY LABEL COMPONENT, the security label component element to be added to an existing component is already defined in that security label component.

在 ALTER SECURITY LABEL COMPONENT 期间，要添加到现有组件中的安全标签组件元素已经在该安全标签组件中定义。

-8233 Cannot secure columns or rows in a table without a security policy.

A table cannot be protected with row or column level granularity without associating a security policy with the table. The user should add a security policy to the table using the SECURITY POLICY clause of the CREATE TABLE statement or the ADD SECURITY POLICY clause of the ALTER TABLE statement.

如果不将安全策略与表关联，则无法使用行或列级粒度保护表。用户应该使用 CREATE TABLE 语句的安全策略子句或 ALTER TABLE 语句的 ADD SECURITY POLICY 子句向表添加安全策略。

-8234 Invalid specification of a column of type IDSSECURITYLABEL.

For a column of type IDSSECURITYLABEL, the specification of an attribute for the column is invalid because a column of type IDSSECURITYLABEL cannot be encrypted or altered to a different data type. The column of type IDSSECURITYLABEL also cannot have attributes like column protection,single column contraints or be part of multiple column referential or check contraints. The DEFAULT clause cannot be specified for the IDSSECURITYLABEL column in a CREATE TABLE statement. The DEFAULT clause can be specified for the IDSSECURITYLABEL column only in an ALTER TABLE statement. The default value provided will only be applied to existing rows in the table.

对于 IDSSECURITYLABEL 类型的列，该列的属性规范无效，因为 IDSSECURITYLABEL 类型的列不能加密或更改为不同的数据类型。IDSSECURITYLABEL 类型的列也不能具有列保护、单列约束等属性，也不能成为多列引用或Check 约束的一部分。不能为 CREATE TABLE语句中的 IDSSECURITYLABEL 列指定 DEFAULT 子句。DEFAULT 子句只能在 ALTER TABLE语句中为 IDSSECURITYLABEL 列指定。提供的缺省值将仅应用于表中的现有行。

-8235 A security policy cannot be added to a temporary, typed or external table.

Adding a security policy to a temporary, typed or external table is not supported. Do not associate a security policy with a temporary or external table.

不支持向临时表、类型表或外部表添加安全策略。不要将安全策略与临时表或外部表相关联。

-8236 Only one security label column is allowed in a table.

An attempt was made to create or alter a table with more than one security label column. For a CREATE TABLE statement, declare only one column to have the IDSSECURITYLABEL type. For an ALTER TABLE statement, a column of type IDSSECURITYLABEL already exists.

尝试创建或更改具有多个安全标签列的表。对于 CREATE TABLE 语句，只声明一个列具有IDSSECURITYLABEL 类型。对于 ALTER TABLE 语句，IDSSECURITYLABEL 类型的列已经存在。

-8237 Cannot modify column to type IDSSECURITYLABEL.

An existing column cannot be modified to IDSSECURITYLABEL data type;this data type is used only for the security label column to protect data rows. To protect table with row-level granularity, add a new column of type IDSSECURITYLABEL.

现有列不能修改为 IDSSECURITYLABEL 数据类型；此数据类型仅用于安全标签列以保护数据行。为了保护具有行级粒度的表，添加一个 IDSSECURITYLABEL 类型的新列。

-8238 Source table must have the same security protection as target table.

The security protection on the tables is not identical. The tables are protected by different security policies or the set of security labels protecting columns in the source table is not identical to that of target table. The two tables must have the same secuirty policy, same protection granularity, have the same set of protected columns, and each pair of corresponding columns must be protected with same security label.

表上的安全保护并不相同。表受不同安全策略的保护，或者源表中保护列的安全标签集与目标表中的安全标签不完全相同。这两个表必须具有相同的安全策略、相同的保护粒度、同一组受保护的列，并且每一对对应的列都必须使用相同的安全标签进行保护。

-8239 The table already has a security policy.

A table can have at most one security policy attached to it. Do not try to associate another security policy with the table before you have dropped the association of the table with its current security policy.

一个表最多可以附加一个安全策略。在删除表的关联和当前的安全策略之前，不要尝试将其他安全策略与表关联。

-8240 The table is not protected with a security policy.

A security policy cannot be dropped from a table that is not protected with a security policy.

不能从不受安全策略保护的表中删除安全策略。

-8241 The column has already been protected by a security label.

The specified column is already protected by a security label. Do not add another security label for protecting the column.

指定的列已经受到安全标签的保护。不要添加另一个用于保护列的安全标签。

-8242 The column is not protected by a security label.

Column security cannot be dropped from a column that is not protected by a secuirty label.

不能从不受安全标签保护的列中删除列安全性。

-8243 User does not hold a security label for READ access.

To execute the built-in function SECLABEL_TO_CHAR, the user must have a security label for READ access of the security policy. Ask the DBSECADM to grant a security label for READ access.

要执行内置函数 SECLABEL_TO_CHAR，用户必须拥有安全策略的读访问安全标签。请DBSECADM 授予读取访问的安全标签。

-8244 The value provided for row security label column is invalid.

An INSERT or UPDATE statement specified a value for a column of type IDSSECURITYLABEL. The value corresponds to a null label or cannot be converted to a valid security label for the security policy that is protecting the table. Check the INSERT or UPDATE statement and make sure that the value being set in the security label column is valid for the security policy protecting the table. Sometimes an invalid value can be generated as a result of a SELECT statement done from a table that is not protected with the same security policy as the target table. You should only copy security labels between tables protected by the same security policy.

INSERT 或 UPDATE 语句为 IDSSECURITYLABEL 类型的列指定一个值。该值对应于空标签，或不能转换为保护表的安全策略的有效安全标签。检查 INSERT 或 UPDATE 语句，并确保安全标签列中设置的值对于保护表的安全策略有效。有时，从不受目标表保护的表中执行的 SELECT 语句可以生成无效的值。只应在受同一安全策略保护的表之间复制安全标签。

-8245 User cannot perform READ access to the protected column.

While accessing the table protected by a security policy, the user is attempting SELECT, DELETE, or UPDATE access on the column. The user does not have the LBAC credentials necessary to read the column.

Ask the DBSECADM to grant the user the LBAC credentials that allow READ access to the column.

在访问受安全策略保护的表时，用户正在尝试对列进行 SELECT、DELETE 或 UPDATE 访问。用户没有读取列所需的 LBAC 凭据。请 DBSECADM 授予用户允许读取该列的 LBAC 凭据。

-8246 User cannot perform WRITE access to the protected column.

While accessing the table protected by a security policy, the user is attempting INSERT, DELETE, or UPDATE access on column. The user does not have the LBAC credentials necessary to update the column.

Ask the DBSECADM to grant the user the LBAC credentials that allow WRITE access to the column.

在访问受安全策略保护的表时，用户正在尝试对列进行 SELECT、DELETE 或 UPDATE 访问。用户没有更新列所需的 LBAC 凭据。请 DBSECADM 授予用户 LBAC 凭据，允许对该列进行写访问。

-8247 User does not have the LBAC credentials to perform INSERT on table .

The user is not allowed to perform INSERT on the table. A user is not allowed to insert a row into a protected table if the user does not have appropriate security label or exemption credentials. Ask the DBSECADM to grant the user the proper security label or exemptions required to perform insert operation.

不允许用户在表上执行 INSERT 操作。如果用户没有适当的安全标签或豁免凭据，则不允许用户将一行插入受保护的表中。请 DBSECADM 授予用户执行 INSERT 操作所需的适当安全标签或豁免。

-8248 User does not have the LBAC credentials to perform SELECT on table .

The user is not allowed to perform SELECT on the table. A user is not allowed to select rows in a protected table if the user does not have appropriate security label or exemption credentials. Ask the DBSECADM to grant the user the proper security label or exemptions required to perform select operation.

不允许用户在表上执行 SELECT 。如果用户没有适当的安全标签或豁免凭据，则不允许用户在受保护的表中选择行。请 DBSECADM 授予用户执行 SELECT 操作所需的适当安全标签或豁免。

-8249 User does not have the LBAC credentials to perform UPDATE on table .

The user is not allowed to perform UPDATE on the table. A user is not allowed to update a row in a protected table if the user does not have appropriate security label or exemption credentials. Ask the DBSECADM to grant the user the proper security label or exemptions required to perform update operation.

不允许用户对表执行 UPDATE 。如果用户没有适当的安全标签或豁免凭据，则不允许用户更新受保护表中的行。请 DBSECADM 授予用户执行 UPDATE 操作所需的适当安全标签或豁免。

-8250 User does not have the LBAC credentials to perform DELETE on table .

The user is not allowed to perform DELETE on the table. A user is not allowed to delete a row from a protected table if the user does not have appropriate security label or exemption credentials. Ask the DBSECADM to grant the user the proper security label or exemptions required to perform delete operation.

不允许用户对表执行 DELETE 操作。如果用户没有适当的安全标签或豁免凭据，则不允许用户从受保护的表中删除一行。请 DBSECADM 授予用户执行 DELETE 操作所需的适当安全标签或豁免。

-8251 Update, delete, or insert into a UNION ALL view is not allowed.

Updates, deletes, and inserts are not allowed into a UNION ALL view if that view is created on one or more protected tables. If you have sufficient credentials, perform the DML operation on the base table,rather than on the UNION ALL view.

如果在一个或多个受保护的表上创建了 UNION ALL 视图，则不允许更新、删除和插入。

如果有足够的凭据，则在基表上执行 DML 操作，而不是在 UNION ALL视图上执行 DML操作。

-8252 Cannot set role to DBSECADM.

DBSECADM is a system defined role. SET ROLE statement can only be used with user created roles.

DBSECADM 是一个系统定义的角色。SET ROLE 语句只能与用户创建的角色一起使用。

-8253 Cannot open database .

The database server cannot find the specified database. To find the names of all databases, query sysmaster:sysdatabases.

数据库服务器找不到指定的数据库。要查找所有数据库的名称，请查询 sysmaster：sysdatabases。

-8254 Database is currently opened by another user.

Another user has opened the specified database in exclusive mode. Repeat the statement after a short delay or when the database is known to be idle.

另一个用户已以独占模式打开指定的数据库。在短时间延迟或数据库已知空闲时重复该语句。

-8255 User does not have DBSA authority.

User does not have the necessary permission to perform the operation;only DBSA has the authority to perform this operation. Contact the DBSA to perform this operation.

用户没有执行该操作所需的权限；只有 DBSA 有权执行此操作。请与 DBSA 联系以执行此操作。

-8256 Invalid character in element .

The security label component element has an invalid character. The element name cannot include parentheses, comma, or colon characters: ( ), :安全标签组件元素的字符无效。元素名称不能包括括号、逗号或冒号字符：()，：-8257 The security label component element cannot be null.

The security label component element specified is null. The element name should be a non-null quoted character string.

指定的安全标签组件元素为空。元素名应该是一个非空引号字符串。

-8258 The rule specified is not consistent with the security policy.

The rule specified is not consistent with the security policy.

指定的规则与安全策略不一致。

-8259 Cannot GRANT or REVOKE SETSESSIONAUTH privilege for role.

To grant or revoke SETSESSIONAUTH privilege for role is not allowed.

Specify an individual user or PUBLIC.

不允许授予或撤销角色的 SETSESSIONAUTH 权限。指定单个用户或公共用户。

-8260 Multiple security policy clauses.

The security policy clause has been specified more than once. Either ADD or DROP SECURITY POLICY was specified more than once or a combination of ADD and DROP SECUIRTY POLICY was specified. Change the statement to so that it has only one ADD or DROP SECURITY POLICY clause.

已多次指定安全策略子句。ADD or DROP SECURITY POLICY 不止一次指定，或者指定ADD and DROP SECURITY POLICY 的组合。将语句更改为只有一个 ADD or DROP SECURITY POLICY 子句。

-8261 Cannot secure rows in a table without a default value for the IDSSECURITYLABEL column.

A non-empty table cannot be protected with row-level granularity without specifying a default value for the IDSSECURITYLABEL column.

Change the ALTER TABLE statement to specify the DEFAULT clause for the IDSSECUIRTYLABEL column.

如果不为 IDSSECURITYLABEL 列指定默认值，则无法用行级粒度保护非空表。更改 ALTER TABLE 语句以指定 IDSSECUIRTYLABEL 列的缺省子句。

-8262 Cannot update partition flags.

This internal error indicates the database server could not update partition flags to set or unset table protection. Check the accompanying ISAM error code for more information.

此内部错误指示数据库服务器无法更新分区标志以设置或取消表保护。有关更多信息，请查看附带的 ISAM 错误代码。

-8263 The component type specified does not match the type in the system catalog.

The security label component type specified in ALTER SECURITY LABEL COMPONENT statement does not match the type of this component in the system catalog.

在 ALTER SECURITY LABEL COMPONENT 语句中指定的安全标签组件类型与系统目录中此组件的类型不匹配。

-8264 Cannot alter ARRAY security label component to add elements before.

You cannot add more elements before the specified element because too many alters have been performed on the ARRAY security label component. You can add elements before or after other elements in the security label component.

您不能在指定的元素之前添加更多的元素，因为在 ARRAY 安全标签组件上执行了太多的更改。可以在安全标签组件中的其他元素之前或之后添加元素。

-8265 Cannot alter ARRAY security label component to add elements after.

You cannot add more elements after the specified element because too many alters have been performed on the ARRAY security label component. You can add elements before or after other elements in the security label component.

不能在指定元素之后添加更多元素，因为在 ARRAY 安全标签组件上执行了太多的更改。

可以在“安全标签”组件中的其他元素之前或之后添加元素。

-8266 Operation not permitted.

This operation is an internal command that you are not permitted to use.

此操作是不允许使用的内部命令。

-8267 Cannot add LBAC protection to a table defined for replication.

The specified operation cannot be performed on a table if replication is defined on the table. LBAC is not supported with Enterprise Replication.

如果在表上定义了复制，则无法对表执行指定的操作。Enterprise Replication 不支持LBAC。

-8268 Cannot create a distinct type of type IDSSECURITYLABEL.

The statement specified creation of a distinct data type as IDSSECURITYLABEL.

A IDSSECURITYLABEL data type cannot be a distinct type. Remove DISTINCT from the statement or specify a different data type.

该语句指定创建一个不同的数据类型为 IDSSECURITYLABEL 。IDSSECURITYLABEL 数据类型不能是 DISTINCT 的类型。从语句中移除 DISTINCT 的数据类型或指定不同的数据类型。

-8269 LBAC internal error: If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果这个内部错误再次出现，请注意所有情况，并与 GBase 技术支持部门联系。

-8270 Row security label for a protected table cannot be null.

To insert data into a row protected table either user should have LBAC security label or the user has to explicitly specify a row security label.

若要将数据插入受行保护的表中，任何用户都应该具有 LBAC 安全标签，或者用户必须显式指定行安全标签。

-8300 The specified sequence object is not in the database.

The database server cannot find the sequence object specified in the statement. The sequence object might have been renamed or dropped from the database.

数据库服务器找不到语句中指定的序列对象。序列对象可能已被重命名或从数据库中删除。

Check the names of sequence objects in the statement. If the names are spelled as you intended, check that you are using the database you want.

To find the names of all sequence objects, query the syssequences table.

请检查语句中序列对象的名称。如果名称按您的意愿拼写，请检查是否正在使用所需的数据库。若要查找所有序列对象的名称，请查询 syssequences 表。

-8301 Sequence already exists in the database.

This statement tries to create a table or sequence object with the name that is shown, but a sequence object with that name already exists.

Only one table or sequence object with a given name can exist in a single database. (In an ANSI-compliant database, the name of the user that created a table or sequence object name qualifies it, so one table or sequence object of a given name per user can exist.)此语句尝试创建具有所显示名称的表或序列对象，但具有该名称的序列对象已经存在。

在单个数据库中只能存在一个具有给定名称的表或序列对象。(在符合 ANSI 标准的数据库中，创建表或序列对象名称的用户的名称可以对其进行限定，因此每个用户都可以存在一个给定名称的表或序列对象。)Check the spelling of the name; if it is as you intended, and you are sure it should not exist, check that you are using the right database.

You can review the names of all tables and sequence objects in this database by querying systables as follows:检查名称的拼写；如果它是您想要的，并且您确定它不存在，请检查您正在使用正确的数据库。通过查询系统，可以查看此数据库中所有表和序列对象的名称，如下所示：SELECT tabname FROM systables WHERE tabid > 99-8302 A Sequence object definition value is invalid or out of range.

A non-integral or out-of-range value has been specified in the sequence object's definition in the CREATE SEQUENCE or ALTER SEQUENCE statements.

The sequence object's definition parameters include its START/RESTART value, INCREMENT value, MAXVALUE, and MINVALUE.

在 CREATE SEQUENCE 或 ALTER SEQUENCE 语句中序列对象的定义中指定了一个非整数或超出范围的值。序列对象的定义参数包括其 START/RESTART值、 INCREMENT 值、MAXVALUE 和 MINVALUE。

Check that the values specified for the sequence object's definition parameter are integral and in the range (-2e63 + 1) or-9,223,372,036,854,775,807 and (+2e63 -1) or 9,223,372,036,854,775,807.

检查为序列对象定义参数指定的值是整的，并且在范围 (-2e63 + 1) 或-9,223,372,036,854,775,807 和 (+2e63 -1) 或 9,223,372,036,854,775,807 之间。

-8303 Duplicate or conflicting (%s) specification in sequence definition.

A duplicate or conflicting specification for sequence object definition parameters has been found in the CREATE SEQUENCE or ALTER SEQUENCE statements.

在 CREATE SEQUENCE 或 ALTER SEQUENCE 语句中发现了序列对象定义参数的重复或冲突规范。

Conflicting specifications include combination of MAXVALUE-NOMAXVALUE,MINVALUE-NOMINVALUE, CACHE-NOCACHE, ORDER-NOORDER, and CYCLE-NOCYCLE.

相互冲突的规范包括 MAXVALUE-NOMAXVALUE、MINVALUE-NOMINVALUE、CACHE-NOCACHE、ORDER-NOORDER 和 CYCLE-NOCYCLE 的组合。

Check whether any sequence definition parameters have been specified more than once or if both the conflicting parameters have been specified.

检查是否已多次指定任何序列定义参数，或者是否指定了这两个相互冲突的参数。

-8304 MAXVALUE cannot be less than MINVALUE.

You cannot set the MAXVALUE of the sequence object to less than its MINVALUE.

不能将序列对象的 MAXVALUE 设置为小于 MINVALUE 。

-8305 INCREMENT 0 is not allowed in sequences.

You cannot specify an INCREMENT value of 0 for sequence objects. The INCREMENT value has to be a non-zero integral value.

不能为序列对象指定一个为0的 INCREMENT 值。INCREMENT 值必须是一个非零积分值。

-8306 CACHE size should be in the range of 1 to 2,147,483,647.

The number of cached values of a sequence object has to be in the range of 1 to 2,147,483,647.

序列对象的缓存值必须在 1 到 2,147,483,647 之间。

Use NOCACHE parameter specification to specify a cache size of 0.

使用 NOCACHE 参数规范指定缓存大小为 0。

-8307 CACHE size should be less than one cycle. The default CACHE size is 20.

The number of cached values of a sequence object cannot be greater than the number of values generated in single cyclic sequence. The default number of cached values is 20.

序列对象的缓存值的数量不能大于在单个循环序列中生成的值的数量。缓存值的缺省值为 20。

Check whether the number of cached values is less than 20 and no cache parameter has been specified in the sequence object definition. If so, specify an appropriate value for CACHE parameter. Use NOCACHE parameter specification to specify a cache size of 0.

检查缓存值的数量是否小于 20，并且序列对象定义中没有指定 CACHE 参数。如果是，请为 CACHE 参数指定适当的值。使用 NOCACHE 参数规范指定缓存大小为 0。

-8308 Cannot set START value less than MINVALUE or greater than MAXVALUE.

You cannot set a sequence object to start at a value less than its MINVALUE or greater than its MAXVALUE.

不能将序列对象设置为开始值小于 MINVALUE 或大于 MAXVALUE 的值。

Check the statement and modify the range MINVALUE-MAXVALUE or set an appropriate START value in this range.

检查语句并修改范围 MINVALUE-MAXVALUE 或在此范围内设置适当的开始值。

-8309 Cannot RESTART the sequence at a value less than MINVALUE or greater than MAXVALUE You cannot set a sequence object to restart at a value less than its MINVALUE or greater than its MAXVALUE.

不能将序列对象设置为以小于 MINVALUE 或大于 MAXVALUE 的值重新启动。

If you are attempting to restart the sequence, check to see that the RESTART value is in the range MINVALUE-MAXVALUE. If not, either alter the MINVALUE-MAXVALUE parameters or set an appropriate value to restart from.

If you are attempting to alter either or both MINVALUE and MAXVALUE parameters, check to see whether a restart value has already been set for the sequence that does not lie in the altered MINVALUE-MAXVALUE range. To find an existing set restart value, query the syssequences table.

如果试图重新启动序列，请检查重新启动值是否在 MINVALUE-MAXVALUE 范围内。如果没有，可以更改 MINVALUE-MAXVALUE 参数，或者设置要重新启动的适当值。如果试图更改MINVALUE 和 MAXVALUE 参数，请检查是否已为已更改的 MINVALUE-MAXVALUE 范围内的序列设置了重新启动值。若要查找现有的SET重新启动值，请查询 syssequences 表。

-8310 MINVALUE cannot be set to exceed current value.

You cannot alter the sequence definition to set the MINVALUE greater than the current value of the sequence object. The current value of the sequence object is the value generated on last NEXTVAL reference.

不能更改序列定义以设置大于序列对象当前值的 MINVALUE 。序列对象的当前值是在上一次 NEXTVAL 引用上生成的值。

If you have already initialized the sequence in your session, you may compare the CURRVAL of your session with the MINVALUE in the statement.

However, the CURRVAL of your session may not be in sync with the current value of the sequence object, as there may be other sessions generating numbers from the sequence object. You can set and check the current value of the sequence object by generating a number with a NEXTVAL reference.

如果您已经在会话中初始化了该序列，则可以将会话的 CURRVAL 与语句中的 MINVALUE进行比较。但是，会话的 CURRVAL 可能与序列对象的当前值不同步，因为可能有其他会话从序列对象生成数字。您可以通过使用 NEXTVAL 引用生成一个数字来设置和检查序列对象的当前值。

-8311 MAXVALUE cannot be set to be lesser than the current value.

You cannot alter the sequence definition to set MAXVALUE less than the current value of the sequence object. The current value of the sequence object is the value generated on the last NEXTVAL reference.

不能更改序列定义以将 MAXVALUE 设置为小于序列对象的当前值。序列对象的当前值是在最后一个 NEXTVAL 引用上生成的值。

If you have already initialized the sequence in your session, you may compare the CURRVAL of your session with the MAXVALUE in the statement.

However, the CURRVAL of your session may not be in sync with the current value of the sequence object, as there may be other sessions generating numbers from the sequene object. You can set and check the current value of the sequence object by generating a number with a NEXTVAL reference.

如果已经在会话中初始化了序列，则可以将会话的 CURRVAL 与语句中的 MAXVALUE 进行比较。但是，会话的 CURRVAL 可能与序列对象的当前值不同步，因为可能有其他会话从序列对象生成数字。您可以通过使用 NEXTVAL 引用生成一个数字来设置和检查序列对象的当前值。

-8312 No options specified for ALTER SEQUENCE.

The ALTER SEQUENCE statement has no parameters specified to be altered.

Specify the definition parameters you intend to alter and then run the statement.

ALTER SEQUENCE 语句没有指定要更改的参数。指定要更改的定义参数，然后运行该语句。

-8313 Sequence (%s) exceeds its MAXVALUE.

The specified sequence object cannot generate numbers because it has exceeded its MAXVALUE.

指定的序列对象无法生成数字，因为它已经超过了其 MAXVALUE。

If you have set a MAXVALUE for the sequence, you can alter it to a higher value, up to (+2e63 -1) or 9,223,372,036,854,775,807. If the MAXVALUE is already set to this highest value, consider altering your sequence to be a cyclic sequence to restart from the MINVALUE.

如果为序列设置了 MAXVALUE，则可以将其修改为更高的值，最多可达(+2e63 -1) 或9,223,372,036,854,775,807。如果 MAXVALUE 已经设置为此最高值，请考虑将您的序列更改为要从 MINVALUE 重新启动的循环序列。

-8314 Sequence (%s) goes below its MINVALUE.

The specified sequence object cannot generate numbers because it has gone below its MINVALUE.

指定的序列对象无法生成数字，因为它低于其 MINVALUE。

If you have set a MINVALUE for the sequence, you can alter it to a lower value, up to (-2e63 +1) or -9,223,372,036,854,775,807. If the MINVALUE is already set to this lowest value, consider altering your sequence to be a cyclic sequence to restart from the MAXVALUE.

如果已经为序列设置了 MINVALUE，则可以将其更改为较低的值，最多为(-2e63 +1) 或-9,223,372,036,854,775,807。如果 MINVALUE 已经设置为这个最低值，请考虑将您的序列更改为要从 MAXVALUE 重新启动的循环序列。

-8315 Sequence (%s) CURRVAL is not yet defined in this session.

You cannot get the session CURRVAL because the sequence object has not been initialized in this session. The session CURRVAL is the value generated on a previous call to the sequence object's NEXTVAL.

无法获得会话 CURRVAL，因为该会话中没有初始化序列对象。会话 CURRVAL 是在以前调用序列对象的 NEXTVAL 时生成的值。

If the sequence object has been renamed using RENAME SEQUENCE, you will need to reinitialize the sequence object in your session.

如果序列对象已使用重命名序列重命名，则需要在会话中重新初始化序列对象。

Run a NEXTVAL first to define a CURRVAL for the sequence object in your session.

首先运行 NEXTVAL 为会话中的序列对象定义一个 CURRVAL。

-8316 Cannot rename a sequence object using a synonym.

You cannot perform a rename operation on a sequence object using a synonym.

Specify the instead.

不能使用同义词对序列对象执行重命名操作。指定代替。

If you intend to rename the synonym, then drop the existing synonym and create a new one.

如果您打算重命名同义词，那么删除现有的同义词并创建一个新的同义词。

-8317 A sequence object cannot appear in the FROM clause.

A sequence object cannot appear in the FROM clause. To generate a number from the sequence object use:序列对象不能出现在 FROM 子句中。要从序列对象生成一个数字，请使用：SELECT .[NEXTVAL|CURRVAL] from ;A DELETE operation is not allowed on sequence objects.

不允许对序列对象执行 DELETE 操作。

-8318 This action is not allowed on sequence object.

Only the following operations are allowed on sequence objects:只允许对序列对象执行以下操作：SELECT .[NEXTVAL|CURRVAL] from ;ALTER SEQUENCE DROP SEQUENCE RENAME SEQUENCE GRANT/REVOKE CREATE SYNONYM DROP SYNONYM Check to see whether you have specified any operation that does not belong to this set.

检查是否指定了不属于此集的任何操作。

-8319 Sequence object cannot be used here.

Cannot refer to sequence object's CURRVAL or NEXTVAL in the following cases:在以下情况下不能引用序列对象的 CURRVAL 或 NEXTVAL：WHERE clause of a SELECT/DELETE statement a condition of CHECK constraint SELECT statement with DISTINCT operator, aggregate function, GROUP BY clause, ORDER BY clause and UNION, INTERSECT, or MINUS set operator a fragment expression of CREATE TABLE or ALTER TABLE a VIEW definition DEFAULT clause of CREATE TABLE or ALTER TABLE Check to see whether you attempted any operation in this set.

检查是否尝试在此集中进行任何操作。

-8320 Only SELECT and ALTER are valid priveleges for sequence objects.

Only a subset of Table level privileges are valid for sequence objects.

You can GRANT or REVOKE only SELECT and ALTER privileges.

只有表级别权限的子集对序列对象有效。您可以 GRANT 或 REVOKE 仅 SELECT 和 ALTER权限。

Both these privileges can be granted with the WITH GRANT option.

这两个权限都可以使用 WITH GRANT 选项授予。

-8321 Not owner of sequence object.

Only the owner of the table or a user who has Database Administrator privileges can execute this statement, for example, to drop a sequence object.

Check that the statement names the sequence object you intended. If it does, you will have to get its owner or a DBA to execute this statement. To find out whom to contact, you can query the system catalog as follows:例如，只有表的所有者或具有数据库管理员权限的用户才能执行此语句以删除序列对象。

检查语句是否命名了您想要的序列对象。如果是这样的话，您必须让它的所有者或 DBA来执行这个语句。要找出与谁联系，您可以查询系统目录，如下所示：SELECT tabname, owner FROM systables WHERE tabid > 99;SELECT username FROM sysusers WHERE usertype = 'D'-8322 Remote sequences are not supported currently.

You cannot reference a sequence object on a remote database.

不能引用远程数据库上的序列对象。

Check to see whether you have a reference of type:请检查是否有类型的引用：@:.[NEXTVAL|CURRVAL]-8324 Serial foreign keys should not refer to serial unique keys.

Both the referencing and referenced columns in a referential relationship are SERIAL columns or SERIAL8 columns or BIGSERIAL columns, which the database server does not allow.

引用关系中的引用列和引用列都是数据库服务器不允许的 SERIAL 列或 SERIAL 8 列或BIGSERIAL 列。

Change the referencing columns to be of a nonserial data type.

请将引用列更改为非串行数据类型。

-8328 Write failed. count rows unloaded (check ulimit or disk space).

After writing count lines of output to the unload file, an error occurred trying to write the next line. Look for operating-system messages that might give more information. Possible causes include a full disk or a disk quota limit.

将输出的计数行写入卸载文件后，试图写入下一行时发生错误。寻找可能提供更多信息的操作系统消息。可能的原因包括完整的磁盘或磁盘配额限制。

-8331 Invalid table or view name (%s) in the REFERENCING clause of the CREATE PROCEDURE or CREATE FUNCTION statement.

This error is generated from the CREATE TRIGGER statement when a routine with the REFERENCING clause is called within the action statement with a mismatched table or view name.

当使用不匹配的表或视图名称在 action 语句中调用带有 REFERENCING 子句的例程时，将从 CREATE TRIGGER 语句中生成此错误。

The table or view name in the REFERENCING clause of the CREATE PROCEDURE or CREATE FUNCTION statement should match the triggering table or view name.

CREATE PROCEDURE 或 CREATE FUNCTION 语句的 REFERENCING 子句中的表或视图名称应与触发表或视图名称匹配。

-8332 Only NEW value of the column reference can be modified.

Neither the OLD correlation name nor the table or view name in the REFERENCING clause can be specified in the left hand side of the LET statement in the trigger routine body.

在触发器例程正文的 LET 语句的左侧，既不能指定 REFERENCING 子句中的 OLD 关联名称，也不能指定表或视图名。

Example 1 of error:错误示例 1：CREATE PROCEDURE testproc1()REFERENCING OLD as O NEW as N FOR T;...

LET O.column1 = ; --- error END PROCEDURE;Example 2 of error:错误示例 2：CREATE PROCEDURE testproc2()REFERENCING OLD as O NEW as N FOR T;...

LET T.column1 = ; --- error END PROCEDURE;-8333 Invalid invocation of the routine with referencing clause.

This error is returned in the following cases:在下列情况下将返回此错误：* The routine was created with the REFERENCING clause but was not executed from the trigger action statement.

* 这个例程是用 REFERENCING 子句创建的，但是没有从触发器操作语句中执行。

* The routine was created with the REFERENCING clause but was not executed with the WITH TRIGGER REFERENCES clause.

* 例程是用 REFERENCING 子句创建的，但没有使用 WITH TRIGGER REFERENCES 子句执行。

* The routine was NOT created with the REFERENCING clause and was executed with the WITH TRIGGER REFERENCES clause.

* 例程不是用 REFERENCING 子句创建的，而是用 WITH TRIGGER REFERENCES 子句执行的。

* The routine was created with the REFERENCING clause but was not executed from the FOR EACH ROW trigger action statement.

* 该例程是用引用 REFERENCING 创建的，但没有从 FOR EACH ROW 触发器操作语句中执行。

-8334 REFERENCING clause cannot be used in external routines.

For external routines, using the REFERENCING clause to access the OLD or the NEW values for the column(s) is not valid.

对于外部例程，使用 REFERENCING 子句访问列的旧值或新值无效。

-8335 Usage of the Boolean function (%s) is not valid in this context.

The Boolean functions INSERTING, UPDATING, DELETING and SELECTING are valid for procedures that are executed from trigger action statements.

布尔函数的 INSERTING、UPDATING、DELETING 和 SELECTING 对于从触发器动作语句执行的过程是有效的。

These functions return 't' or 'f' depending on the trigger type.

这些函数根据触发器类型返回‘t’或‘f’。

For Example:例如：Create trigger trig1 INSERT ON tab1 for each row(execute procedure proc1());Create procedure proc1()define i integer;define u integer;if (INSERTING) then LET i = 1;end if if (UPDATING) then LET u = 1;end if end procedure;Execution of the above example will set the variable i to 1 but will not set u to 1 because the created trigger is an insert trigger.

上面示例的执行将变量 i 设置为 1 ，但不会将 u 设置为 1 ，因为创建的触发器是插入触发器。

-8336 Undefined symbol (%s).

The symbol is undefined in the current context. If the error is from CREATE TRIGGER or CREATE PROCEDURE/FUNCTION with REFERENCING clause, check for the misspelling of the OLD or NEW correlation variable names.

符号在当前上下文中未定义。如果错误来自 CREATE TRIGGER 或 CREATE PROCEDURE/FUNCTION with REFERENCING，请检查旧的或新的相关变量名的拼写错误。

-8337 New value of column reference (%s) cannot be modified.

A trigger routine whose REFERENCING clause specifies a view cannot modify the NEW value of any column in that view.

其 REFERENCING 子句指定视图的触发器例程不能修改该视图中任何列的新值。

Example of error:错误示例：CREATE VIEW View1 ...

CREATE PROCEDURE testproc()REFERENCING OLD as O NEW as N FOR View1;...

LET N.column1 = ; --- error END PROCEDURE;Here the REFERENCING clause of a trigger routine declares N as a correlation name for qualifying NEW values of columns in a view. The LET statement is not valid, because a correlation name cannot qualify NEW column values on the left side of LET expressions if the REFERENCING clause specified a view.

这里，触发器例程的 REFERENCING 子句声明 N 为一个相关名称，用于限定视图中列的新值。 LET 语句无效，因为如果 REFERENCING 子句指定视图，关联名称无法限定 LET 表达式左侧的新列值。

The syntax in this example is valid only for LET statements within trigger routines that are invoked (in the FOREACH section of the action clause) by an INSERT or UPDATE trigger on a table, but not for INSTEAD OF triggers on views.

此示例中的语法仅适用于表上的 INSERT 或 UPDATE 触发器调用的触发器例程中的 LET语句(在操作子句的 FOR EACH 部分)，而不是对视图上的触发器。

-8351 Function Invalid input XML document or input XPATH string.

Explanation:The input XML document or XPATH string has illegal characters or the XML document is not well-formed or the XPATH string is not correct.

说明：输入的 XML 文档或 XPATH 字符串有非法字符，或者 XML 文档格式不佳，或者XPATH 字符串不正确。

Action:Supply valid input arguments to the function which is a well-formed XML document or a valid XPATH string.

For Example :select extractvalue(col2, '/customer/personnel/') from tab;The above example has an XPATH string with trailing '/' which is invalid XPATH string. The correct usage would be,select extractvalue(col2, '/customer/personnel') from tab;操作：向函数提供有效的输入参数，该函数是格式良好的 XML 文档或有效的 XPATH 字符串。例如： select extractvalue(col2, '/customer/personnel')from tab; 上面的示例有一个带尾部‘/’的 XPATH 字符串，这是无效的 XPATH 字符串。正确的用法是，select extractvalue(col2, '/customer/personnel') from tab;-8352 Function Empty input XML document.

Explanation:The input arguments, XML document, or XPATH string are passed as empty strings. For example:SELECT extract(col, '') FROM tab;SELECT extractvalue('', '') FROM tab;Action:Supply valid input arguments to the function which is a well-formed XML document or a valid XPATH string.

说明：输入参数、XML 文档或 XPATH 字符串作为空字符串传递。例如：SELECT extract(col, '') FROM tab;SELECT extractvalue('', '') FROM tab;操作：将有效的输入参数提供给作为格式良好的 XML 文档或有效的 XPATH 字符串的函数。

-8353 Function NULL input XML document.

Explanation:The input XML document is passed as NULL.

Action:Supply a well-formed XML document as the input.

说明：输入的 XML 文档作为 NULL 传递。

操作：提供格式良好的 XML 文档作为输入。

-8354 Function Exception received for ICU memory allocation.

Explanation:An exception was received while allocating memory for ICU data structures.

Action:Make sure that the system has enough memory to run the command.

If the problem persists, contact Technical Support to resolve the problem.

说明：在为 ICU 数据结构分配内存时，收到了异常。

操作：确保系统有足够的内存来运行命令。如果问题仍然存在，请与技术支持联系以解决问题。

-8355 Function Error parsing the input XML document.

Explanation:The input XML document for is not a well-formed XML string. For example:SELECT idsxmlparse('John') from tab;The input XML string is not a well formed XML string in this case because it is missing a tag.

Action:Supply a well-formed XML document as the input.

For example:SELECT idsxmlparse('John') from tab;说明：为输入的 XML 文档不是格式良好的 XML 字符串。例如：SELECT idsxmlparse('John') from tab;在本例中，输入xml字符串不是格式良好的xml字符串，因为它缺少标签。

操作：提供一个格式良好的XML文档作为输入。例如：SELECT idsxmlparse('John') from tab;-8356 Function Returned multiple nodes for the query.

Explanation:The function returned more than one node.

Action:Modify the function so that only one node is returned.

说明：函数返回一个以上的节点。

操作：修改函数以便只返回一个节点。

-8357 Function Out of memory exception.

Explanation:The database server needed to allocate memory in order to process the query, but none was available.This error might reflect a hardware limit, an operating-system configuration limit, or a temporary shortage of space.

Action:Try the query again after a delay. If it still fails, consult your system administrator. If possible, revise your query to join fewer tables, to order or group on fewer columns, or to operate in two or more separate statements. On DOS systems, exit to the operating-system command line, free some disk space or reduce the complexity of your program, and resubmit the program.If the problem persists, contact Technical Support to resolve the problem.

说明：数据库服务器需要为处理查询分配内存，但没有可用，此错误可能反映了硬件限制、操作系统配置限制或临时空间不足。操作：延迟后再尝试查询。如果仍然失败，请咨询系统管理员。如果可能的话，修改查询以加入更少的表，对更少的列进行排序或分组，或者在两个或多个单独的语句中操作。在 DOS 系统上，退出操作系统命令行，释放一些磁盘空间或降低程序的复杂性，然后重新提交程序。如果问题仍然存在，请与技术支持联系以解决问题。

-8358 Function Connection Open Failed.

Explanation: The open connection call failed while running the function.

Action:Rerun the application. Make sure server is running and there is no error messages in server log file. If the problem persists,contact Technical Support to resolve the problem.

说明：打开的连接调用在运行函数时失败。

-8359 Function Error allocating temporary clob file.

Explanation:The server was unable to allocate enough memory for allocating a temporary clob file while running the function .

Action:Make sure that the system has enough memory to run the command.

If the problem persists, contact Technical Support to resolve the problem.

说明：服务器无法分配足够的内存，以便在运行函数时分配临时clob 文件。

操作：确保系统有足够的内存来运行命令。如果问题仍然存在，请与技术支持联系以解决问题。

-8360 Function Large Object spec init failed.

Explanation:The server failed to open large object specification init structure while running the function .

Action:Make sure that the system has enough memory to run the command.

If the problem persists, contact Technical Support to resolve the problem.

说明：服务器在运行函数时未能打开大型对象规范 init 结构。

操作：确保系统有足够的内存来运行命令。如果问题仍然存在，请与技术支持联系以解决问题。

-8361 Function Failed to create a large object.

Explanation:The server failed to create a smart large object while running the function .

Action:Make sure that the system has enough memory to run the command.

If the problem persists, contact Technical Support to resolve the problem.

说明：服务器在运行函数时未能创建智能大对象。

操作：确保系统有足够的内存来运行命令。如果问题仍然存在，请与技术支持联系以解决问题。

-8362 Function Failed to write to a large object.

Explanation:The server failed to write to an open smart large object while running the function .

Action:Make sure that the system has enough memory to run the command.

If the problem persists, contact Technical Support to resolve the problem.

说明：服务器在运行函数时未能写入打开的智能大对象。

操作：确保系统有足够的内存来运行命令。如果问题仍然存在，请与技术支持联系以解决问题。

-8363 Function Null argument to function.

Explanation:One or more of the arguments that were passed to the function is null.

Action:Contact Technical Support to resolve the problem.

说明：传递给函数的一个或多个参数为 NULL。

：联系技术支持部门解决问题。

-8364 Function Null buffer passed Explanation:The state buffer that is used for storing XML output is null.

Action:Verify that system has enough memory.Contact Technical Support to resolve the problem.

说明：用于存储 XML 输出的状态缓冲区为 NULL 。

操作：确认系统有足够的内存。联系技术支持解决问题。

-8365 Function Null row descriptor Explanation:The row descriptor information in the argument was null.

Action:Contact Technical Support to resolve the problem.

说明：参数中的行描述符信息为空。

：联系技术支持部门解决问题。

-8366 Function Null type ID Explanation:The row descriptor type ID is null.

Action:Contact Technical Support to resolve the problem.

说明：行描述符 ID 为 NULL。

：联系技术支持部门解决问题。

-8367 Function Null type descriptor Explanation:The descriptor of row descriptor type descriptor is null.

Action:Contact Technical Support to resolve the problem.

说明：行描述符类型描述符的描述符为空。

：联系技术支持部门解决问题。

-8368 Function Buffer size exceeds maximum size Explanation:The output of must be less than 32739 bytes.

Action:If the combined size of output records exceeds 32739 bytes,one need to use a clob function.

说明：的输出必须小于 32739 字节。

操作：如果输出记录的合并大小超过 32739 字节，则需要使用 clob 函数。

-8369 Function Memory allocation for internal buffer failed Explanation:Function was not able to allocate more memory.

Action:Make sure that the system has enough memory to run the command.

If the problem persists, contact Technical Support to resolve the problem.

说明：函数无法分配更多内存。

操作：确保系统有足够的内存来运行命令。如果问题仍然存在，请与技术支持联系以解决问题。

-8370 Function init failed Explanation:clob function for init has failed.

Action:Contact Technical Support to resolve the problem.

说明：init的 clob 函数失败。

：联系技术支持部门解决问题。

-8371 Function create failed Explanation:clob function for create has failed.

Action:Contact Technical Support to resolve the problem.

说明：创建的 clob 函数失败。

：联系技术支持部门解决问题。

-8372 Function stat failed Explanation:clob function for getting status has failed.

Action:Contact Technical Support to resolve the problem.

说明：获取状态的 clob 函数失败。

：联系技术支持部门解决问题。

-8373 Function stat size failed Explanation:clob function for getting size status has failed.

Action:Contact Technical Support to resolve the problem.

说明：获取大小状态的 clob 函数失败。

：联系技术支持部门解决问题。

-8374 Function write with seek failed Explanation:clob function for write with seek has failed.

Action:Contact Technical Support to resolve the problem.

说明：用查找写写的 clob 函数失败。

：联系技术支持部门解决问题。

-8375 Function General exception.

Explanation:Function received a general exception during execution.

Action:Contact Technical Support to resolve the problem.

说明：函数在执行过程中收到了一般的异常。

：联系技术支持部门解决问题。

-8376 Function null input large object handle.

Explanation:A null input large object handle was passed as an input XML string for function .

Action:Supply a valid smart large object handle.

For example ,consider a table tab :create table tab(col1 int, col2 clob);Clob data can be inserted as,INSERT INTO tab values(1, filetoclob("data.xml", "client"));where "data.xml" is XML string document. The column tab.col2 can be used as input large object handle to function .

说明：空输入大对象句柄作为函数的输入 xml 字符串传递。

操作：提供一个有效的智能大对象句柄。例如，考虑一个表选项卡：create table tab(col1 int, col2 clob);clob 数据可以作为如下插入：INSERT INTO tab values(1, filetoclob("data.xml", "client"));其中“data.xml”是 XML 字符串文档。tab.col2 列可以用作函数的输入大对象句柄。

-8377 Function failed because the first argument is too long.

Explanation: The length of the first argument in the function is larger than the maximum allowed length.

Action: Run the function again with a first argument that is less than or equal to the maximum allowed length.

说明：函数中第一个参数的长度大于允许的最大长度。

操作：使用小于或等于最大允许长度的第一个参数再次运行该函数。

-8378 Function failed because the second argument is too long.

Explanation: The length of the second argument in the function is larger than the maximum allowed length.

Action: Run the function again with a second argument that is less than or equal to the maximum allowed length.

说明：函数中第二个参数的长度大于允许的最大长度。

操作：使用小于或等于最大允许长度的第二个参数再次运行该函数。

-9001 Only columns of type CHARACTER may be subscripted or printed without trailing blanks.

Either you attempted to subscript or apply the CLIPPED function to a noncharacter variable, or you specified a variable to have the wrong data type.

您可以尝试下标或将 CLIPPED 函数应用于非字符变量，也可以指定一个变量以获得错误的数据类型。

-9002 An unknown operation code was found in the PMIM.

An internal ACEGO error occurred. Make sure that a version of ACEPREP at the same version level as ACEGO compiled your report. If that is the case, recompile the report to make sure that the .arc file is not corrupted. If the error recurs, note all circumstances and contact GBase Technical Support.

发生了内部 ACEGO 错误。确保 ACEPREP 的版本与 ACEGO 编译报告的版本相同。如果是这种情况，请重新编译报告，以确保 .arc 文件没有损坏。如果错误再次发生，请注意所有情况，并与 GBase 技术支持部门联系。

-9003 A USING format string may contain only one '.'.

The format string that specifies the display of a number contains more than one decimal point. Remove all but one of the decimal points. Refer to the discussion of the USING function in the reference manual.

指定数字显示的格式字符串包含多个小数点。删除一个小数点以外的所有小数点。参考手册中关于 USING 函数的讨论。

-9004 The column name is not in the current table, or the user variable name has not been defined.

The name that is shown cannot be related to either a column in a database table or a defined variable. Check its spelling. If you meant it to be a variable, add it in the DEFINE section. If you meant to name a column in the database, check to see if the table was altered or its columns were renamed.

所显示的名称不能与数据库表中的列或定义的变量相关联。检查它的拼写。如果您希望它是一个变量，那么将其添加到 DEFINE 部分。如果要在数据库中命名列，请检查表是否已更改或其列是否被重命名。

-9014 Usage: SACEGO [-q][-d database] report-filename.

Flags:标志：-q SACEGO will not print any messages or errors.

-q SACEGO 不会打印任何消息或错误。

-d SACEGO will use the database name that follows the -d option instead of the database name that is specified in the DATABASE section of the report specification.

-d SACEGO 将使用 -d 选项后面的数据库名称，而不是报表规范的数据库部分中指定的数据库名称。

This message displays when ACEGO is not given appropriate command-line arguments. Other messages might explain it explicitly. You can use the-s option, as the manual describes, in place of -q as shown in the message; they have the same effect.

当 ACEGO 未被赋予适当的命令行参数时，此消息将显示。其他消息可能会显式地解释它。您可以使用 -s 选项（如手册所描述的那样）来代替消息中所示的 -q ；它们具有相同的效果。

-9025 The column name is not in the current table. Any column used as an ORDER BY column must be in the current table.

The name that is displayed appears after the words ORDER BY, but it is not the name of a column or the display label of an expression that is selected in this statement.

显示的名称出现在单词 ORDER BY 之后，但在此语句中选择的不是列的名称或表达式的显示标签。

-9046 The report output file filename could not be opened. This is probably due to permissions.

The report was directed to the destination shown, either with a REPORT TO statement or through the contents of the DBPRINT environment variable. Make sure that the destination was spelled correctly. Verify that your account has operating-system permissions to write the destination file and that the destination disk is writable and not full.

该报告被定向到显示的目标，或者使用 REPORT TO 语句，或者通过 DBPRINT 环境变量的内容。确保目标拼写正确。验证您的账户是否具有写入目标文件的操作系统权限，以及目标磁盘是否可写入且未满。

-9047 The output file filename could not be created.

Probably your account does not have write permission in that directory,the disk is full, or you have exceeded a limit on open files.

可能您的账户在该目录中没有写权限，磁盘已满，或者您已超出打开文件的限制。

-9048 The pipe pipe-specification could not be opened.

The report was directed to the pipe that is shown in the REPORT TO statement. Make sure that all program names in it are spelled correctly, that the programs exist, and that they are on the current execution path. Look for other messages from the operating system that might indicate the source of trouble (for example, a message that indicates not enough system memory was available).

报告指向 REPORT TO 语句中所显示的管道。确保其中的所有程序名拼写正确，程序存在，并且它们位于当前执行路径上。查找来自操作系统的其他可能指示故障来源的消息（例如，指示系统内存不足的消息）。

-9049 A value entered as a command line parameter cannot be converted to the data type type.

A PARAMETER statement in the DEFINE section defines one of the values from the command line as having data type type. However, the value that is given on the command line cannot be converted to that type. Check the following points:DEFINE 部分中的 PARAMETER 语句将命令行中的一个值定义为具有数据类型。但是，不能将命令行上的值转换为该类型。检查以下要点：* If type is numeric, check that the parameter can be read as a number.

* 如果类型为数字，请检查参数是否可以读取为数字。

* If type is MONEY, the parameter should nevertheless not include a currency symbol.

* 如果类型是 MONEY，则参数不应包括货币符号。

* If type is CHARACTER or VARCHAR, check that the parameter is not longer than the length that is defined for the variable.

* 如果类型为 CHARACTER 或 VARCHAR，请检查参数是否大于为变量定义的长度。

* If type is DATETIME, check that the parameter is correctly punctuated (refer to the information on DATETIME and INTERVAL data in the user guide).

* 如果类型为 DATETIME，请检查参数是否被正确标点(请参阅用户指南中有关DATETIME 和 INTERVAL 的信息)。

* If type is DATE, check that the parameter is correctly punctuated as a date.

* 如果类型为 DATE，请检查参数是否被正确标点符号为日期。

Correctly punctuated DATE, DATETIME and INTERVAL values contain characters that might have special meaning to the operating system. The problem might be that the parameter was correct but needed quotes around it to protect it.

正确标点的 DATE、DATETIME 和 INTERVAL 值包含可能对操作系统具有特殊意义的字符。

问题可能是，参数是正确的，但需要引号来保护它。

-9050 The user variable name is of type type. The value entered is out of range or cannot be converted to that type.

A value was entered in response to a PROMPT statement, which stores the value in a variable of the name and type shown. However, it was impossible to convert the entered value to the data type of the variable (see the discussion of error -9049 for details on conversion).

Rerun the report and enter appropriate data (also consider revising the prompt string to better guide the user).

输入一个值响应 PROMPT 语句，该语句将该值存储在所示名称和类型的变量中。但是，不可能将输入的值转换为变量的数据类型（有关转换的详细信息，请参阅对 Error-9049 的讨论）。重新运行报告并输入适当的数据（还考虑修改提示字符串以更好地指导用户）。

-9051 The number of defined parameters in the ACE program does not equal the number of actual parameters passed to ACEGO on the command line.

The number of parameters that are defined using PARAMETER statements in the DEFINE section does not agree with the number of items that are given as parameters on the command line. Check that parameters that contain spaces or other special characters are enclosed in quotes; the lack of quotes can cause a single parameter to be taken as more than one.

使用 DEFINE 部分中的 PARAMETER 语句定义的参数与命令行中作为参数给定的项数不一致。检查包含空格或其他特殊字符的参数是否用引号括起来；缺少引号会导致单个参数被视为多个参数。

-9052 The format string is too large. It may not be larger than 79 characters.

A limit exists on the size of the format string that is presented to the USING function.

显示给 USING 函数的格式字符串的大小存在限制。

-9053 An unknown entry in the .arc file has been detected. Recompile your ACE report specification using SACEPREP and then rerun SACEGO. Be certain that the version numbers for SACEPREP and SACEGO are identical.

The versions of ACEPREP and ACEGO must agree. (To check the version of either program, run it from the command line with the -v option.) To recompile the report, use a version of the compiler, ACEPREP, that is identical to the version of the runner, ACEGO. If the versions are already the same, recompile the report anyway to ensure that the .ace file has not been corrupted. If the error recurs, note all circumstances and contact GBase Technical Support.

ACEPREP 和 ACEGO 的版本必须达成一致。（要检查这两个程序的版本，请使用 -v 选项从命令行运行它。）若要重新编译报表，请使用编译器 ACEPREP 的版本，该版本与运行程序 ACEGO 的版本相同。如果版本已经相同，那么无论如何都要重新编译报告，以确保.ace 文件没有损坏。如果错误再次发生，请注意所有情况，并与 GBase 技术支持部门联系。

-9054 The ACE report was compiled by version A compiler. This runner can only run 5 through B. Recompile your ACE report specification using SACEPREP and then rerun SACEGO.

-9055 The compiled report file filename could not be found or opened.

The report filename was named on the ACEGO command line. It expects to locate the file filename.arc in the current directory or a path that the DBPATH environment variable names, but it could not find the file or could not open it for reading. Check that the filename was spelled correctly and that your account has read access to it.

报告文件名在 ACEGO 命令行上命名。它希望在当前目录或 DBPATH 环境变量名称的路径中找到文件 filename.arc，但是它找不到该文件，或者无法打开它进行读取。检查文件名是否拼写正确，并且您的账户是否有读取访问权限。

-9059 A select statement which is not the final select statement in an ACE report must select into a temporary table.

The SELECT section of the report can contain more than one SELECT statement. However, only the last one of these statements can produce the rows that are the report contents. The preceding SELECT statements are used to prepare data in temporary tables that the final statement delivers to the report. Change the report specification so that all but the last SELECT statement contain INTO TEMP clauses.

报表的 SELECT 部分可以包含多个 SELECT 语句。但是，只有最后一条语句才能生成作为报表内容的行。前面的 SELECT 语句用于在临时表中准备最后语句传递给报表的数据。更改报表规范，以便除最后一条 SELECT 语句外，所有语句都包含 INTO TEMP 子句。

-9060 The values m and n used to subscript name are outside the bounds for the column's defined length.

A column substring in the ORDER BY clause is incorrect. When taking a substring of a column, the first number in brackets specifies the position of the first character, and the second number specifies the position of the last character of the substring. Both numbers must be at least 1 and not greater than the total length of the column or variable.

ORDER BY 子句中的列子字符串不正确。当取列的子字符串时，括号中的第一个数字指定第一个字符的位置，第二个数字指定子字符串的最后一个字符的位置。这两个数字必须至少为 1 ，且不大于列或变量的总长度。

-9061 A 'SELECT INTO' statement cannot be executed as the last select statement in an ACE report.

The SELECT section of the report can contain more than one SELECT statement. The last (or only) one of these statements must produce the rows that are the contents of the report. Any preceding SELECT statements are used to prepare data in temporary tables that the final statement delivers to the report. Change the report specification so that all but the last SELECT statement contain INTO TEMP clauses.

报表的 SELECT 部分可以包含多个 SELECT 语句。这些语句中的最后一条（或唯一一条）必须生成作为报表内容的行。前面的任何 SELECT 语句都用于在临时表中准备最后语句传递给报表的数据。更改报表规范，以便除最后一条 SELECT 语句外，所有语句都包含INTO TEMP 子句。

-9062 An error has occurred during the conversion of a numeric value to a CHARACTER type user variable. The CHARACTER type variable is not long enough to hold the result.

The conversion of a numeric value to character produced more numeric characters than the destination could hold. Rather than truncate the result, ACEGO stops with an error. You can either redefine the destination variable, or you can limit the size of the converted value(for example, with a USING format string).

将数值转换为字符会产生比目标所能容纳的更多的数字字符。ACEGO 没有截断结果，而是以错误结束。可以重新定义目标变量，也可以限制转换值的大小（例如， USING 格式字符串)。

-9063 The user function name, defined by the user in the DEFINE statement of ACE, could not be found in the C function definition table userfuncs in the user's C static data area.

The DEFINE section of the report contains a FUNCTION statement indicating that an external function name would be linked with the report. (The ESQL/C manual covers the use of external C functions with ACE reports and PERFORM screens.) However, the name and address of each such function must appear in a static array that is named userfuncs.

That array, along with the computer code of the external functions, is linked with a custom version of ACEGO. Because name did not appear in the array, ACEGO cannot call it.

报告的“定义”部分包含一个 FUNCTION 语句，指示将与报告链接外部函数名。（ESQL/C手册涵盖了外部 C 函数与 ACE 报告和 PERFORM 屏幕的使用。）但是，每个这样的函数的名称和地址必须出现在一个名为 userfuncs 的静态数组中。该数组与外部函数的计算机代码一起与 ACEGO 的自定义版本链接。因为数组中没有出现名称，所以 ACEGO 无法调用它。

Check that you are executing the correct, customized version of ACEGO(the original version of the program has no external functions linked to it). Check to see if name is correctly spelled. Then examine the source of the C functions to make sure that the userfuncs array is defined correctly and that it contains an entry for name.

请检查是否正在执行正确的自定义版本的 ACEGO （程序的原始版本没有与其链接的外部功能）。检查名称是否拼写正确。然后检查C函数的源，以确保正确定义了 userfuncs 数组，并确保它包含一个名称条目。

-9064 The run-time string table is full. No more memory can be allocated.

The data space available for temporary character strings is full.

Temporary strings are built when calling external C functions and when processing the USING, SPACE, and ASCII built-in functions. Reduce the use of these items.

临时字符串可用的数据空间已满。临时字符串是在调用外部 C 函数和处理 USING、SPACE和 ASCII 内置函数时生成的。减少使用这些项目。

-9065 Memory allocation has failed.

ACEGO was unable to allocate memory to hold a row, a line, or an SQL data structure. The space needed is not (as the message text suggests)directly related to the size of the report specification. The report lacks only a few thousand bytes, at most, to run.

ACEGO 无法分配内存以容纳行、行或 SQL 数据结构。所需的空间（如消息文本所示）与报表规范的大小没有直接关系。报告最多只缺少几千字节即可运行。

-9066 An error has occurred while writing to the output report.

The report destination was opened correctly, but the operating system reported an error while output was being written. Look for error messages from the operating system that explain the problem. The most common cause of the error is lack of available disk space.

报表目标正确打开，但操作系统在编写输出时报告了一个错误。从解释问题的操作系统中查找错误消息。错误最常见的原因是缺乏可用的磁盘空间。

-9067 ACEs arithmetic stack has exceeded its bounds. The expression here is too complicated.

Reduce the complexity of the arithmetic expression. For example, divide the expression into subexpressions and assign the values of each to a variable.

降低了算法表达式的复杂度。例如，将表达式划分为子表达式，并将每个表达式的值赋值给变量。

-9068 An SQL statement has been found in the SELECT section that is not a SELECT statement. Only SELECT statements or SELECT statements that create temporary tables are allowed in the SELECT section.

Possibly the word SELECT is misspelled in the report specification. If you intentionally wrote another SQL statement such as UPDATE or INSERT,remove it; only SELECT statements are permitted in reports. (You can execute other SQL statements in a C function that is called from a report. The ESQL/C manual discusses linking external C functions with reports.)可能在报表规范中单词 SELECT 拼写错误。如果有意编写另一条 SQL 语句，如 UPDATE或 INSERT，则删除它；报表中只允许 SELECT 语句。(可以在从报表调用的 C 函数中执行其他 SQL 语句。ESQL/C 手册讨论了将外部 C 函数与报表连接起来的问题。)-9070 A record in the flat ascii input file contains more data fields than what was specified in the DEFINE ASCII statement of the report.

A field in the ASCII file is a sequence of zero or more characters that ends in a delimiter character (the delimiter is specified in the READ statement). Effectively, as many fields as delimiter characters exist in each record. The number of fields must be the same in each record,and each field must be defined in an ASCII statement in the DEFINE section of the report. Extra fields are not ignored. Look for message-9072; it can help you locate the record in error.

ASCII 文件中的字段是以分隔符字符结尾的零个或多个字符的序列(分隔符是在 READ 语句中指定的)。实际上，每个记录中都存在许多作为分隔符字符的字段。每个记录中的字段数必须相同，每个字段必须在报表的 DEFINE 部分的 ASCII 语句中定义。额外的字段不会被忽略。查找信息 -9072 ；它可以帮助您找到错误的记录。

-9071 A record in the flat ascii input file contains less data fields than what was specified in the DEFINE ASCII statement of the report.

A field in the ASCII file is a sequence of zero or more characters that ends in a delimiter character (the delimiter is specified in the READ statement). Effectively, as many fields as delimiter characters exist in each record. The number of fields must be the same in each record,and each field must be defined in an ASCII statement in the DEFINE section of the report. No default exists for missing fields. Look for message -9072; it can help you locate the record in error.

ASCII 文件中的字段是以分隔符字符结尾的零个或多个字符的序列（分隔符是在 READ语句中指定的)。实际上，每个记录中都存在许多作为分隔符字符的字段。每个记录中的字段数必须相同，每个字段必须在报表的 DEFINE 部分的 ASCII 语句中定义。缺少字段不存在默认设置。查找信息 -9072；它可以帮助您找到错误的记录。

-9072 The count records from the ascii input file have been read in.

This informational message helps you locate the source of a problem in the ASCII input file. The problem that is described in another message was found in the count line of the file.

此信息消息帮助您在 ASCII 输入文件中找到问题的来源。在文件的计数行中发现了另一条消息中描述的问题。

-9140 An attempt was made to divide by zero on line number. The result was set to zero.

An expression on line number of the report-specification file contains a division operation. At some point in the report run, the divisor in the expression was zero. Examine the expression and the data it uses and write the report so that division by zero will not occur (for example, by testing for zero in an IF statement). This error can result from applying an aggregate function to a defined variable before the first row of data is processed. To avoid this situation, make sure that any variable has a value before it is used (for example, by setting it from a command-line parameter or with a PROMPT FOR statement).

报告规范文件的行号上的表达式包含一个除法操作。在报告运行的某个时候，表达式中的除数为零。检查表达式及其使用的数据，并编写报告，以便不会发生零除法（例如，在IF 语句中测试零）。在处理第一行数据之前，将聚合函数应用于定义的变量可能会导致此错误。为了避免这种情况，请确保在使用变量之前任何变量都有一个值（例如，通过命令行参数或使用 PROMPT FOR 语句来设置它）。

-9142 Date conversion error.

ACEGO is trying to convert from characters into a DATE data type but found an error. Either the date is not punctuated correctly, unwanted nonnumeric characters are present, or the date itself is inconsistent(for example, "01/32/91").

ACEGO 试图将字符转换为 DATE 数据类型，但发现了一个错误。要么日期没有正确标点符号，要么出现了不需要的非数字字符，或者日期本身不一致(例如，“01/32/91”)。

-9143 Character, Text, and Byte data cannot be printed with using formats.

The USING function can only be applied to numeric data. Revise the report specification.

USING 函数只能应用于数字数据。修改报告规范。

-9200 Purpose routine (am_xxx) is not yet supported with JVTI.

Your JVTI code included a purpose method that is not supported in this release. am_xxx can be any of the following unsupported methods: am_delete, am_insert, am_update, am_check, am_truncate,or am_stats.

您的 JVTI 代码包含了在此版本中不受支持的目的方法。am_xxx 可以是下列任何不受支持的方法：am_delete、am_insert、 am_update、 am_check、am_truncate 或am_stats。

-9201 Secondary access_method with Java am_purpose routine is not supported.

You attempted to create a secondary access_method with Java-Language User Defined Routines. Secondary access_methods are not supported in Java technology.

您试图使用 Java 语言用户定义的例程创建一个辅助 access_method 。Java 技术不支持辅助 access_method 。

To create a secondary access_method, you must use the C language User Defined Routines. For more information, see the Virtual-Index Interface Programmer's Guide.

要创建辅助 access_method ，必须使用 C 语言用户定义的例程。有关更多信息，请参见虚拟索引界面程序员指南。

-9202 JVTI only supports external am_sptype in this release.

Your CREATE PRIMARY ACCESS_METHOD SQL statement specified an am_sptype value other than "X". JVTI allows you to address only extspace (not sbspace or dbspace) data storage.

您的 CREATE PRIMARY ACCESS_METHOD SQL 语句指定了“X”以外的 am_sptype 值。JVTI允许您只访问 extspace （而不是 sbspace 或 dbspace ）数据存储。

Use the ALTER ACCESS_METHOD SQL statement to change am_sptype to 'X'.

使用 ALTER ACCESS_METHOD SQL 语句来把 am_sptype 改成 'X'。

-9250 Xadatasource type datasource_type_name already exists in database.

The xadatasource type that you are creating with CREATE XADATASOURCE TYPE statement already exists. You must use a new name.

用 CREATE XADATASOURCE TYPE 语句创建的 xadatasource 类型已经存在。你必须使用一个新的名字。

-9251 Xadatasource datasource_name already exists in database.

The xadatasource that you are creating with a CREATE XADATASOURCE datasource_name USING statement already exists. You must use a new name.

用 CREATE XADATASOURCE datasource_name USING 语句创建的 xadatasource 已经存在。你必须使用一个新的名字。

-9252 Xadatasource type datasource_type_name not found.

The datasource_type_name you are trying to drop with DROP XADATASOURCE TYPE datasource_type_name statement does not exist. Use the correct datasource_type_name.

要使用 DROP XADATASOURCE TYPE 语句删除的 datasource_type_name 不存在。使用正确的 datasource_type_name。

-9253 Xadatasource datasource_name not found.

The datasource_name DROP XADATASOURCE datasource_name does not exist.

Use the correct name.

datasource_name DROP XADATASOURCE datasource_name 不存在。请使用正确的名称。

-9254 Improper purpose function used for xadatasource type.

A purpose routine used with the CREATE XADATASOURCE TYPE type_name statement is improper. It might be spelled incorrectly. Otherwise, it is used incorrectly in combination with the other purpose routines, or it is a purpose routine is not appropriate for the xadatasource type. Correct the spelling of the purpose routine or change one or more of the purpose routines until the combination of purpose routines is valid.

与 CREATE XADATASOURCE TYPE type_name 语句一起使用的目的例程是不正确的。可能拼错了。否则，它与其他目的例程组合使用不正确，或者它是一个不适合 xadatasource 类型的目的例程。纠正目的例程的拼写，或更改一个或多个目的例程，直到目的例程组合有效为止。

Example: CREATE XADATASOURCE TYPE xads_t1(xa_flags = 1,xa_version = 0,xa_open = xa2pc_open,xa_start = xa2pc_start,xa_close = xa2pc_close,xa_end = xa2pc_end,xa_rollback = xa2pc_rollback,xa_prepare = xa2pc_prepare,xa_commit = xa2pc_commit,xa_recover = xa2pc_recover,xa_forget = xa2pc_forget,xa_complete = xa2pc_complete);例如: CREATE XADATASOURCE TYPE xads_t1(xa_flags = 1,xa_version = 0,xa_open = xa2pc_open,xa_start = xa2pc_start,xa_close = xa2pc_close,xa_end = xa2pc_end,xa_rollback = xa2pc_rollback,xa_prepare = xa2pc_prepare,xa_commit = xa2pc_commit,xa_recover = xa2pc_recover,xa_forget = xa2pc_forget,xa_complete = xa2pc_complete);-9255 Duplicate purpose function used for xadatasource type.

A purpose routine used with the CREATE XADATASOURCE TYPE datasource_type_name statement has been used more than once. Change the purpose routines used until no duplicates exist.

与 CREATE XADATASOURCE TYPE datasource_type_name 语句一起使用的目的例程已不止一次使用。更改使用的目的例程，直到不存在重复项为止。

-9256 Required purpose function is was not used for the xadatasource type.

A required purpose routine has not been used with the CREATE XADATASOURCE TYPE datasource_type_name statement. Change the purpose routines used until the required purpose routines are included or preserved.

CREATE XADATASOURCE TYPE datasource_type_name 语句没有使用所需的目的例程。更改所使用的目的例程，直到包含或保留所需的目的例程为止。

Example: CREATE XADATASOURCE TYPE xads_t1(xa_flags = 1,xa_version = 0,xa_open = xa2pc_open,xa_start = xa2pc_start,xa_close = xa2pc_close,xa_end = xa2pc_end,xa_rollback = xa2pc_rollback,xa_prepare = xa2pc_prepare,xa_commit = xa2pc_commit,xa_recover = xa2pc_recover,xa_forget = xa2pc_forget,xa_complete = xa2pc_complete);例如: CREATE XADATASOURCE TYPE xads_t1(xa_flags = 1,xa_version = 0,xa_open = xa2pc_open,xa_start = xa2pc_start,xa_close = xa2pc_close,xa_end = xa2pc_end,xa_rollback = xa2pc_rollback,xa_prepare = xa2pc_prepare,xa_commit = xa2pc_commit,xa_recover = xa2pc_recover,xa_forget = xa2pc_forget,xa_complete = xa2pc_complete);-9257 Improper value used for purpose function for xadatasource type.

A purpose routine has been used with an improper value in a CREATE XADATASOURCE TYPE datasource_type_name statement. Use the proper type of value for the purpose routine.

在 CREATE XADATASOURCE TYPE datasource_type_name 语句中，使用了一个目的例程和一个不正确的值。使用适当类型的值作为目的例程。

-9258 Not an owner of xadatasource type or DBA.

The user executing a DROP XADATASOURCE TYPE statement is not authorized because the user is not the owner of the xadatasource type or does not have DBA privileges.

没有授权执行 DROP XADATASOURCE TYPE 语句的用户，因为用户不是 xadatasource 类型的所有者，或者没有 DBA 权限。

-9259 Not an owner of xadatasource or DBA.

The user executing a DROP XADATASOURCE statement is not authorized because the user is not the owner of the xadatasource type or does not have DBA privileges.

没有授权执行 DROP XADATASOURCE 语句的用户，因为该用户不是 xadatasource 类型的所有者，或者没有 DBA 权限。

-9260 Cannot drop xadatasource type (type_name) that is still in use.

An xadatasource type cannot be dropped while it is in use. Be sure that no xadatasource is defined using type_name.

当 xadatasource 类型正在使用时，不能删除它。确保没有使用 type_name 定义xadatasource 。

-9261 Cannot drop xadatasource (name) that is still in use.

An xadatasource cannot be dropped while it is in use. Be sure that name is currently not registered in the transaction.

在使用时，不能删除 xadatasource 。确保该名称当前未在事务中注册。

-9262 Error [err] indicated by an xadatasource purpose function.

An error occurred when an attempt was made to execute an xadatasource purpose routine. For more information, refer to the accompanying XA error code.

试图执行 xadatasource 目的例程时发生错误。有关更多信息，请参阅所附 XA 错误代码。

-9263 Can't execute CREATE/DROP XADATASOURCE statements in non logging database.

'CREATE XADATASOURCE TYPE', 'CREATE XADATASOURCE', 'DROP XADATASOURCE TYPE' and'DROP XADATASOURCE' statements are for trasactional support for external datasources. Non logging databases do not support transactions and therefore these statements cannot be executed in non logging database.

'CREATE XADATASOURCE TYPE'、'CREATE XADATASOURCE'、'DROP XADATASOURCE TYPE' 和'DROP XADATASOURCE' 语句用于外部数据源的事务处理支持。非日志数据库不支持事务，因此不能在非日志数据库中执行这些语句。

-9265 Invalid xadatasource name.

The xadatasource name passed as argument is invalid. The valid format for the xadatasource name is 'xadatasourcename' or 'owner.xadatasourcename'.

作为参数传递的 xadatasource 名称无效。xadatasource 名称的有效格式是“xadatasourcename”或“owner.xadatasourcename”。

-9266 Not in a transaction.

The database server cannot register or unregister xadatasource instance because no transaction is active in the current session. In order to register or unregister an xadatasource instance, you must start a transaction.

数据库服务器无法注册或取消注册 xadatasource 实例，因为当前会话中没有活动的事务。为了注册或取消注册 xadatasource 实例，您必须启动一个事务。

-9267 Xadatasource name is not present in the database.

The xadatasource name is not present in the current database. Check the name of the xadatasource; it might be spelled incorrectly. Otherwise create the xadatasource name.

当前数据库中不存在 xadatasource 名称。检查 xadatasource 的名称；它可能拼写错误。否则，创建 xadatasource 名称。

-9268 Xadatasource name is not registered in the transaction.

The xadatasource name is not registered in the transaction; xadatasource has to be registered before it can be unregistered.

xadatasource 名称未在事务中注册；xadatasource 必须在未注册之前注册。

-9269 xa_open purpose function of xadatasource has returned an error.

The xa_open purpose function of xadatasource has returned an error.

In order to register the xadatasource instance, xa_open needs to be Successful (i.e. it needs to return XA_OK).

xadatasource 的 xa_open purpose 函数返回了一个错误。为了注册 xadatasource实例，xa_open 需要成功（即它需要返回 XA_OK）。

-9270 Type <opaque_type_name> is unsupported in distributed queries.

The type <opaque_type_name> is unsupported in distributed queries.

The type <opaque_type_name> cannot be used in queries that access more than one database.

<opaque_type_name> 类型在分布式查询中不支持。

<opaque_type_name> 类型不能用于访问多个数据库的查询。

Modify the query not to use the <opaque_type_name> data type.

修改查询，使其不使用 <opaque_type_name> 数据类型。

-9271 Type <opaque_type_name> is not identically defined in all the databases used in the distributed queries.

The attributes of the user-defined data type <opaque_type_name> are different on the local and remote databases. A UDT used in a distributed queries must have the same attributes and type hierarchy in all databases accessed by the query.

在本地数据库和远程数据库上，用户定义的数据类型 <opaque_type_name> 的属性是不同的。在分布式查询中使用的UDT必须在查询所访问的所有数据库中具有相同的属性和类型层次结构。

Examine the definition of the <opaque_type_name> UDT in both your local and remote databases. Modify one or both of the UDTs so that they are the same.

请检查本地和远程数据库中 <opaque_type_name> UDT 的定义。修改一个或两个UDT，使它们是相同的。

-9272 The data type <type_name> is not supported for current client/server configuration.

The data type <type_name> is not supported for current client version.

Modify the query not to use the <type_name> data type or upgrade client version.

当前客户端版本不支持 <type_name> 数据类型。修改查询以不使用<type_name> 数据类型或升级客户端版本。

-9273 Cannot create duplicate table table-name.

In a non-ANSI database, table names must be unique. When two different users create tables with the same name at the same time, one or both of the users can receive this message. Rerun the CREATE TABLE statement.

在非 ANSI 数据库中，表名必须是唯一的。当两个不同的用户同时创建同名的表时，其中一个或两个用户都可以收到此消息。重新运行 CREATE TABLE 语句。

-9274 Complex type name length exceeds maximum allowd 65535.

The statement is trying to create complex type. The name of the complex type is exceeds maximum allowed 65535. Modify the statement such that it uses smaller identifiers.

该语句试图创建复杂类型。复杂类型的名称超过了最大允许的 65535 。修改语句，使其使用较小的标识符。

-9275 Decimal data precision exceeds the allowable limit for DRDA connections.

The query output contains decimal data that has precision exceeding the allowable limit of 31 digits for DRDA connections.

查询输出包含十进制数据，其精度超过 DRDA 连接所允许的 31 位数字限制。

-9300 Cannot set clear flag for UDT () in global jar list.

J/Foundation cannot set the clear flag for the specified user-defined type in the global jar list.

J/Foundation 无法为全局 jar 列表中指定的用户定义类型设置清除标志。

-9301 Cannot set remove flag for jar () in global JVP list.

J/Foundation cannot set the remove flag for the specified jar in the global JVP list.

J/Foundation 无法在全局 JVP 列表中为指定的 jar 设置删除标志。

-9302 Cannot set new path flag for .

J/Foundation cannot set a new path flag for the specified object.

J/Foundation 不能为指定对象设置新的路径标志。

-9303 User SQL Exception. J/Foundation returned the specified SQL exception.

J/Foundation 返回指定的 SQL 异常。

-9305 Attempt to read or position past end of UDT data.

This error occurs when a Java user-defined routing (UDR) attempts to read or set a position beyond the end of the user-defined type (UDT) data available from a UDT data input stream.

Check the length and structure of the UDT carefully against the data input UDR code.

当 Java 用户定义路由 (UDR) 试图读取或设置用户定义类型 (UDT) 数据结束后的位置时，会发生此错误。请对照数据输入 UDR 代码仔细检查 UDT 的长度和结构。

-9400 User-defined aggregate already exists.

The name given already exists in your database, either as an aggregate name or as the name of a routine. (You cannot have an aggregate and a routine with the same name.)给定的名称在数据库中已经存在，可以是聚合名称，也可以是例程的名称。(您不能拥有一个聚合和一个同名的例程。)Change your CREATE AGGREGATE statement to give the aggregate a unique name.

更改 CREATE AGGREGATE 语句，使聚合具有唯一的名称。

-9401 Cannot re-define or drop builtin aggregate .

The named aggregate is a system-defined aggregate. You can overload the functions that support the built-in aggregates, but you cannot redefine or drop built-in aggregates.

命名聚合是一个系统定义的聚合。可以重载支持内置聚合的函数，但不能重新定义或删除内置聚合。

Create support functions for the named aggregate but do not use the CREATE AGGREGATE statement.

请为命名聚合创建支持函数，但不要使用 CREATE AGGREGATE 语句。

-9402 Multiple occurrences of the modifier.

Each of the modifiers INIT, ITER, COMBINE, FINAL, and HANDLESNULLS can appear only once in the CREATE AGGREGATE statement. Check your statement for repeated modifier names.

每个修饰符 INIT、ITER、COMBINE、FINAL 和 HANDLESNULLS 只能在 CREATE AGGREGATE语句中出现一次。检查语句中是否有重复的修饰符名称。

-9403 The modifier must be specified.

You need to include the named modifier in your CREATE AGGREGATE statement.

The iterator (ITER) and combine (COMBINE) functions are required for all user-defined aggregates.

您需要在 CREATE AGGREGATE 语句中包含命名修饰符。所有用户定义的聚合都需要iterator (ITER) 和 combine (COMBINE) 函数。

-9404 User-defined aggregate does not exist.

The named aggregate does not exist in your database. Before you can use a user-defined aggregate, you must create the necessary support functions and register the new aggregate with a CREATE AGGREGATE statement.

数据库中不存在命名聚合。在使用用户定义的聚合之前，必须创建必要的支持函数，并使用 CREATE AGGREGATE 语句注册新聚合。

-9405 Must be owner of user-defined aggregate or DBA.

You attempted to drop a user-defined aggregate that someone else created.

To drop a user-defined aggregate, you must own (be the creator of) the aggregate or you must have DBA privilege.

您试图删除其他人创建的用户定义聚合。要删除用户定义的聚合，您必须拥有（创建）聚合，或者必须拥有 DBA 权限。

-9406 Cannot resolve support function for user-defined aggregate.

You attempted to use a built-in aggregate for which the database server could not find an appropriate support function. For example, if you try to use the SUM aggregate on the "new_type" data type, the database server looks for the following operator function:您试图使用数据库服务器找不到适当支持函数的内置聚合。例如，如果试图在“new_type”数据类型上使用 SUM 聚合，数据库服务器将查找以下运算符函数：plus(new_type, new_type)This error can also occur for a user-defined aggregate when one of the support functions that the CREATE AGGREGATE statement has listed(INIT/ITER/COMBINE/FINAL) is missing.

如果创建聚合语句列出的支持函数之一(INIT/ITER/COMBINE/FINAL)缺失，用户定义的聚合也可能发生此错误。

Make sure that you have the correct support functions for the user-defined aggregate. These functions must be exist and must be registered in the database with CREATE FUNCTION.

确保您对用户定义的聚合具有正确的支持功能。这些函数必须存在，并且必须使用CREATE FUNCTION 在数据库中注册。

-9407 Set-up parameter to the aggregate cannot contain non-group columns.

If the user-defined aggregate has been defined with a set-up argument, the second argument of this aggregate must be either a constant or one of the columns in the GROUP BY clause of your query.

如果用设置参数定义了用户定义的聚合，则该聚合的第二个参数必须是查询 GROUP BY子句中的常量或列之一。

For example, the following two statements are valid:例如，以下两个语句是有效的：SELECT new_aggr(colA, 2) FROM some_table SELECT new_aggr(colA, colB) GROUP BY colB FROM some_table-9408 User-defined aggregate has no arguments.

The user-defined aggregate in your SELECT statement does not specify any arguments.

SELECT 语句中的用户定义聚合没有指定任何参数。

Make sure that the user-defined aggregate of the SELECT statement provides the correct number of arguments (one or possibly two, if the aggregate includes a set-up argument).

请确保 SELECT 语句的用户定义聚合提供正确的参数（如果聚合包括一个设置参数，则可能提供两个参数）。

-9409 User-defined aggregate has too many arguments.

The user-defined aggregate in your SELECT statement specifies too many arguments.

SELECT 语句中的用户定义聚合指定了太多的参数。

Make sure that the user-defined aggregate of the SELECT statement provides the correct number of arguments (one or possibly two, if the aggregate includes a set-up argument).

确保 SELECT 语句的用户定义的聚合提供了正确的参数（如果聚合包括一个设置参数，则可能提供两个）。

-9410 User-defined aggregate has two arguments but no INIT function specified.

The user-defined aggregate in your SELECT statement specifies a set-up argument. However, the CREATE AGGREGATE statement that defined this aggregate has not specified an INIT support function. The handling of a set-up argument must occur in an INIT function.

SELECT 语句中的用户定义聚合指定一个设置参数。但是，定义此聚合的 CREATE AGGREGATE 语句尚未指定 INIT 支持函数。设置参数的处理必须在 INIT 函数中进行。

You can either call the user-defined aggregate without a set-up argument or implement a set-up argument for the user-defined aggregate. To implement a set-up argument, take the following actions:您可以在没有设置参数的情况下调用用户定义的聚合，也可以为用户定义的聚合实现一个设置参数。若要实现设置参数，请执行以下操作：- Write an INIT support function that handles the set-up argument.

编写一个处理设置参数的 INIT 支持函数。
Register the INIT function (with CREATE FUNCTION).
注册 INIT 函数（带有 CREATE FUNCTION）- Drop the user-defined aggregate (with DROP AGGREGATE).
删除用户定义的聚合(带有 DROP AGGREGATE)。
redefine the user-defined aggregate (WITH CREATE AGGREGATE),providing the INIT modifier to specify the new INIT support function.
重新定义用户定义的聚合(带有 CREATE AGGREGATE)，提供 INIT 修饰符来指定新的 INIT 支持函数。

-9411 User-defined aggregate support function does not handle nulls.

You created your aggregate with the HANDLESNULLS option, but the function named in the error message does not handle nulls.

您使用 HANDLESNULLS 选项创建了聚合，但错误消息中指定的函数不处理空值。

When you create an aggregate with HANDLESNULLS, all support functions must also handle nulls. You can either change the aggregate or change the function. To change the aggregate, drop the aggregate and re-create it without the HANDLESNULLS option.

使用 HANDLESNULLS 创建聚合时，所有支持函数也必须处理空值。可以更改聚合，也可以更改函数。若要更改聚合，请删除聚合，然后在不使用 HANDLESNULLS 选项的情况下重新创建聚合。

If the aggregate needs to handle null values, you must modify the function so that it can handle nulls. Then drop the function and reregister it with the HANDLESNULLS option.

如果聚合需要处理空值，则必须修改函数，使其能够处理空值。然后删除该函数并使用HANDLESNULLS 选项重新注册它。

-9412 Return type of the support function does not match the aggregate state type.

When you extend a built-in aggregate for a user-defined data type, the return type of the operator function must be the same as the data type for which you are extending the aggregate. For example, if you try to use the SUM aggregate on the "new_type" data type, thedatabase server looks for a plus() function with the following signature:当为用户定义的数据类型扩展内置聚合时，运算符函数的返回类型必须与扩展聚合的数据类型相同。例如，如果试图在“new_type”数据类型上使用 SUM 聚合，数据库服务器将查找具有以下签名的 plus() 函数：CREATE FUNCTION plus(c1 new_type, c2 new_type)RETURNING new_type;This error can also occur for user-defined aggregates if the return type of an INIT support function is not the same as that of the ITER or COMBINE function. For user-defined types, make sure that the return types of the INIT function (if any), ITER function, and COMBINE function are the same as the user-defined type.

如果 INIT 支持函数的返回类型与 ITER 或 COMBINE 函数的返回类型不同，用户定义的聚合也可能发生此错误。对于用户定义的类型，请确保 INIT 函数(如果有的话)、 ITER函数和 COMBINE 函数的返回类型与用户定义的类型相同。

-9422 JDK 1.2 cannot be used with kernel AIO.

JDK 1.2 cannot be used with kernel AIO.

JDK 1.2 不能与内核 AIO 一起使用。

Disable kernel AIO and try again.

请禁用内核 AIO，然后再试一次。

-9423 Transaction request %s failed to execute.

A server JDBC attempt to start a transaction failed to execute.

服务器 JDBC 试图启动事务失败。

Check online.log for any failures.

请检查 online.log 是否有任何故障。

-9424 Server JDBC failed to get a row from the server.

A server JDBC attempt to get a row from the database server resulted in an error. This is an internal error.

服务器 JDBC 试图从数据库服务器获取一行，导致错误。这是内部错误。

-9425 Internal error with the Java memory pool.

An unexpected internal error occurred during use of the Java memory pool.

The pool could have been corrupted.

在使用 Java 内存池时发生了意外的内部错误。

池可能已损坏。

Restart the database server.

请重新启动数据库服务器。

-9426 Can't use Native threads in this configuration.

You cannot use native threads in this configuration. Only green threads can be supported on this platform.

不能在此配置中使用本机线程。在这个平台上只能支持绿色线程。

-9427 Can't use Green threads in this configuration.

You cannot use green threads in this configuration. Only native threads can be supported on this platform.

不能在此配置中使用绿色线程。在此平台上只能支持本机线程。

-9428 Java configuration () parameter error.

The configuration parameter was not specified correctly.

未正确指定配置参数。

Modify the configuration parameter and restart the server.

请修改配置参数并重新启动服务器。

-9429 Java initialization failed, unable to find the library/routine().

Java startup failed to locate the library or the specified routine().

Java 启动未能找到库或指定的例程()。

Check the Java installation on the machine. Either a wrong version of the JDK has been installed, or the installation has not been completed correctly.

检查机器上的 Java 安装。不是安装了 JDK 的错误版本，就是安装没有正确完成。

-9430 JNI internal error. Unable to find or execute JNI call().

The specified JNI call could not be executed. Possible causes of this error include invalid JVP ONCONFIG variable settings, a possible VM crash, and VM corruption. For example, your JVPCLASSPATH ONCONFIG parameter might be missing the $GBS_HOME/extend/krakatoa/krakatoa.jar file, or JVPCLASSPATH or another ONCONFIG parameter might have an incorrect path or file name.

无法执行指定的 JNI 调用。此错误的可能原因包括无效的 JVP ONCONFIG 变量设置、可能的 VM 崩溃和 VM 损坏。例如，您的 JVPCLASSPATH ONCONFIG 参数可能缺少$GBS_HOME/extend/krakatoa/krakatoa.jar 文件，或者 JVPCLASSPATH 或其他ONCONFIG 参数可能有不正确的路径或文件名。

Check your JVP ONCONFIG variable settings. If the settings are valid,contact GBase Technical Support.

请检查您的 JVP ONCONFIG 变量设置。如果设置有效，请与 GBase 技术支持部门联系。

-9431 Can't find system class or method or library ().

Java startup failed to locate the system class or method ().

Java启动未能找到系统类或方法()。

Check the Java installation and J/Foundation installation on the computer. Either the wrong version has been installed, or the installation has not been completed correctly.

检查计算机上的 Java 安装和 J/Foundation 安装。要么安装了错误的版本，要么安装没有正确完成。

-9432 Variable length UDTs are not supported in this version of Java.

This version of Java does not support variable-length. This feature is scheduled to be enabled in a future release.

这个版本的 Java 不支持可变长度。此功能计划在以后的发行版中启用。

-9433 Cannot position Blob/Clob.

An internal error occurred during access to a large object.

访问大对象时发生内部错误。

Contact GBase Technical Support.

联系 GBase 技术支持。

-9434 Unexpected failure during initialization of Java virtual processor.

An unexpected failure occurred during the initialization of a JVP.

在初始化 JVP 期间发生了意外的失败。

Check online.log for details.

查看 online.log 获取详细信息。

-9435 Unexpected failure during Java procedure execution.

An unexpected failure occurred during Java procedure execution.

在 Java 过程执行期间发生了意外的失败。

Check online.log for details.

查看 online.log 获取详细信息。

-9436 Java UDR's VP class must be CLASS_JAVA.

A Java UDR can run only on a JVP.

Java UDR 只能在 JVP 上运行。

-9437 Unable to get SQLException information.

An internal error during access to the SQLException object.

访问 SQLException 对象时出现内部错误。

Contact GBase Technical Support.

联系 GBase 技术支持。

-9438 Feature or method () is not supported for opaque types.

The feature or method () is currently not supported for opaque types. This feature or method might be implemented in a future release.

当前不透明类型不支持此功能或方法 () 。这个特性或方法可能在将来的版本中实现。

-9439 Feature or method () is not supported for distinct types.

The feature or method () is currently not supported for distinct types. This feature or method might be implemented in a future release.

当前不同类型不支持此功能或方法 () 。这个特性或方法可能在将来的版本中实现。

-9440 Server JDBC failed to open cursor.

An attempt to open a cursor fetch by server JDBC failed.

尝试打开服务器 JDBC 的光标失败。

-9441 Cannot create UDR Thread (%s).

The Embedded Java Virtual Machine failed to create a thread for processing the UDR call. Contact GBase Technical Support.

嵌入式 Java 虚拟机未能创建用于处理 UDR 调用的线程。与 GBase 技术支持部门联系。

-9442 Error loading Java UDR class (%s).

Make the following checks to ensure that the class that contains the Java UDR is loaded:进行以下检查以确保加载了包含 Java UDR 的类：o The directory that contains the class must be specified in the CLASSPATH environment variable.

o 包含类的目录必须在 CLASSPATH 环境变量中指定。

o The jar that contains the class must be correctly installed with the built-in procedure install_jar().

o 包含该类的 JAR 必须与内置过程 install_jar() 一起正确安装。

o The jar file has been created correctly, with the proper path to the class.

o JAR 文件已被正确创建，并具有正确的类路径。

-9443 Cannot find class for type (%s).

For a user-defined-type mapping, make sure that the class is present in the CLASSPATH environment variable or in a jar that is installed in the database. Mappings for other data types come from the Java Developer's Kit(JDK) or GBase 8s-enhanced classes. For these data types, check the installation of your JDK and GBase 8s database server.

对于用户定义的类型映射，请确保类存在于 CLASSPATH 环境变量或安装在数据库中的JAR 中。其他数据类型的映射来自 Java Developer's Kit (JDK) 或 GBase 8s 增强类。

对于这些数据类型，请检查 JDK 和 GBase 8s 数据库服务器的安装。

-9444 Initialization of Java virtual processor failed: ().

Possible causes for this error message include incorrect settings in the configuration file for the database server, incorrect installation of the JDK release, missing links to the JDK shared libraries,and no gbasedbt.policy file.

此错误消息的可能原因包括数据库服务器配置文件中的不正确设置、JDK发行版的错误安装、JDK 共享库的链接缺失以及没有 gbasedbt.policy 文件。

Make sure that the configuration file for the database server has the correct settings for J/Foundation. Also make sure that your JDK release is properly installed. For Solaris systems that require /usr/lib links to the JDK shared libraries, make sure that the links are properly installed with the setjdk utility program.

确保数据库服务器的配置文件具有 J/Foundation 的正确设置。还请确保您的 JDK 发行版已正确安装。对于需要 /usr/lib 链接到 JDK 共享库的 Solaris 系统，请确保这些链接与 setjdk 实用程序一起正确安装。

If the gbasedbt.policy file is missing, copy the file $GBS_HOME/extend/krakatoa/gbasedbt.policy.std to$ GBS_HOME/extend/krakatoa/gbasedbt.policy. You can customize the gbasedbt.policy file after you create it.

如果缺少 gbasedbt.policy 文件，请复制 $GBS_HOME/extend/krakatoa/gbasedbt.policy.std 文件到$ GBS_HOME/extend/krakatoa/gbasedbt.policy。你可以在创建 gbasedbt.policy文件后定制它。

-9445 Java language manager operation failed (%s).

Contact GBase Technical Support.

联系 GBase 技术支持。

-9446 Execution of Java user-defined routine failed: (%s).

Correct the implementation of the Java UDR based on the problem that the paranthetical message indicates.

根据附加消息指示的问题纠正 Java UDR 的实现。

-9447 Cannot perform Java-to-SQL type mapping for type (%s).

The user-defined-type mapping is invalid. Refer to the J/Foundation documentation for allowed type mappings.

用户定义的类型映射无效。有关允许的类型映射，请参阅 J/Foundation 文档。

-9448 Unequal number of parameters in SQL and Java signature (%s).

Make sure that the SQL and Java signatures that the CREATE FUNCTION or CREATE PROCEDURE statement has provided specify the same number of parameters.

确保 CREATE FUNCTION 或 CREATE PROCEDURE 语句提供的 SQL 和 Java 签名指定了相同数量的参数。

-9449 Java UDR method not found or is not static: (%s).

Make sure that the specified Java method exists as a public static method in the specified class. Also make sure that the signature of the defined method matches the signature that the CREATE FUNCTION or CREATE PROCEDURE statement has specified.

确保指定的 Java 方法作为公共静态方法存在于指定的类中。还要确保定义方法的签名与CREATE FUNCTION 或 CREATE PROCEDURE 语句指定的签名匹配。

-9450 Java method invocation failed (%s).

Make sure that the Java method is accessible. That is, it must either be public or be in the same package as the caller.

确保 Java 方法是可访问的。也就是说，它必须是公共的，或者与调用者在同一个包中。

-9451 Error instantiating user-defined-type mapping class (%s).

Make sure that the Java class specified has the proper access permissions for instantiation. Check the instantiation rules for the Java language.

确保指定的 Java 类具有实例化的适当访问权限。检查 Java 语言的实例化规则。

-9452 Error processing null argument. Use Java object form of type (%s).

You have probably used a Java primitive type as an argument to a Java method that maps to the specified Java UDR. A null value for a primative-type argument is invalid. Replace the Java primitive type with a Java Object type. For example, replace "int" with "java.lang.Integer".

您可能已经将 Java 原语类型用作映射到指定 Java UDR 的 Java 方法的参数。初始类型参数的空值无效。用 Java 对象类型替换 Java 原语类型。例如，将“int”替换为“java.lang.Integer”。

-9453 The JDBC command doesn't return any rows.

The database server did not return any rows as a result of the JDBC command.

由于 JDBC 命令，数据库服务器没有返回任何行。

-9454 Error getting length for user-defined type ().

An error occurred during an attempt to retrieve the length for the specified user-defined type.

试图检索指定用户定义类型的长度时发生错误。

Make sure that the length of the user-defined type is correctly stored in the sysxtdtypes system catalog table.

请确保用户定义类型的长度正确存储在 sysxtdtypes 系统目录表中。

-9455 Cannot access large object.

Make sure that the default sbspace, which the SBSPACENAME configuration parameter indicates, has been created. The onspaces utility creates sbspaces.

确保已创建了 SBSPACENAME 配置参数指示的默认 sbspace 。onspace 实用程序创建sbspace。

-9456 Cannot get large object length.

The database server cannot obtain the length of a large object using a JDBC connection. Make sure the connection from which the large object comes is still valid.

数据库服务器无法使用 JDBC 连接获取大对象的长度。确保来自大对象的连接仍然有效。

-9457 Cannot convert large object handle to byte[].

The database server cannot obtain the content of a large object using a JDBC connection. Make sure the connection from which the large object comes is still valid.

数据库服务器无法使用 JDBC 连接获取大对象的内容。确保来自大对象的连接仍然有效。

-9458 Cannot start large object search.

The database server cannot perform seek on a large object using a JDBC connection. Make sure the connection from which the large object comes is still valid.

数据库服务器无法使用 JDBC 连接对大对象执行查找。确保来自大对象的连接仍然有效。

-9459 Large object Error: (%s).

The database server cannot access a large object using a JDBC connection.

Check the problem information contained in the error message. Also make sure the connection from which the large object comes is still valid.

数据库服务器无法使用 JDBC 连接访问大对象。检查错误消息中包含的问题信息。还要确保大对象所来自的连接仍然有效。

-9460 Wrong connection for large object.

Contact GBase Technical Support.

联系 GBase 技术支持。

-9461 Cannot read (%s) bytes off binary stream.

The large object does not contain as many bytes of data as are requested to be read from it.

大对象不包含被请求读取的数据字节。

Make sure the binary stream used to create a large object has a sufficient amount of data.

请确保用于创建大对象的二进制流具有足够的数据量。

-9462 Driver being shutdown.

The Java virtual processor (VP) cannot create new JDBC connections while it is in the process of being shut down. Terminate your JDBC session and restart it after the VP is completely removed from the database server.

Java 虚拟处理器(VP)在关闭过程中无法创建新的 JDBC 连接。终止 JDBC 会话，并在 VP从数据库服务器中完全删除后重新启动它。

-9463 Cannot load the specified IfxProtocol class: (%s).

Make sure that the JDBC URL, which you specify in the DriverManager.getconnection() method, has a valid protocol class name for the ProtocolClass parameter.

确保在 DriverManager.getconnection() 方法中指定的 JDBC URL 具有 ProtocolClass参数的有效协议类名。

-9464 Must specify user=name in the URL.

Make sure the JDBC URL contains the username.

确保 JDBC URL 包含用户名。

-9465 Must specify dbname in the URL.

Make sure the JDBC URL contains the database name.

确保 JDBC URL 包含数据库名称。

-9466 Must specify password=value in the URL.

Make sure the JDBC URL contains the password for the desired user session.

确保 JDBC URL 包含所需用户会话的密码。

-9467 Driver shutdown, no new connection.

The Java virtual processor (VP) was shut down in the middle of creating a JDBC connection. Terminate your JDBC session and restart it after the VP is completely removed from the database server.

Java 虚拟处理器(VP)在创建 JDBC 连接时被关闭。终止 JDBC 会话，并在 VP 从数据库服务器中完全删除后重新启动它。

-9468 Cannot make UDR connection in non-UDR thread.

A UDR connection can be made only from the thread executing a Java UDR. Make sure the connection is not created on a child thread forked by the UDR.

只能从执行 Java UDR 的线程中建立 UDR 连接。确保连接不是在 UDR 分叉的子线程上创建的。

-9469 UDR connection failed.

Contact GBase Technical Support.

联系 GBase 技术支持。

-9470 Cannot establish JDBC connection for embedding application.

Contact GBase Technical Support.

联系 GBase 技术支持。

-9471 Database server connection failed.

Contact GBase Technical Support.

联系 GBase 技术支持。

-9472 Error creating Solano connection: (%s).

Contact GBase Technical Support.

联系 GBase 技术支持。

-9473 Connection to database failed.

Make sure that the database exists and has all required access permissions.

确保数据库存在并具有所有必需的访问权限。

-9474 Could not connect to database (%s).

Contact GBase Technical Support.

联系 GBase 技术支持。

-9475 Connection is closed.

Make sure the connection used to issue the JDBC operation is still open.

确保用于发出 JDBC 操作的连接仍处于打开状态。

-9476 Database server JDBC error: (%s).

Contact GBase Technical Support.

联系 GBase 技术支持。

-9477 Cannot obtain UDR environment.

UDR environment objects are available only to Java UDR threads. Make sure the getUDREnv() method is not invoked by a child thread forked by the Java UDR.

UDR环境对象只对 Java UDR 线程可用。确保 Java UDR 分叉的子线程不会调用getUDREnv() 方法。

-9478 VM too low on memory: (%s) bytes left.

There is insufficient memory to start a new instance of a Java UDR. Reduce the number of session connected to the Java virtual processor (VP) or terminate the resource-intensive Java computations.

内存不足，无法启动 Java UDR 的新实例。减少连接到 Java 虚拟处理器(VP)的会话数量，或终止资源密集型 Java 计算。

-9479 Unknown throwable: (%s).

The Java UDR throws an unknown exception. Check the Java VP log for details.

-9480 Unknown iterator code.

Contact GBase Technical Support.

联系 GBase 技术支持。

-9481 Internal Error: (%s).

Contact GBase Technical Support.

联系 GBase 技术支持。

-9482 Deployment descriptor file (%s) is not in the right format.

Refer to the J/Foundation documentation for the correct format of a deployment descriptor file.

有关部署描述符文件的正确格式，请参阅 J/Foundation 文档。

-9483 Unrecognized type: (%s).

Make sure that the specified data type is registered in the current database.

确保指定的数据类型已在当前数据库中注册。

-9484 Invalid jar name.

If the jar name specifies the database and/or username, make sure that these names match the database and user in the environment in which the jar is being installed.

如果 jar 名称指定了数据库和/或用户名，请确保这些名称与安装 jar 的环境中的数据库和用户匹配。

-9485 Attempt to install an existing jar: (%s).

Remove the existing jar before you install a new one that has the same name.

在安装同名的新 jar 之前，先删除现有的 jar 。

-9486 Invalid URL.

Check the syntax of the URL for the jar.

检查 jar 的 URL 语法。

-9487 Attempt to remove non-existing jar: (%s).

You cannot drop a jar that has not first been installed.

您不能删除第一次安装的 jar 。

-9488 Invalid jar removal. All dependent UDRs not dropped.

You cannot drop a jar if dependent UDRs still reference any of the classes within the jar. Drop all user-defined functions and/or user-defined procedures that reference a class in the jar within their external names.

如果依赖的 UDR 仍然引用 jar 中的任何类，则不能删除 jar 。删除所有用户定义的函数和/或用户定义的过程，引用外部名称中的 jar 中的一个类。

-9489 Invalid jar replacement. Class (%s) from old jar is still referenced.

There is at least one class in the old jar that is not replaced in the new jar and is referenced by a Java UDR. You must either drop the Java UDR before you attempt to replace the jar, or add the class to the new jar.

旧 jar 中至少有一个类在新 jar 中没有被替换，并且被 Java UDR 引用。您必须在尝试替换 jar 之前删除 Java UDR，或者将类添加到新的 jar 中。

-9490 No manifest file found for jar (%s).

All deployment descriptions that install_jar() needs to process must be listed in the manifest file for the jar. Make sure that the manifest file is created correctly for the jav. If no deployment descriptors are to be processed, pass a value of '0' as the last parameter to the install_jar()built-in procedure.

install_jar() 需要处理的所有部署描述必须在 jar 的清单文件中列出。确保为 jav正确地创建了清单文件。如果不处理部署描述符，则将值‘0’作为最后一个参数传递给install_jar() 内置过程。

-9491 User threads are not allowed in this context, must be a DBAThread.

Java threads created by users from within user-defined routines are not allowed to open JDBC connections.

用户从用户定义的例程中创建的 Java 线程不允许打开 JDBC 连接。

If such threads need to execute SQL statements, then they need to open Solano connections to run the queries against.

如果这样的线程需要执行 SQL 语句，那么它们需要打开 Solano 连接来运行对其的查询。

-9492 Unsupported feature: (%s).

This version of the database server cannot implement the specified feature.

此版本的数据库服务器无法实现指定的功能。

-9493 Unsupported command from deployment descriptor: (%s).

Check the J/Foundation documentation for the commands that the database server supports within deployment descriptor files.

查看 J/Foundation 文档，了解数据库服务器在部署描述符文件中支持的命令。

-9494 Java not supported in this database server or Error loading Java language module.

The version of your database server might not be Java enabled.

数据库服务器的版本可能没有启用 Java 。

If you are using a Java-enabled database server and the Java language module $GBS_HOME/extend/krakatoa/lmjava.so does not exist in your distribution, contact GBase Technical Support.

如果您使用的是启用 Java 的数据库服务器，并且 Java 语言模块$GBS_HOME/extend/krakatoa/lmjava.so 在您的发行版上不存在，请与 GBase 技术支持部门联系。

-9495 Database server JDBC internal error. Check with your administrator.

Unexpected JDBC driver internal error. This error is raised if the JDBC driver fails to acquire an internal resource.

意外的 JDBC 驱动程序内部错误。如果 JDBC 驱动程序无法获取内部资源，则会引发此错误。

For diagnostic information, check the jvp.log and online.log files.

有关诊断信息，请查看 jvp.log 和 online.log 文件。

-9496 Unable to map Java type to an SQL type or SQL type to a Java type.

Unable to map between the Java type and the specified SQL type. This error is usually raised when the database server is unable to start a Java user-defined routine because its SQL types could not be mapped to Java types.

无法在 Java 类型和指定的 SQL 类型之间进行映射。当数据库服务器由于无法将其 SQL类型映射到 Java 类型而无法启动 Java 用户定义的例程时，通常会引发此错误。

Check the declaration of the Java user-defined routine.

请检查 Java 用户定义例程的声明。

-9498 Incorrect path to JAR file specified: ().

The pathname for the JAR file to be installed is incorrect.

要安装的 jar 文件的路径名不正确。

Correct the path to the JAR file and retry.

更正 JAR 文件的路径并重试。

-9499 Internal JAR handling error. Check with your administrator.

Unexpected JAR handling error.

意外的 JAR 处理错误。

For additional information, check the jvp.log and online.log files.

有关其他信息，请查看 jvp.log 和 online.log 文件。

-9500 A subscript is out of bounds.

This statement takes a substring of a character variable. The substring values (that is, two numbers in square brackets) are incorrect. The first is less than zero or greater than the length of the column, or the second is less than the first. Correct the form specification and recompile.

此语句接受字符变量的子字符串。子字符串值（即方括号中的两个数字）是不正确的。

第一个小于零或大于列的长度，或第二个小于第一个。修改表单规范并重新编译。

-9503 The table tablename could not be opened.

Check that the table name is correctly spelled. If so, the table tablename might not exist in the database (it might have been dropped or renamed); or if it exists, your account might not have SELECT access to it. Alternatively, if you are using the GBase 8s SE database server,you might have exceeded the limit on open files, which can limit the number of tables that you can name in a SELECT statement. In this case,you might have to revise the SELECT section of the report to use more SELECT statements, each of which names fewer tables. Products after检查表名是否拼写正确。如果是这样，表名可能不存在于数据库中（它可能已被删除或重命名）；如果存在，则您的账户可能无法对其进行 SELECT 访问。或者，如果您正在使用GBase 8s SE 数据库服务器，您可能已经超出了打开文件的限制，这可以限制您可以在SELECT 语句中命名的表的数量。在这种情况下，您可能必须修改报表的 SELECT 部分，以使用更多 SELECT 语句，每个语句的表名称都较少-9503 PRINT FILE filename could not be opened.

The file that is shown could not be opened for output. Look for operating-system error messages that might give more information.

Possible causes include a full disk or lack of the correct permissions for the file or directory.

显示的文件无法打开以供输出。查找可能提供更多信息的操作系统错误消息。可能的原因包括完整的磁盘或文件或目录缺乏正确的权限。

-9504 The argument number is out of bounds for the ascii function. Arguments must be between 0 and 255, inclusive.

The input to the ASCII function must be a number between 0 and 255.

Examine the use of this function in the report specification. If the improper value number came from a command-line parameter, you might consider testing it with an IF statement.

ASCII 函数的输入必须是 0 到 255 之间的数字。在报表规范中检查此函数的使用情况。

如果不正确的值号来自命令行参数，则可以考虑使用 IF 语句对其进行测试。

-9602 Illegal attempt to convert a collection type into another type.

You attempted to store a collection of one type in a collection of a different type, or you attempted to move a collection into a host variable that is not a collection. In ESQL/C, a collection host variable declared to contain elements of a specific type can only hold collections of that same type. If you require that a collection host variable hold collections of different types, declare it without the specific type information.

尝试将一种类型的集合存储在不同类型的集合中，或者尝试将集合移动到非集合的宿主变量中。在 ESQL/C 中，声明为包含特定类型元素的集合宿主变量只能保存该类型的集合。如果要求集合宿主变量持有不同类型的集合，请在没有特定类型信息的情况下声明该集合。

-9605 Scroll cursor can't select collection columns.

You attempted to select a collection column while you were using a scroll cursor. You must rewrite the query without the scroll cursor or eliminate any collection columns from the select list.

在使用滚动游标时，尝试选择集合列。必须在没有滚动光标的情况下重写查询，或者从选择列表中删除任何集合列。

-9606 Collections are not allowed in the GROUP BY clause.

Move the reference to a collection column in the GROUP BY list.

将引用移动到 GROUP BY 列表中的集合列。

-9607 Collections are not allowed in the DISTINCT clause.

Either remove the DISTINCT clause or remove the collection column from the SELECT clause.

从 SELECT 子句中删除 DISTINCT 子句或删除集合列。

-9608 Collections are not allowed in the ORDER BY clause.

Remove the reference to a collection column in the GROUP BY list.

删除对 GROUP BY 列表中集合列的引用。

-9609 Collections are not allowed in the expression.

You attempted to select a collection from within a subquery, perform an aggregation on a collection, or use a collection in some other expression that is not allowed. Check your manual to determine the places where you can use collections in expressions.

您试图从子查询中选择集合，对集合执行聚合，或在不允许的其他表达式中使用集合。

检查您的手册，以确定您可以在表达式中使用集合的位置。

-9610 Illegal attempt to use collection host variable.

You attempted to calculate the cardinality of a data type that is not a collection, incorrectly used a collection host variable by using an untyped collection without assigning a value to it, or used incorrect syntax to create a collection derived table.

您试图计算非集合的数据类型的基数，使用未指定值的非类型化集合错误地使用集合主机变量，或使用不正确的语法创建集合派生表。

Check your manual to determine the correct usage of collections in this context.

请检查手册以确定集合在此上下文中的正确用法。

-9611 ROM clause cannot have a join when one of the tables is a collection.

You cannot join a table derived from a collection with a table. Remove TABLE(:coll_host_var) from the FROM clause of your query.

不能将从集合派生的表与表连接起来。从查询的 FROM 子句中删除 TABLE(:coll_host_var) 。

-9612 No WHERE, GROUP BY, HAVING or ORDERBY clause is allowed in a collection.

Remove any WHERE, GROUP BY, HAVING, or ORDER BY clause from your statement or remove TABLE(:coll_host_var) from the FROM clause of your statement.

从语句中删除 WHERE、GROUP BY、HAVING 或 ORDER BY 子句或从语句的 FROM 子句中删除 TABLE(:coll_host_var) 。

-9613 Select list cannot have expression when selecting from a collection.

Only '*' or column names are allowed in the select list for derived tables that use collections. Check your SELECT list.

在使用集合的派生表的选择列表中，只允许使用“*”或列名。检查您的选择列表。

-9614 Derived column list is not allowed for this statement.

UPDATE statements do not require derived-column lists. Columns are listed in parentheses following a table name. Also, in any SQL statement, a derived-column list can be associated only with collection-derived tables and not others.

UPDATE 语句不需要派生列表。列在表名后面的括号中。此外，在任何 SQL 语句中，派生列表只能与集合派生表相关联，而不能与其他表关联。

Remove the derived-column list from the UPDATE statement.

从 UPDATE 语句中删除派生列表。

-9615 AT keyword is not allowed when inserting in a base table.

Use the AT keyword only when you are inserting into a LIST.

只在插入列表时使用 AT 关键字。

-9616 Position value should be specified through a constant or a variable.

The position argument for an AT keyword of a list must be a simple integer literal or host variable.

列表的AT关键字的位置参数必须是简单的整数、文字或主机变量。

Simplify the expression to one of these.

请将表达式简化为其中之一。

-9617 Source for the SET clause should be a simple expression.

Collection derived tables can only be updated using constants, host variables, or table columns.

只能使用常量、宿主变量或表列更新集合派生表。

-9618 Aliasing is not allowed for a collection of ROW types.

For collection-derived tables, you need not provide a column name alias. Remove the column name alias.

对于集合派生表，不需要提供列名别名。删除列名别名。

-9620 Cannot select the collection variable (collection_variable_name).

This error occurs within SPL when you attempt to place an SPL collection variable in the select list. You must remove the collection variable from the select list.

当您试图将 SPL 集合变量放置在选择列表中时，SPL 中会发生此错误。必须从选择列表中删除集合变量。

-9621 The number of derived columns do not match the actual number of columns.

For collection-derived tables, you must provide number of derived columns matching with columns in select list.

For example, the following SELECT statement would cause error -9621:对于集合派生表，必须提供与 SELECT 列表中的列匹配的派生列数。例如，以下 SELECT语句将导致错误 -9621：SELECT * FROM TABLE(MULTISET(SELECT colno, colname FROM syscolumns WHERE tabid > 99)) AS vtab(vc1)-9623 Internal length must be greater than zero and smaller than 32,768.

When you use the CREATE OPAQUE TYPE statement to define a fixed-length opaque type, the value that you specify for the internal length modifier must be greater than 0 bytes and smaller than 32,768 bytes.

使用“创建不透明类型”语句定义固定长度的不透明类型时，为内部长度修饰符指定的值必须大于 0 字节，小于 32,768 字节。

Use a valid value to define the type.

使用有效值定义该类型。

-9624 Maximum length must be greater than zero and smaller than 32,768.

When you use the CREATE OPAQUE TYPE statement to define a variable-length opaque type, the value that you specify for the maximum length modifier must be greater than 0 bytes and smaller than 32,768 bytes.

Redefine the type with a valid value.

当您使用 CREATE OPAQUE TYPE 语句定义可变长度不透明类型时，您为最大长度修饰符指定的值必须大于 0 字节，小于 32,768 字节。用有效值重新定义类型。

-9625 Alignment must be set to 1, 2, 4 or 8.

When you use the CREATE OPAQUE TYPE statement to define an opaque type,the value that you specify for the alignment modifier must be 1, 2, 4,or 8. Redefine the type with a valid value.

使用“创建不透明类型”语句定义不透明类型时，为对齐修饰符指定的值必须为 1、2、4或 8 。用有效值重新定义类型。

-9626 Maximum length should be set for variable-sized opaque types only.

When you use the CREATE OPAQUE TYPE statement to define a fixed-length opaque type, you should not specify the maximum length modifier.

当使用 CREATE OPAQUE TYPE 语句定义固定长度的不透明类型时，不应指定最大长度修饰。

-9627 Passedbyvalue can only be set if length is 1, 2, or 4.

When you use the CREATE OPAQUE TYPE statement to define a fixed-length opaque type that is passed by value, its internal length must be 1, 2,or 4.

使用 CREATE OPAQUE TYPE 语句定义通过值传递的固定长度的不透明类型时，其内部长度必须为 1、2 或 4。

-9628 Type (type_name) not found.

The specified type_name could not be found. The datatype name you use should either be a built-in datatype of GBase 8s Dynamic Server or an extended datatype explicitly created by the user/application.

If you encounter this error on a Read-only Secondary of an HDR pair,check to see if the specified type_name was ever created on the Primary.

找不到指定的类型名称。您使用的数据类型名称应该是 GBase 8s Dynamic Server 的内置数据类型，或者是用户/应用程序显式创建的扩展数据类型。如果在 HDR 对的只读二级遇到此错误，请检查指定的 type_name 是否在主服务器上创建。

Example of extended datatypes: distinct type, row type, collection type,and opaque type. Before you can use an extended type, you must create it with the CREATE TYPE statement.

example: CREATE DISTINCT TYPE di AS INT;CREATE ROW TYPE rt (a INT, b CHAR(10));扩展数据类型示例：distinct 类型、row 类型、collection 类型和 opaque 类型。在使用扩展类型之前，必须用 CREATE TYPE 语句创建它。

例如：CREATE DISTINCT TYPE di AS INT;CREATE ROW TYPE rt (a INT, b CHAR(10));-9629 Not owner of type.

USAGE permission is required for the use of opaque types. Use the GRANT USAGE ON TYPE statement to grant permission to use a type.

使用不透明类型需要 USAGE 权限。使用 GRANT USAGE ON TYPE 语句授予使用类型的权限。

-9630 Cannot drop type (type_name): still in use.

An opaque type cannot be dropped while it is in use. Be sure that no casts, functions, or distinct type definitions are based on the type.

不透明类型在使用时不能删除。确保没有基于类型的转换、函数或 distinct 类型定义。

-9631 Opaque type (type_name) already exists in database.

Opaque types must be unique within the schema (ANSI mode) or database.

Be sure that the type does not already exist.

在架构（ANSI 模式）或数据库中，不透明类型必须是唯一的。确保该类型不存在。

-9632 Value does not match the type of column (column_name).

If the value does not match the data type of the column, but can be converted into the data type of the column, then you might need to use an implicit or explicit cast.

如果值与列的数据类型不匹配，但可以转换为列的数据类型，则可能需要使用隐式或显式强制转换。

If you want the conversion to be automatic, then create an implicit cast by using the CREATE IMPLICIT CAST statement to define a cast between the source and destination types. See the description of the CREATE CAST statement in the GBase 8s Guide to SQL: Syntax.

如果希望转换是自动的，那么通过使用 CREATE IMPLICIT CAST 语句来创建隐式 CAST，以定义源类型和目标类型之间的强制转换。参见 GBase 8s SQL 指南：语法中对 CREATE CAST 语句的描述。

In some cases, you might need to use explicit casting. A common cause of error -9632 is failure to explicitly cast a row type. For example,the following INSERT statement would cause error -9632:在某些情况下，您可能需要使用显式强制转换。导致错误 -9632 的一个常见原因是未能显式地强制转换行类型。例如，以下 INSERT 语句将导致错误 -9632：CREATE ROW TYPE rt1 (i INT, f FLOAT);CREATE TABLE table1 (rt1_col rt1);INSERT INTO table1 (rt1_col) VALUES (ROW(1, 2.0));The correct INSERT statement, with the explicit cast, follows:使用显式强制转换的正确 INSERT 语句如下：INSERT INTO table1 (rt1_col) VALUES (ROW(1, 2.0)::rt1);-9633 ALTER TABLE cannot modify column (column_name) type. Need a cast from the current type to the new type.

Conversions of column types require a cast. Use the CREATE CAST statement to define a cast from the source to destination type.

列类型的转换需要强制转换。使用 CREATE CAST 语句定义从源类型到目标类型的强制转换。

-9634 No cast from .

The specified cast does not exist or the cast function does not exist. Use the CREATE CAST statement to define the cast or to create the cast function.

指定的强制转换不存在或不存在强制转换函数。使用 CREATE CAST 语句定义 CAST 或创建 CAST 函数。

-9635 An attempt has failed to convert an opaque type into another type without a cast function.

The specified cast does not exist or the cast function does not exist. Use the CREATE CAST statement to define the cast or to create the cast function.

指定的强制转换不存在或不存在强制转换函数。使用 CREATE CAST 语句定义 CAST 或创建 CAST 函数。

The BOOLEAN, BLOB, CLOB, and LVARCHAR data types are implemented by the database server as built-in opaque data types.

BOOLEAN、BLOB、CLOB 和 LVARCHAR 数据类型由数据库服务器作为内置的不透明数据类型实现。

-9636 Opaque type exceeded its maximum length.

Opaque types are defined with a maximum length that cannot be exceeded. Verify that user-defined routines that return the type do not attempt to exceed the size limit.

不透明类型定义的最大长度不能超过。验证返回类型的用户定义例程是否试图超过大小限制。

-9637 Cast function (function_name) does not exist.

The function associated with a cast must exist when the cast is executed. Use the CREATE FUNCTION statement to create the function.

在执行强制转换时，必须存在与强制转换关联的函数。使用 CREATE FUNCTION 语句创建函数。

-9638 Grant/Revoke under on opaque types disallowed.

The UNDER clause in the GRANT/REVOKE statements applies to row types only. It cannot be used with opaque types.

GRANT/REVOKE 语句中的 UNDER 子句仅适用于行类型。它不能与不透明类型一起使用。

-9639 Grant/Revoke under on distinct of non-row types disallowed.

The UNDER clause in the GRANT/REVOKE statements applies to row types(and distinct of row-types) only. You cannot use the UNDER clause with non-row types or distinct of non-row types.

GRANT/REVOKE 语句中的 UNDER 子句仅适用于行类型（以及 distinct of row-types)。

不能在非行类型或 distinct 非行类型的情况下使用 UNDER 子句。

-9640 Cannot drop type (type_name): distinct type defined over the type.

Before you can drop a type, you must first drop all distinct types based on the type.

在删除类型之前，必须先根据类型删除所有 distinct 类型。

-9641 Drop type can only drop opaque type or distinct type.

The DROP TYPE statement applies to opaque and distinct types only. Use DROP ROW TYPE statement to drop row types.

DROP TYPE 语句仅适用于不透明和不同的类型。

使用 DROP ROW TYPE 语句来删除行类型。

-9642 A quoted string exceeds 32,768 bytes.

The system imposes a limit of 32,768 bytes on quoted strings. You cannot exceed this limit.

系统对引用的字符串施加 32,768 字节的限制。您不能超过此限制。

-9643 Type (type_name) is not hashable.

Hashing is used in GROUPBY queries and as a mechanism to eliminate duplicate values in DISTINCT and UNION, INTERSECT, or MINUS clauses. You cannot use types declared as non-hashable in these statements.

散列用于 GROUP BY 查询，并用作消除 DISTINCT 和 UNION、INTERSECT 或 MINUS 子句中重复值的机制。在这些语句中，不能使用声明为不可引用的类型。

-9645 Cannot execute cast from user-defined type to character format.

When you use the debugging feature of SPL to print the content of a user-defined, data-type variable, this error occurs if the database server cannot find or execute the cast function to convert from the given user-defined data type to character or long format.

当您使用 SPL 的调试功能打印用户定义的数据类型变量的内容时，如果数据库服务器无法找到或执行从给定用户定义的数据类型转换为字符或长格式的强制转换函数，则会发生此错误。

-9646 Result of a Boolean expression is not of Boolean type.

When a conditional expression, such as a WHERE clause or an IF clause,is evaluated in this statement, the result is not a Boolean value. All conditional expressions must evaluate to a Boolean value, so check that all conditional expressions evaluate correctly. If the expression does not, use appropriate casts to make it evaluate properly.

当在此语句中计算条件表达式（如 WHERE 子句或 IF 子句）时，结果不是布尔值。所有条件表达式都必须计算为布尔值，因此请检查所有条件表达式的计算是否正确。如果表达式没有，则使用适当的强制转换使其正确计算。

-9647 Cannot drop extended type <extended_type_name>: still in use.

The extended type that you are attempting to drop is being referenced by another type or table. Before you drop the extended type, first drop any type or table that refers to the extended type.

要删除的扩展类型正在由另一个类型或表引用。在删除扩展类型之前，首先删除引用扩展类型的任何类型或表。

-9648 Invalid value specified for a Boolean type't','T' or 'f','F' or NULL are the only valid values for boolean type.

“T”或“f”、“F”或 NULL 是布尔型的唯一有效值。

-9650 Right hand side of IN expression must be a COLLECTION type.

The column that is specified for the IN clause must be a COLLECTION type. For other data types you must specify values in a parenthesized list.

For example:为 IN 子句指定的列必须是 COLLECTION 类型。对于其他数据类型，必须在括号大小的列表中指定值。例如：SELECT * FROM CUSTOMER WHERE CUSTOMER_NUM IN (101);-9651 The statement failed because binary large objects are not allowed in the Union, Intersect, or Minus queries.

You selected a TEXT or BYTE column in a UNION, INTERSECT, or MINUS query. The projection clause of each query cannot include any TEXT or BYTE columns. These columns are not allowed in a UNION, INTERSECT, or MINUS clause because TEXT and BYTE columns cannot be tested for equality. A UNION ALL clause, however,can include TEXT and BYTE columns (in a standalone SELECT statement or in a UNION view).

您在 UNION、INTERSECT 或 MINUS 查询中选择了 TEXT 或 BYTE 列。每个查询的投影子句不能包括任何 TEXT 或 BYTE 列。这些列在 UNION、INTERSECT 或 MINUS 子句中是不允许的，因为不能测试 TEXT 或 BYTE 列是否相等。但是，UNION ALL 子句可以包括TEXT 或 BYTE 列（在独立 SELECT 语句中或在 UNION 视图中)。

-9653 UNDER privilege required to create subtype/subtable.

The user is not the owner of the type or table under which the statement attempted to create a subtype or subtable, and the user has not been granted the UNDER privilege on that type or table.

用户不是该语句试图创建子类型或子表的类型或表的所有者，并且该用户未被授予在该类型或表上的 UNDER 权限。

To create a named row type under an existing named row type or to create a table under an existing table, you must be the owner of the supertype or supertable or you must have been granted the UNDER privilege on that supertype or supertable. For example, the following sequence of statements allows a user named user2 to create a named row type and table under the row type and table that user1 created.

若要在现有命名行类型下创建命名行类型或在现有表下创建表，您必须是该超级类型或超级表的所有者，或者您必须已在该超级类型或超级表上被授予 UNDER 权限。例如，下面的语句序列允许名为 user 2 的用户在 user 1 创建的行类型和表下创建命名行类型和表。

-- As user named user1-- 作为名为 user 1 的用户CREATE ROW TYPE super_rt (int_col INT);GRANT USAGE ON TYPE super_rt TO user2;GRANT UNDER ON TYPE super_rt TO user2;CREATE TABLE super_table OF TYPE super_rt;GRANT UNDER ON super_table TO user2;-- As user named user2-- 作为名为 user 2 的用户CREATE ROW TYPE sub_rt (float_col FLOAT) UNDER user1.super_rt;CREATE TABLE sub_table OF TYPE sub_rt UNDER user1.super_table;-9654 The element types of the collection are not unique; explicit casting is required.

The element types of the complex type (row, set, multiset, or list) are not unique and cannot be converted from one complex type to another complex type by implicit casting. Use the explicit casting notation to explicitly cast the source complex type to the desired target complex type.

复杂类型（行、集、多集或列表）的元素类型不是唯一的，不能通过隐式转换从一种复杂类型转换为另一种复杂类型。使用显式转换表示法将源复杂类型显式转换为所需的目标复杂类型。

-9656 Cannot create a distinct type of type (serial or serial8 or bigserial).

The statement specified creation of a distinct data type as SERIAL or SERIAL8 or BIGSERIAL. A SERIAL or SERIAL8 or BIGSERIAL data type cannot be a distinct type.

语句指定创建 distinct 数据类型为 SERIAL 或 SERIAL 8 或 BIGSERIAL。 SERIAL 或SERIAL 8 或 BIGSERIAL 数据类型不能是 distinct 类型。

Remove DISTINCT from the statement or specify a different data type.

从语句中移除 DISTINCT 数据类型或指定不同的数据类型。

-9657 Cannot determine the data type of a collection in the given expression.

The data type of a collection used in the provided expression cannot be determined until run time. Casting the collection to a specific data type usually solves this problem.

在所提供的表达式中使用的集合的数据类型要到运行时才能确定。将集合转换为特定的数据类型通常可以解决此问题。

-9700 Routine (routine_name) ambiguous - more than one routine resolves to given signature.

This problem happens when an argument (or its source type or parent type) has implicit casts to the parameters of two or more routines.

当参数（或其源类型或父类型）对两个或多个例程的参数进行隐式转换时，就会发生此问题。

For example, assume two routines exist called routine_name(paramtype1)and routine_name(paramtype2), and routine_name is invoked with routine_name(argtype). Also, implicit casts exist from argtype to paramtype1 and argtype to paramtype2. In this case, this error is raised.

例如，假设存在两个例程-即 routine_name(paramtype1)和 routine_name(paramtype2)，并使用 routine_name(argtype) 调用 routine_name 。此外，隐式转换也存在于 argtype 到 paramtype 1，argtype 到paramtype 2 之间。在这种情况下，会引发此错误。

The error is also raised, if instead of argtype, argtype_dad which is in the source type hierarchy of argtype (if argtype is a distinct type)or in the super type hierarchy of argtype (if argtype is a row type)has casts to paramtype1 and paramtype2.

如果 argtype_dad 位于 argtype 的源类型层次结构（如果 argtype 是一个 distinct类型）或 argtype 的超级类型层次结构中（如果 argtype 是行类型)，则还会引发错误。

You will need to redefine the implicit casting scheme, such that only one casts exists from argtype to either paramtype1 or paramtype2 or remove one of the routines.

您将需要重新定义隐式转换方案，以便只存在从 argtype 到 paramtype 1 或 paramtype 2 或删除其中一个例程的一个强制转换。

-9701 An EXTERNAL PROCEDURE cannot have RETURN clause.

Do not specify the returns/returning clause to a PROCEDURE that is an external procedure. You can specify this clause for a SPL procedure,but specifying a RETURN clause to a procedure is highly discouraged.

不要将 returns/returning 子句指定为外部过程 PROCEDURE。可以为 SPL 存储过程指定此子句，但非常不鼓励为存储过程指定 RETURN 子句。

-9702 When a FUNCTION is created, the RETURN clause must be specified.

All functions must return a value. Specify a return clause or use a CREATE PROCEDURE statement.

所有函数都必须返回一个值。指定返回子句或使用 CREATE PROCEDURE 语句。

-9703 Modifiers VARIANT and NOT VARIANT cannot be used in the same routine.

Either VARIANT or NOT VARIANT can be specified either as a modifier or as a clause after the LANGUAGE clause. If both are specified, they must both be specified as VARIANT or as NOT VARIANT. Either make them consistent or remove one of the references as a modifier or as a clause after the LANGUAGE clause.

可以将 VARIANT 或 NOT VARIANT 指定为修饰符，也可以指定为 LANGUAGE 子句之后的子句。如果两者都被指定，则必须将它们都指定为 VARIANT 或 NOT VARIANT。要么使它们保持一致，要么将其中一个引用作为修饰符或在 LANGUAGE 子句之后作为子句删除。

-9704 For SPL routine, parameter must be named.

The name of the parameter in a CREATE FUNCTION or CREATE PROCEDURE statement is optional only for external routines. Specify the parameter name.

CREATE FUNCTION 或 CREATE PROCEDURE 语句中的参数名称仅对外部例程是可选的。指定参数名称。

-9705 The modifier (modifier-name) is not valid for SPL routines.

This message displays a modifier that you cannot specify for an SPL routine. The following modifiers are invalid for SPL routines: CLASS, CLIENT,HANDLESNULLS, INTERNAL, ITERATOR, PARALLELIZABLE, PERCALL_COST, SELFUNC, and STACK. Other modifiers might also be invalid.

此消息显示不能为 SPL 例程指定的修饰符。以下修饰符对 SPL 例程无效：CLASS、CLIENT、HANDLESNULLS、INTERNAL、ITERATOR、PARALLELIZABLE、PERCALL_COST、SELFUNC 和 STACK 。其他修饰符也可能无效。

-9706 END PROCEDURE/FUNCTION does not match with CREATE PROCEDURE/FUNCTION.

If you are using a CREATE PROCEDURE statement, the end clause must contain END PROCEDURE. If you are using a CREATE FUNCTION statement,the end clause must contain END FUNCTION. Do not mix and match PROCEDURE and FUNCTION keywords.

如果使用 CREATE PROCEDURE 语句，End 子句必须包含 END PROCEDURE。如果使用CREATE FUNCTION 语句，End 子句必须包含 END FUNCTION。不要混合和匹配程序和功能关键字。

-9707 Modifiers COMMUTATOR and NEGATOR are not allowed in procedure.

Because procedures do not return values, these modifiers are not allowed in a CREATE PROCEDURE statement. Use a CREATE FUNCTION statement or do not specify these modifiers.

因为存储过程不返回值，所以在 CREATE PROCEDURE 语句中不允许使用这些修饰符。使用CREATE FUNCTION 语句或不指定这些修饰符。

-9708 SELFUNC modifier can only be used in EXTERNAL FUNCTION.

Do not specify SELFUNC modifier to a SPL routine or an external procedure.

不要为 SPL 例程或外部过程指定 SELFUNC 修饰符。

-9709 More than one distinct type of the parameter type have cast to argument type.

This situation occurs if more than one distinct type of the source type of the parameter has casts from the argument type. For example, assume the routine routine_name(paramtype) exists. Both paramdist1 and paramdist2 are distinct types of paramdist1. The routine is invoked as routine_name(argtype). Casts also exist from argtype to paramdist1 and argtype to paramdist2. Because distinct types inherit all the routines defined on the source types, paramdist2 and paramdist1 inherit the routine routine_name. Thus the routine resolution cannot resolve the routine, and this error results.

如果参数的源类型有多个不同类型的参数具有参数类型的强制转换，则会发生这种情况。

例如，假设例程 routine_name(paramtype) 存在。paramdist1 和 paramdist2 都是不同类型的 paramdist1。例程作为 routine_name(argtype) 被调用。类型转换也从 argtype到 paramdist1， argtype 到 paramdist2 。因为不同的类型继承了在源类型上定义的所有例程，所以 paramdist2 和 paramdist1 继承了例程 routine_name。因此，例程解析不能解决例程，而此错误将导致此错误。

-9710 Overloading of built-in functions is not allowed.

Built-in functions such as dbinfo and trim should not be overloaded.

Change the name of the routine that you are creating so that it does not conflict with the names already used in the database server.

内置函数，如 dbinfo 和 trim 不应该重载。更改正在创建的例程的名称，使其不与数据库服务器中已经使用的名称冲突。

-9711 Late bound functions cannot have different number of return values Due to late binding, the function that is executed could change in the middle of query execution. This error is called if the number of values returned by the new function is not the same as the previous function.

All functions with the same name defined over a type hierarchy should have the same number of return values.

由于后期绑定，执行的函数可能会在查询执行过程中发生变化。如果新函数返回的值数与前一个函数不相同，则调用此错误。在类型层次结构上定义的所有名称相同的函数都应该具有相同数量的返回值。

-9712 Late bound functions cannot have different return types.

Due to late binding, the function that is executed could change in the middle of query execution. This error results if the type of values returned by the new function is not the same as the previous function.

All functions with the same name defined over a type hierarchy should have the same type of return values.

由于后期绑定，执行的函数可能会在查询执行过程中发生变化。如果新函数返回的值类型与前一个函数不相同，则会导致此错误。在类型层次结构上定义的所有名称相同的函数都应该具有相同类型的返回值。

-9713 Identifier too long - maximum allowed length for this identifier is 128.

The specific name specified in the CREATE PROCEDURE or CREATE FUNCTION statement is longer than 128 bytes. Shorten the name.

CREATE PROCEDURE 或 CREATE FUNCTION 语句中指定的特定名称大于 128 个字节。请缩短名称。

-9714 OUT parameter can only be the last parameter of a routine.

When an OUT parameter is specified in the CREATE FUNCTION statement, it must be the last parameter and the only parameter with the OUT option.

当在 CREATE FUNCTION 语句中指定 OUT 参数时，它必须是最后一个参数，也是唯一具有OUT 选项的参数。

-9715 A procedure cannot have any OUT parameters.

A CREATE PROCEDURE function cannot have OUT parameters. Only a CREATE FUNCTION statement can have OUT parameters in the parameter. The parameter specified as OUT should be the only and last parameter.

CREATE PROCEDURE 函数不能有 OUT 参数。只有 CREATE FUNCTION 语句才能在参数中包含 OUT 参数。指定为 OUT 的参数应该是唯一的也是最后一个参数。

-9716 This routine routine_name has the same specific name as another routine.

A specific name is unique within a name space. In a non-ANSI database,it is unique within a database. In an ANSI database, it is unique within the user's schema. Change the name to a unique name.

特定名称在名称空间中是唯一的。在非 ANSI 数据库中，它在数据库中是唯一的。在ANSI 数据库中，它在用户模式中是唯一的。将名称更改为唯一名称。

-9717 Owner name specified in the routine name and specific name must be the same.

If the specific name is qualified with the owner name, the owner name specified should be the same as the owner name used in qualifying the routine being created. If the routine name is not qualified, it should be the same as the current user.

如果特定名称与所有者名称限定，则指定的所有者名称应与用于限定正在创建的例程的所有者名称相同。如果例程名称没有限定，则应与当前用户相同。

-9718 Owner name specified in the specific name must be the current user.

-9719 A routine and an aggregate cannot share the same name.

An attempt to create a routine (UDR) with the same name as an aggregate is illegal. Also, creating an aggregate with the same name as a routine is also invalid. A routine name may not also match a built-in aggregate name, like sum(), count(), or max().

试图创建与聚合名称相同的例程 (UDR) 是非法的。此外，创建与例程同名的聚合也是无效的。例程名称也可能与内置聚合名称不匹配，例如 sum()、count() 或 max()。

Change the aggregate or the routine name that is causing the failure.

更改导致故障的聚合或例程名称。

-9720 Module name or language name specified is not valid.

The module name or language name that you specified in the ifx_replace_module() or ifx_unload_module() function call is not valid. The only valid language name for these functions is C.

您在 ifx_replace_module() 或 ifx_unload_module() 函数调用中指定的模块名称或语言名称无效。这些函数的唯一有效语言名称是 C。

Check the module names for correctness. Check if module path is included in the values for the DB_LIBRARY_PATH configuration parameter.

Replace the module name or language name, or update the value of DB_LIBRARY_PATH, and execute the function again.

检查模块名是否正确。检查 DB_LIBRARY_PATH 配置参数的值中是否包含模块路径。替换模块名称或语言名称，或更新 DB_LIBRARY_PATH 的值，然后再次执行该函数。

-9721 Module name could not be unloaded while in use.

You can use the ifx_unload_module() function only to unload an unused shared-object file; that is, when no executing SQL statements(in any database) are using any user-defined routines in the specified shared-object file.

您可以使用 ifx_unload_module() 函数来卸载未使用的共享对象文件；也就是说，当没有执行 SQL 语句（在任何数据库中）使用指定的共享对象文件中的任何用户定义的例程时。

Wait until all active SQL statements complete before trying to unload the shared-object file.

在尝试卸载共享对象文件之前，等待所有活动 SQL 语句完成。

-9722 Specify a non-zero SQL error number in the RAISE EXCEPTION statement.

You must provide a non-zero value for the SQL error number parameter in the RAISE EXCEPTION statement. To display your customized error string,specify -746 as the value of the SQL error.

必须为引发异常语句中的 SQL 错误号参数提供非零值。若要显示自定义错误字符串，请指定 -746 作为 SQL 错误的值。

-9740 Execution of remote routine (routine_name) with non-built-in types is not allowed.

When you invoke a remote routine you cannot pass complex data types or unsupported user-defined opaque types as routine arguments or return types.

Cast the unsupported data types to supported data types or create the routine in the local database.

调用远程例程时，不能将复杂的数据类型或不受支持的用户定义的不透明类型作为例程参数或返回类型传递。请将不支持的数据类型转换为受支持的数据类型或在本地数据库中创建例程。

-9741 Internal error - attempt to pass arguments in C style while requiring argument casts.

An internal programming error occurred. If this error recurs,note all circumstances and contact GBase Technical Support.

发生内部编程错误。如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-9743 Internal error - unable to determine all routines in statement.

A SQL statement that passed host variables into routines still had unknown routine argument types after host variable binding. Rerun the query without passing host variables to any routine or rerun the query and pass the correct number of host variables.

将主机变量传递给例程的 SQL 语句在宿主变量绑定之后仍然具有未知的例程参数类型。

重新运行查询，而不将主机变量传递给任何例程，或重新运行查询，并传递正确的主机变量数。

-9744 BUILTIN routine routine_name definition does not match internal operator.

This entry from SYSPROCEDURES with language BUILTIN does not match the internal format of the operator that is being overloaded. If this error recurs, note all circumstances and contact GBase Technical Support.

来自 SYSPROCEDURES 的带有 BUILTIN 语言的条目不匹配正在重载的操作符的内部格式。

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-9748 Cannot convert argument types when passing arguments by name, routine routine_name.

At least one argument requires a cast before it can be passed into the routine. Casts are not supported when passing arguments by name. Use explicit casts from the argument to the parameter type.

至少有一个参数需要强制转换才能传递到例程中。当按名称传递参数时，不支持强制转换。使用从参数到参数类型的显式转换。

-9750 Routine routine_name determined during PREPARE and BIND/EXECUTE return different types.

If host variables are used in the statement that is being prepared, in the absence of argument types information, the server tries to resolve to a routine that is most likely the routine to which the user intended to resolve. However, during BIND/EXECUTE time, in the presence of argument type information, the routine specified in the statement might resolve to a different routine. In that case, if the return types of the routine that the server originally selected are different than the one later resolved, this error is raised.

如果正在准备的语句中使用宿主变量，则在没有参数类型信息的情况下，服务器将尝试解析到最有可能是用户要解析的例程。但是，在绑定/执行期间，在存在参数类型信息的情况下，语句中指定的例程可能会解析为不同的例程。在这种情况下，如果服务器最初选择的例程的返回类型与后来解决的例程不同，则会引发此错误。

-9751 Cannot prepare the statement because the return type of the routine routine_name is not known.

The database server could not prepare the statement because a host variable was specified without a data type in a routine acting on a collection-derived table.

You must cast the host variable to a data type that the routine takes as an argument.

数据库服务器无法准备语句，因为在对集合派生的表进行操作的例程中指定了一个主机变量而没有数据类型。必须将主机变量转换为例程作为参数的数据类型。

For example, the following statement fails to prepare because the argument type of the ST_IsValid routine is not specified:例如，由于未指定 ST_IsValid 例程的参数类型，以下语句无法准备：SELECT * FROM table(function ST_IsValid(?));The following statement prepares successfully because the host variable is cast to a valid data type for the ST_IsValid routine:以下语句准备成功，因为主机变量被转换为 ST_IsValid 例程的有效数据类型：SELECT * FROM table(function ST_IsValid(?::st_multipolygon));-9752 Argument must be a Statement Local Variable or SPL variable or argument for an OUT or INOUT parameter.

UDRs with OUT/INOUT parameters cannot be used in the WHERE clause of a SELECT statement unless the OUT/INOUT parameters are defined as Statement Local Variables (SLV). For example除非 OUT/INOUT 参数定义为语句局部变量(SLV)，否则不能在 SELECT 语句的 WHERE 子句中使用带有 OUT/INOUT 参数的 UDRS。例如SELECT *FROM mytable WHERE foo (arg1, arg2, inout1, inout2, ...., inoutn) ;is not a valid syntax assuming that foo is a UDR which has OUT/INOUT parameters denoted by inout1...inoutn above. To use UDR foo in the WHERE clause the above example must be modified to不是一个有效的语法，假设 foo 是一个 UDR，其中包含上面 inout1...inoutn 表示的OUT/INOUT 参数。若要在 WHERE 子句中使用 UDR foo，必须将上述示例修改为SELECT myslv1 , ..., myslvN, *FROM mytable WHERE foo (arg1, arg2, myslv1 # svlDataType1,..., myslvN # svlDataTypeN);myslv1, ..., myslvN are the SLVs defined for the OUT/INOUT parameters with return datatype svlDataType1, ..., svlDataTypeN respectively.

Please note that it is optional to use the SLVs in the projection list for the SELECT statement.

myslv 1 ...、myslvN 分别是为 OUT/INOUT 参数定义的 SLV，其返回数据类型分别为svlDataType 1、...、svlDataTypeN。请注意，在 SELECT 语句的投影列表中使用 SLV是可选的。

You can invoke an SPL routine or a C UDR with OUT or INOUT parameters within a routine written in SPL. The parameter you pass into the OUT or INOUT parameter must be either an SPL variable or a parameter from another SPL routine, and the parameter cannot be passed as any form of expression.

您可以在用 SPL 编写的例程中调用带有OUT 或 INOUT 参数的 SPL 例程或 C UDR。传入OUT 或 INOUT 参数的参数必须是 SPL 变量或来自另一个 SPL 例程的参数，并且该参数不能作为任何形式的表达式传递。

Example:示例：create procedure p1(inout in1 integer);define a int;let a = in1;let in1 = a + 1;end procedure;create function f1(in1 integer) returning integer;call p1(in1);return in1;end function;-9753 Unable to find User Defined Routine with the given id.

The user defined routine with the specified ID cannot be found.

找不到具有指定 ID 的用户定义例程。

CAUSE The user defined routine ID is incorrect or has been changed.

原因用户定义的例程 ID 不正确或已更改。

ACTION Correct the ID in the prepared statement and then reprepare and execute the statement.

操作：更正准备语句中的 ID，然后重新准备并执行该语句。

-9754 No usage privilege.

The user does not have usage privilege on create functions or the user does not have grant/revoke usage privilege on a language. This error is returned when the user does not have the privilege to create a user-defined routine.

用户在CREATE函数上没有使用特权，或者用户在语言上没有授予/撤销使用权限。当用户没有权限创建用户定义的例程时，会返回此错误。

Ask user gbasedbt or a user with GRANT option privilege on the language to grant usage permission to you.

请询问 gbasedbt 用户或在语言上具有 GRANT 选项权限的用户授予您使用权限。

-9757 Remote iterator function is not supported in this context.

Remote iterator function used in the context of a table reference is not currently supported. Only local server iterator functions can be used.

当前不支持表引用上下文中使用的远程迭代器函数。只能使用本地服务器迭代器函数。

For example, this is not supported:例如，不支持：select * from table (function remote_db@remote_server:tv1());-9780 Statement-local variable cannot be an argument to a function called from outside the WHERE clause.

A user-defined routine (UDR) invocation that accepts a Statement Local Variable as an argument can be performed only in a WHERE clause of a Data Manipulation Language statement. This error results if this rule is violated. Move the UDR invocation inside a WHERE clause.

接受局部变量作为参数的用户定义例程 (UDR) 调用只能在数据操作语言语句的 WHERE 子句中执行。如果违反此规则，则会导致此错误。将 UDR 调用移到 WHERE 子句中。

-9781 SLV cannot be an argument to a function invoked explicitly by EXECUTE or CALL.

A routine that has an OUT parameter can only be invoked as part of a data-management language query (only in the WHERE clause). Do not invoke such a routine with a CALL or EXECUTE statement.

具有 OUT 参数的例程只能作为数据管理语言查询的一部分调用（仅在 WHERE 子句中)。

不要使用 CALL 或 EXECUTE 语句调用这样的例程。

-9782 Statement Local Variable has already been defined.

The same statement-local variable (SLV) is used for different OUT and INOUT parameters in a query. Ensure that the SLV is unique within a query.

相同的语句局部变量 (SLV) 用于查询中不同的 OUT 和 INOUT 参数。确保 SLV 在查询中是唯一的。

-9784 SLV (my_slv) has no producer-UDR; or is outside the scope of the producer-UDR.

A statement-local variable (SLV) is out of scope. For example, given a UNION,INTERSECT, or MINUS of two SELECT statements, one SELECT statement declares an SLV and the other SELECT statement references the SLV.

语句局部变量（SLV）超出作用域。例如，给定两个 SELECT 语句的 UNION、INTERSECT或 MINUS，一个 SELECT 语句声明一个 SLV，另一个 SELECT 语句引用 SLV 。

-9785 SLV (my_slv) cannot be accessed before it is produced by a UDR You cannot access the SLV until it is generated in the UDR. The following statement will produce the error:除非在 UDR 中生成 SLV，否则不能访问 SLV。以下语句将产生错误：SELECT slv_var FROM my_table WHERE foo_slv(slv_var # int)OR my_table.column IN (100,200,300);If the IN clause of the OR condition in the WHERE clause is evaluated before the UDR foo_slv is called, then slv_var is not initialized.

如果在调用 UDR foo_slv 之前计算 WHERE 子句中 OR 条件的 IN 子句，则 slv_var 不初始化。

-9786 Only iterative UDR allowed in this context.

The function used in the FROM clause of a select statement should be an iterative UDR.

The iterative UDRs written in SPL should have 'return with resume' clause.

SELECT 语句的 FROM 子句中使用的函数应该是迭代的 UDR。用 SPL 编写的迭代 UDR 应该有 'return with resume' 子句。

For example,例如，create procedure ret_x1() returning dint;define r1 dint;foreach select a into r1 from x1 return r1 with resume;end foreach;end procedure;The iterative UDRs written in C or Java should be create with 'with (iterator)' modifier in the CREATE FUNCTION statement and should handle the different states of iteration.

用 C 或 Java 编写的迭代 UDR 应该在 CREATE FUNCTION 语句中使用 'with iterator)'修饰符创建，并且应该处理不同的迭代状态。

create function fibgen(arg integer) returning integer with ( iterator)external name "$userfuncdir/fib.udr(fibGen)"language c;-9790 Language Manager initialization failed.

This error can occur in the following scenarios:此错误可能发生在下列方案中：1. The database server could not load internal C language or initialize data areas during server initialization.

在服务器初始化期间，数据库服务器无法加载内部C语言或初始化数据区域。

The following error message appears in the log:以下错误消息出现在日志中：Language Manager initialization failed.

语言管理器初始化失败。

An internal Language Manager error occurs during UDR loading or execution, causing a failure such as memory allocation or locking.
在 UDR 加载或执行过程中发生内部语言管理器错误，导致内存分配或锁定等失败。

The following error messages appears in the log:日志中显示以下错误消息：ERROR: Loading Routine routine_name procid = process_ID_number file:sqlmload.c ERROR: Unloading Routine routine_name procid = process_ID_number file:sqlmunld.c ERROR: Routine execution problem -- procname= procedure_name procid =process_ID_number file: sqlmexec.c-9791 User-defined routine execution failed.

This error occurs under the following circumstances:此错误发生在下列情况：1. A language problem occurred or an internal server error exists. In this case, the following log message is entered in the log:1. 出现语言问题或存在内部服务器错误。在这种情况下，在日志中输入以下日志消息：ERROR: Routine execution failed -- procname = routine_name procid =process_ID_number错误: Routine execution failed -- procname = routine_name procid =process_ID_number 2. The executing routine has caused one of the following exceptions:2. 执行例程导致下列例外情况之一：mem -- memory fault mem -- 内存错误ill -- illegal instruction ill -- 非法指令fpt -- floating point or divide by zero fpt -- 浮点或除以零sys -- system call problem sys -- 系统调用问题"xxx" -- SAPI layer exception explanation"xxx" -- SAPI 层例外的解释The following error message appears in the log:以下错误消息出现在日志中：ERROR: Routine execution trap -- procname = procedure_name procid =process_ID_number reason: error_string-9792 User-defined-routine language initialization failed.

A module failed to load, or an internal language error occurred. The following error message appears in the log:模块加载失败，或发生内部语言错误。以下错误消息出现在日志中：ERROR: Initializing Language language_name Module module_name-9793 User Defined Routine () module load failed.

The following error message appears in the log:以下错误消息出现在日志中：ERROR: Loading Module A bad external name, missing file, or wrong permissions might cause this error. Log message contains the UNIX error number encountered and the actual module name being used. For the C language on UNIX, the following log message might appear:外部名称错误、文件丢失或权限错误可能导致此错误。日志消息包含所遇到的 UNIX 错误号和正在使用的实际模块名。对于 UNIX 上的 C 语言，可能会出现以下日志消息：: C Language Module can't load In the log message, is the current UNIX error number, is the module name from the catalog, and is the dlerror() explanation.

在日志消息中，是当前的 UNIX 错误号，; 是目录中的模块名，是 dlerror() 解释。

-9794 User-defined-routine load failed.

The following error message appears in the log:下面的错误消息出现在日志中：Loading Routine routine_name procid = process_ID_number The routine routine_name is not found in the module, possibly because of a bad external name or the wrong module. The log message log_message_number is probably -1, and error_message_string is the database routine name as opposed to the symbol that was not found.

例程 routine_name 在模块中找不到，可能是因为外部名称错误或模块错误。日志消息log_message_number 可能是 -1，error_message_string 是数据库例程名称，而不是未找到的符号。

-9795 User-defined-routine unload failed.

The following error message appears in the log:以下错误消息出现在日志中：ERROR: Unloading Routine error_name procid = process_ID_number-9796 User-defined routine module unload failed.

An internal system error occurred from a call to dlclose for Solaris C modules. The following error message appears in the log:调用 Solaris C 模块时发生内部系统错误。以下错误消息出现在日志中：ERROR: Unloading Module error_string-9797 User-defined routine language shutdown failed.

The language did not shut down correctly. Probably an internal system error occurred. The following error message appears in the log:语言没有正确地关闭。可能发生了内部系统错误。以下错误消息出现在日志中：ERROR: error_string Language Shutdown-9798 User-defined routine language lookup failed.

Language information is not defined in the system. Either the routine definition is wrong, or something happened to the data dictionary. The following error message appears in the log:系统中没有定义语言信息。要么是常规定义错误，要么是数据字典发生了一些事情。以下错误消息出现在日志中：ERROR: Language error_string -- lookup failed-9799 User-defined routine vitual-processor context-switch failed.

The database server could not switch to or back from the needed VP during load, unload, or execution. The VP class could be wrong in the routine definition, or the VPCLASS parameter could be missing from the onconfig file. The following error messages appear in the log:在加载、卸载或执行期间，数据库服务器无法切换到所需的 VP 或从所需的 VP 切换回来。VP 类在例程定义中可能出错，或者 onconfig 文件中缺少 VPCLASS 参数。以下错误消息出现在日志中：ERROR: Routine execution VP switch failed -- new VP error_string ERROR: Routine execution VP switch failed -- old VP id = VP_ID Make sure the VP class is correct in the routine definition. Also,check the ONCONFIG file to make sure that it includes a VPCLASS parameter for this type of virtual processor and that the setting of the JVPCLASSPATH parameter is correct.

确保 VP 类在例程定义中是正确的。此外，请检查 ONCONFIG 文件，以确保它包含此类虚拟处理器的 VPCLASS 参数，并确保 JVPCLASSPATH 参数的设置是正确的。

-9800 Table table_name is typed.

You cannot add a type to a table that is already typed. Drop the table type and try adding the type again.

不能将类型添加到已键入的表中。删除表类型，然后再次添加该类型。

-9801 Cannot alter table table_name to add type. Incompatible.

The column names and the column types of the table do not match the field names and the field types of the type. Change them to statements.

表的列名和列类型与类型的字段名和字段类型不匹配。把它们改为语句。

-9802 Cannot alter typed table <table_name>.

The only valid ALTER TABLE statement for a typed table is one that drops the table type.

类型表的唯一有效的 ALTER TABLE 语句是删除表类型的语句。

If you need to use any other ALTER TABLE statement on the table, first drop the table type.

如果您需要在表上使用任何其他 ALTER TABLE 语句，那么首先删除表类型。

-9803 Cannot create typed view . Incompatible.

Either you attempted to use a BYTE or TEXT field in a typed view or the column names and the column types of the view do not match the field names and the field types of the type.

尝试在类型化视图中使用 BYTE 或 TEXT 字段，或者视图的列名和列类型与类型的字段名和字段类型不匹配。

Remove any BYTE or TEXT fields or change the field types to match those of the underlying columns.

删除任何 BYTE 或 TEXT 字段，或更改字段类型以匹配基础列的字段类型。

-9804 Cannot generate ROWIDS on typed table <table_name>.

Cannot have a ROWIDS column in a typed table. Either untype the table with ALTER TABLE or do not create a ROWID column.

无法在类型化表中有 ROWIDS 列。要么用 ALTER TABLE 取消表类型，要么不创建 ROWID列。

-9805 SERIAL/SERIAL8/BIGSERIAL data types allowed only as table column types.

You cannot have SERIAL/SERIAL8/BIGSERIAL data types in CREATE ROW statements.

They are allowed only as table-column types.

不能在 CREATE ROW 语句中具有 SERIAL/SERIAL 8/BIGSERIAL 数据类型。它们只允许作为表列类型。

-9806 Cannot have duplicate/null field names in unnamed row types.

The CREATE ROW TYPE statement has duplicate field names or is missing one or more field names.

CREATE ROW 类型语句具有重复的字段名，或者缺少一个或多个字段名。

Specify a unique name for each field in the CREATE ROW TYPE statement.

为 CREATE ROW TYPE 语句中的每个字段指定唯一名称。

-9807 Temporary table <temptable_name> cannot be created with a type.

You cannot create temporary tables with types; typed tables are only for permanent tables. Instead, try using the following example to create a temporary table:不能创建带有类型的临时表；类型表仅用于永久表。相反，尝试使用以下示例创建一个临时表：Instead of:而不是：CREATE ROW TYPE rowtypename (columnname int);CREATE TEMP TABLE tablename OF TYPE rowtypename;use:使用：CREATE TEMP TABLE tablename (columnname int);-9808 The subtable type must be a subtype of the supertable type.

When creating a table hierarchy of supertable and subtable, the subtype for that subtable must also be a subtype of the supertable type (supertype). There must be a type hierarchy defined before the corresponding table hierarchy can be defined.

在创建超级表和子表的表层次结构时，该子表的子类型也必须是超级表类型（父类型）的子类型。在定义相应的表层次结构之前，必须定义类型层次结构。

-9809 Cannot specify blobspace names on TEXT or BYTE field types.

When specifying TEXT or BYTE fields in a complex type, do not specify the name of the blobspace for that data type. The server uses the default partition blobspace for that TEXT or BYTE data type.

在复杂类型中指定 TEXT 或 BYTE 字段时，不要为该数据类型指定 blobspace 的名称。

服务器对该 TEXT 或 BYTE 数据类型使用缺省分区 blobspace。

-9810 Smart-large-object error.

An error occurred during the processing of a smart large object.

在处理智能大对象时发生错误。

For more information, check the accompanying, detailed smart-large-object error code.

有关更多信息，请查看附随的、详细的智能大对象错误代码。

-9811 Invalid smart-large-object fd (<lo_fd>).

An attempt was made to access a smart large object using an invalid LO file descriptor. Check that the LO file descriptor you supplied is correct and that the smart large object is still open.

尝试使用无效的 LO 文件描述符访问智能大对象。检查您提供的 LO 文件描述符是否正确，以及智能大对象是否仍处于打开状态。

-9812 Cannot do implicit begin work.

Internal error. This error can be caused by many different situations,If the error reoccurs, note all circumstances and contact GBase Support.

内部错误此错误可能是由许多不同的情况引起的，如果错误再次发生，请注意所有情况并与GBase支持部门联系。

GBase 8s Dynamic Server implicitly begins transactions for executing SQL statements. Sometimes, GBase 8s Dynamic Server implicitly uses a separate transaction while recompiling statements within a procedure written in the Stored Procedure Language to write the new plan to the catalog. In that case,a failure to begin work results in the failure to execute the procedure.

GBase 8s Dynamic Server 隐式地开始执行 SQL 语句的事务。有时，GBase 8s Dynamic Server 在重新编译用存储过程语言编写的过程中的语句时隐式使用单独的事务，以便将新计划写入目录。在这种情况下，无法开始工作将导致无法执行存储过程。

-9813 Cannot do implicit commit work.

Internal error. This error can be caused by many different situations,If the error reoccurs, note all circumstances and contact GBase Technical Support.

内部错误此错误可能是由许多不同的情况引起的，如果错误再次发生，请注意所有情况并与 GBase 技术支持部门联系。

GBase 8s Dynamic Server implicitly commits transactions for executing SQL statements. Sometimes, GBase 8s Dynamic Server implicitly uses a separate transaction while recompiling statements within a procedure written in the Stored Procedure Language to write the new plan to the catalog. In that case,a failure to commit work results in the failure to execute the procedure.

GBase 8s Dynamic Server 隐式提交用于执行 SQL 语句的事务。有时，GBase 8s Dynamic Server 在重新编译用存储过程语言编写的过程中的语句时隐式使用单独的事务，以便将新计划写入目录。在这种情况下，未能提交工作将导致执行过程失败。

-9814 Invalid default sbspace name (sbspace_name)).

The database server is trying to create a smart large object in the default sbspace, but the sbspace does not exist. Check that the SBSPACENAME parameter in the ONCONFIG file is the name of an existing sbspace. If necessary, the database server administrator can create an sbspace using the onspaces command.

数据库服务器试图在缺省的 sbspace 中创建一个智能大对象，但 sbspace 不存在。检查ONCONFIG 文件中的 SBSPACENAME 参数是否是现有 sbspace 的名称。如果有必要，数据库服务器管理员可以使用 onspaces 命令创建 sbspace 。

-9815 Invalid filename specification (file_spec).

You are calling a function that creates an operating-system file, but the filename specification supplied is not valid.

您正在调用一个创建操作系统文件的函数，但提供的文件名规范无效。

-9816 Btree index not allowed on a column of this datatype.

You have attempted to use a B-tree index on a column that contains one of the following datatypes: blob, clob, json, bson. Remove the statement that attempts to create an index on one of these data types from your program.

您已经尝试在包含以下数据类型之一的列上使用 B-tree 索引：blob、clob、json、bson。从程序中删除试图为其中一种数据类型创建索引的语句。

-9818 Error detected in sql smart-large-object hash table.

Internal error. Contact GBase Technical Support.

内部错误与 GBase 技术支持部门联系。

-9819 Column (column_name) incorrect type for storage in sbspace.

You have attempted to store a column in an sbspace that is not an appropriate type. Only CLOB and BLOB columns can be stored in sbspaces.

Columns of types TEXT and BYTE may not be stored in an sbspace.

您已经尝试将列存储在不适当类型的 sbspace 中。只有 CLOB 和 BLOB 列可以存储在sbspaces 中。 TEXT 和 BYTE 类型的列可能不会存储在 sbspace 中。

-9820 SQL SBLOB error: no such sbspace.

The most likely problem is that an operation specifies an sbspace by name (for example, in the PUT clause of a CREATE TABLE statement),but that sbspace has not been created.

最可能的问题是，操作按名称指定 sbspace （例如，在 CREATE TABLE 语句的 PUT 子句中），但 sbspace 尚未创建。

You can run the onstat utility with the -d option to see the names of sbspaces created. Ask the database server administrator about creating a new sbspace.

您可以使用 -d 选项运行 onstat 实用程序来查看创建的 sbspace 的名称。询问数据库服务器管理员有关创建新的 sbspace 的问题。

-9823 Inconsistent use of procedure named return parameters.

A procedure has duplicate return parameter names or only a partial list of return parameter names.

存储过程具有重复的返回参数名称或返回参数名称的部分列表。

Example of error:错误示例：RETURNING INT AS customer, INT AS customer; -- error RETURNING INT AS customer, INT; -- error-9824 Cannot perform more than one online create/drop index operation on table.

-9825 Online create/drop index not allowed on VII indexes.

-9826 Cannot perform online create/drop index operation along with storage optimization operation.

-9827 The sbspace specified by the SYSSBSPACENAME configuration parameter does not exist (syssbspace_name).

The database server failed to create a smart large object in the sbspace that is specified by the SYSSBSPACENAME configuration parameter because the sbspace does not exist. Check that the value of the SYSSBSPACENAME configuration parameter in the onconfig file is the name of an existing sbspace. If necessary, the database server administrator can create an sbspace using the onspaces command and update the value of the SYSSBSPACENAME configuration parameter in the onconfig file.

由于 sbspace 不存在，数据库服务器未能在由 SYSSBSPACENAME 配置参数指定的sbspace 中创建智能大对象。检查 onconfig 文件中 SYSSBSPACENAME 配置参数的值是否为现有 sbspace 的名称。如果有必要，数据库服务器管理员可以使用 onspaces 命令创建 sbspace，并更新 onconfig 文件中 SYSSBSPACENAME 配置参数的值。

The UPDATE STATISTICS operation might require an existing sbspace,which is specified by the SYSSBSPACENAME configuration parameter.

UPDATE STATISTICS 操作可能需要现有的 sbspace，该空间由 SYSSBSPACENAME 配置参数指定。

-9831 Could not find opclass id opclass_ID while resolving compare routine for index.

The operator class for one or more key parts of the index no longer exists in the database. The index is no longer valid and must be dropped.

数据库中不再存在索引的一个或多个关键部分的运算符类。索引不再有效，必须删除。

-9832 Could not find routine routine_name while resolving compare routine.

Either the comparison routine for one or more key parts of the index no longer exists in the database, or the comparison routine required to perform a sort cannot be found. You need to re-create the compare routine. If an index is involved, the index needs to be dropped.

要么数据库中不再存在索引的一个或多个关键部分的比较例程，要么找不到执行排序所需的比较例程。您需要重新创建比较例程。如果涉及索引，则需要删除索引。

-9833 Could not find extended type type_ID for index.

The type of one or more key parts of the index no longer exists in the database. The index is no longer valid and must be dropped.

数据库中不再存在索引的一个或多个关键部分的类型。索引不再有效，必须删除。

-9835 Could not find routine ID routine_ID for functional key.

The routine identified by the routine ID for one or more functional key parts no longer exists in the database. The index is no longer valid and must be dropped.

数据库中不再存在由一个或多个功能关键部件的例程 ID 标识的例程。索引不再有效，必须删除。

-9836 Could not initialize sequence for routine .

A user-defined routine is missing a statcollect() or compare() function.

用户定义的例程缺少一个 statcollect() 或 compare() 函数Add the missing function to the user-defined routine.

将缺失的函数添加到用户定义的例程中。

-9838 Cannot create operator class for a primary access_method.

You cannot create an operator class for a primary access_method. For a list of available secondary access_methods, you can perform the following query.

不能为主 access_method 创建运算符类。对于可用的辅助 access_method 列表，可以执行以下查询。

SELECT * FROM GBASEDBT.SYSAMS WHERE AM_TYPE = 'S';-9839 Cannot mix generic and specific operators in an operator class.

If you specify the full function signature for one of the strategy functions in the operator class, you need to specify the function signatures for all of the strategy functions.

如果为运算符类中的某个策略函数指定了完整的函数签名，则需要为所有策略函数指定函数签名。

-9840 Invalid number of strategies or support function for btree.

You must specify no more than five operators (operators implementing lessthan, lessthanorequal, equal, greaterthanorequal, and greaterthan)and exactly one support function (the comparison function) in CREATE OPCLASS for the btree access_method.

必须为 btree access_method 在 CREATE OPCLASS 中指定不超过五个操作符（实现小于、小于等于、相等、大于等于和大于）和恰好一个支持函数（比较函数）。

-9841 Operator class for key part not specified or invalid.

The operator class specified in one or more of the key parts is invalid. Probable causes for this error include:在一个或多个关键部件中指定的运算符类无效。造成此错误的可能原因包括：* You might be using an operator class for a different access_method than the one with which you are creating the index.

* 您可能使用运算符类来进行与创建索引的方法不同的 access_method 。

* If the access_method that you use does not have a default operator class associated with it, you must explicitly specify the operator class for each key part.

* 如果使用的 access_method 没有与其关联的缺省运算符类，则必须为每个关键部件显式指定运算符类。

* Data type of the key column and that of the operator class do not match, where strategy function signatures are specified for the operator class.

* 键列的数据类型与运算符类的数据类型不匹配，其中为运算符类指定了策略函数签名。

-9842 Specification of ASC/DESC only applicable to btree.

You cannot specify ASC or DESC in the key part if you are using an access_method other than btree.

如果使用的是 btree 以外的 access_method ，则不能在关键部件中指定 ASC 或DESC 。

-9843 Invalid number of arguments for functional key.

A functional key part can only take between 1 and 16 arguments.

一个函数关键部分只能包含 1 到 16 个参数。

-9844 Invalid function function_name used in a functional key.

The function used in a CREATE INDEX statement cannot be used as a functional key part. Make sure that the function you use is not a variant function.

在 CREATE INDEX 语句中使用的函数不能用作功能键部分。确保您使用的函数不是变量函数。

-9845 access_method access_method_name does not exist in database.

The access_method used in a CREATE INDEX or CREATE OPCLASS statement does not exist. Before you can use an access_method, you must create it with a CREATE ACCESS_METHOD statement. For a list of available access methods, see gbasedbt.sysams.

在 CREATE INDEX 或 CREATE OPCLASS 语句中使用的 access_method 不存在。在使用access_method 之前，必须使用 CREATE ACCESS_METHOD 语句创建它。有关可用access_method 的列表，请参见 gbasedbt.sysams。

-9846 Operator class operator_class_name does not exist in database.

The operator class used in a CREATE INDEX statement does not exist.

Before you can use an operator class, you must create it with a CREATE OPCLASS statement. See gbasedbt.sysopclasses for a list of available operator classes.

在 CREATE INDEX 语句中使用的操作符类不存在。在使用运算符类之前，必须使用CREATE OPCLASS 语句创建它。有关可用运算符类的列表，请参见gbasedbt.sysopclasses。

-9848 Functional key part cannot use a variant function function_name.

The function used in a CREATE INDEX statement for a functional key part must be a nonvariant function (that is, it must be created with the NOT VARIANT modifier in the CREATE FUNCTION statement).

函数关键部分的 CREATE INDEX 语句中使用的函数必须是一个非变量函数(也就是说，它必须使用 CREATE FUNCTION 语句中的不变体修饰符创建)。

-9849 Compare routine routine_name cannot be in SPL The compare routine used for a generic B-tree cannot be written in SPL.

You should rewrite the compare routine in C.

泛型 B-tree 的比较例程不能用 SPL 编写。您应该用 C 重写比较例程。

-9851 access_method access_method_name already exists in database.

The access_method that you are creating with a CREATE ACCESS_METHOD statement already exists. You must use a new name.

使用 CREATE ACCESS_METHOD 语句创建的 access_method 已经存在。你必须用一个新的名字。

-9852 Improper purpose purpose_name used for access_method.

A purpose used with the CREATE ACCESS_METHOD or ALTER ACCESS_METHOD statement is improper. It might be spelled incorrectly. Otherwise, it is used incorrectly in combination with the other purposes, or it is a purpose that is not appropriate for the type of access_method. For example, an access_method cannot be created with AM_DELETE if AM_ROWIDS is not used, and AM_GETBYID cannot be used for a secondary access method. Correct the spelling of the purpose or change one or more of the purposes until the combination of purposes is valid.

CREATE ACCESS_METHOD 或 ALTER ACCESS_METHOD 语句使用的目的是不正确的。可能拼错了。否则，它与其他用途不正确地结合使用，或者它是不适合于 access_method 类型的目的。例如，如果不使用 AM_ROWIDS，则无法使用 AM_DELETE 创建 access_method ，而AM_GETBYID 不能用于辅助 access_method 。更正目的拼写或更改一个或多个目的，直到目的组合有效为止。

-9853 Duplicate purpose purpose_name used for access_method.

A purpose used with the CREATE ACCESS_METHOD or ALTER ACCESS_METHOD statement has been used more than once. Change the purposes used until no duplicates exist.

CREATE ACCESS_METHOD 或 ALTER ACCESS_METHOD 语句使用的目的已不止一次。更改所使用的用途，直到不存在重复项为止。

-9854 Required purpose purpose_name not used for access_method.

A required purpose has not been used with the CREATE ACCESS_METHOD statement, or a required or default purpose has been removed with the ALTER ACCESS_METHOD statement. For example, AM_SCANCOST has a default value if not used with the CREATE ACCESS_METHOD statement, but it cannot be dropped with the ALTER ACCESS_METHOD statement. Change the purposes used until the required purposes are included or preserved.

CREATE ACCESS_METHOD 语句没有使用必需的目的，或者 ALTER ACCESS_METHOD 语句删除了一个必需的或缺省的目的。例如，AM_SCANCOST 如果不与 CREATE ACCESS_METHOD 语句一起使用，则有一个缺省值，但不能使用 ALTER ACCESS_METHOD 语句删除它。更改所使用的用途，直到包括或保留所需的用途为止。

-9855 Improper value used for purpose purpose_name for access_method.

A purpose has been used with an improper value in a CREATE ACCESS_METHOD or ALTER ACCESS_METHOD statement. For example, an integer cannot be used for AM_SPTYPE. Use the proper type of value for the purpose.

在 CREATE ACCESS_METHOD 或 ALTER ACCESS_METHOD 语句中，使用了一个不正确的值。

例如，AM_SPTYPE 不能使用整数。为此目的使用适当类型的值。

-9856 Index not created because the table's access_method doesn't support rowids.

A CREATE INDEX statement was used on a table whose access_method does not support rowids. Because rows from the table are fetched by the index by rowid, the index cannot be created.

在 access_method 不支持 rowids 的表上使用了 CREATE INDEX 语句。因为表中的行是由 rowid 索引获取的，因此无法创建索引。

-9857 Unknown space space_name used for external table/index.

A CREATE TABLE or CREATE INDEX statement has an IN clause that references an extspace that does not exist. Use an existing extspace.

CREATE TABLE 或 CREATE INDEX 语句具有一个 IN 子句，该子句引用不存在的 extspace。使用现有的 extspace。

-9858 Unsupported option option_name used for an external table/index.

An ALTER TABLE or ALTER INDEX statement has an option that is not supported by the access_method. Remove the option.

ALTER TABLE 或 ALTER INDEX 语句具有 access_method 不支持的选项。删除该选项。

-9859 Index not created because its access_method does not support unique keys.

A CREATE UNIQUE INDEX statement or CREATE DISTINCT INDEX statement used an access_method that does not support unique keys.

CREATE UNIQUE INDEX 语句或 CREATE DISTINCT INDEX 语句使用不支持唯一键的access_method 。

Remove UNIQUE from the CREATE INDEX statement or remove DISTINCT from the CREATE INDEX statement.

从 CREATE INDEX 语句中删除 UNIQUE 或从 CREATE INDEX 语句中删除 DISTINCT。

-9860 Improper access_method used.

A CREATE TABLE statement used a secondary access_method or a CREATE INDEX statement used a primary access_method. Use a primary access method with CREATE TABLE and a secondary access_method with CREATE INDEX.

CREATE TABLE 语句使用辅助 access_method ，或者 CREATE INDEX 语句使用主access_method 。使用包含 CREATE TABLE 的主 access_method 和带有 CREATE INDEX的辅助 access_method 。

-9861 Improper access_method parameter information used for an external table/index.

A CREATE TABLE or CREATE INDEX statement is using an access_method with parameter information that is improper. For example, the identifier might be longer than 18 bytes, or the value might be longer than 236 bytes. Correct the parameter information.

CREATE TABLE 或 CREATE INDEX 语句使用的是带有不适当参数信息的 access_method 。

例如，标识符可能大于 18 个字节，或者值可能大于 236 个字节。更正参数信息。

-9862 Could not initialize or execute access_method routine.

An access_method routine failed to execute properly. The RSAM error code gives more information.

access_method 例程无法正确执行。RSAM 错误代码提供了更多信息。

-9863 Opclass opclass_name already exists in database.

The opclass being created with a CREATE OPCLASS statement already exists. Use a new name.

使用 CREATE OPCLASS语句创建的 opclass 已经存在。用一个新的名字。

-9864 Improper strategy definition.

A CREATE OPCLASS statement is using a strategy definition that is improper. For example, a strategy might take at most three arguments.

Correct the strategy definition.

CREATE OPCLASS 语句使用的是不适当的策略定义。例如，一项策略最多可能包含三个参数。修正策略定义。

-9865 Improper support definition.

A CREATE OPCLASS statement is using a support definition that is improper. For example, a support name can be at most 18 bytes. Correct the support definition.

CREATE OPCLASS 语句使用的支持定义不正确。例如，支持名最多可以是 18 个字节。

更正支持定义。

-9867 access_method access_method_name not found.

A DROP ACCESS_METHOD or ALTER ACCESS_METHOD statement uses an access method that does not exist. Use the correct access_method.

DROP ACCESS_METHOD 或 ALTER ACCESS_METHOD 语句使用不存在的 access_method 。

使用正确的 access_method 。

-9868 Not owner of access_method.

The person executing a DROP ACCESS_METHOD or ALTER ACCESS_METHOD statement is not the owner of the access_method or does not have DBA privileges.

执行 DROP ACCESS_METHOD 或 ALTER ACCESS_METHOD 语句的人不是 access_method 的所有者，也不具有 DBA 权限。

-9869 Cannot drop access_method access_method_name: still in use.

A DROP ACCESS_METHOD statement cannot be used if any tables or indexes are defined using that access_method. Drop the tables or indexes first and then drop the access_method.

如果使用 access_method 定义了任何表或索引，则不能使用 DROP ACCESS_METHOD语句。先删除表或索引，然后删 access_method 。

-9870 Cannot alter access_method access_method_name: still in use.

An ALTER ACCESS_METHOD statement cannot be used while anyone is using the access_method. Wait until no one is using the access_method and try again.

在任何人使用 access_method 时，都不能使用 ALTER ACCESS_METHOD 语句。等待，直到没有人使用 access_method ，然后再试一次。

-9871 Alter fragment attach/detach for external table not supported.

The ALTER FRAGMENT statement cannot be used for a table or index that uses an access_method. Either create a new table with the desired properties and copy the data from the old table to the new table or create a new index with the desired properties.

ALTER FRAGMENT 语句不能用于使用 access_method 的表或索引。要么创建一个具有所需属性的新表，然后将数据从旧表复制到新表，要么创建一个具有所需属性的新索引。

-9872 Cannot drop operator class operator_class_name: still in use.

The operator class is being used in an existing index and therefore cannot be dropped. Drop all the indexes that use the operator class before you drop it.

运算符类正在现有索引中使用，因此不能删除。删除所有使用运算符类的索引。

-9873 Not owner of operator class.

You cannot drop an operator class unless you are the owner or the database administrator. Contact the database administrator or the owner of the operator class.

除非您是所有者或数据库管理员，否则不能删除运算符类。请与数据库管理员或操作员类的所有者联系。

-9874 Cannot rename database if it has a virtual table or index.

You cannot rename a database if the database has any tables created using primary access_method (also known as virtual table interface) or indices using secondary access_method (also known as virtual index interface). R-TREE indices are implemented using secondary access_method and therefore, databases with R-TREE indices cannot be renamed.

如果数据库具有使用主 access_method 创建的表（也称为虚拟表接口）或使用辅助access_method 创建的索引(也称为虚拟索引接口)，则不能重命名数据库。R-TREE 索引是使用辅助 access_method 实现的，因此，不能重命名具有 R-TREE 索引的数据库。

-9875 Bad internal structure for collection data: unknown flag value.

The structure of collection or row data might be corrupted.

收集数据或行数据的结构可能已损坏。

Report this situation to GBase Technical Support.

请向 GBase 技术支持部门报告此情况。

-9878 An implied insert column does not accept NULLs.

The statement attempted an implied insert of a null value into a column that does not accept null values.

该语句试图将空值的隐含插入到不接受空值的列中。

Rewrite the INSERT statement to provide a value for any column that do not accept null values, or redefine the column to accept nulls.

请重写 INSERT 语句为任何不接受空值的列提供值，或重新定义该列以接受空值。

-9880 Storage space is incompatible with the access_method.

The operation was unsuccessful because the specified storage space cannot be used by the access_method referenced in the SQL statement.

操作失败，因为 SQL 语句中引用的 access_method 无法使用指定的存储空间。

Change the statement to specify a storage space that is of a type that the access_method supports. To find out whether the access_method supports an extspace (external storage) or sbspace (smart-large-object storage), query the sysams system catalog table for access_method name that you specify in the CREATE TABLE statement USING clause. Refer to the am_sptype value for that access_method. The following values indicate the type of storage space that you can use with the access_method:请更改该语句以指定 access_method 支持的类型的存储空间。若要了解 access_method是否支持extspace（外部存储）或sbspace（智能大对象存储），请查询 sysams 系统目录表以获取使用子句在 CREATE TABLE 语句中指定的 access_method 名称。有关该access_method ，请参考 am_sptype 值。以下值指示可以与 access_method 一起使用的存储空间类型：* 'X' indicates that the access_method supports only extspaces* ‘X’表示 access_method 只支持 extspaces* 'S' indicates that the access_method supports only sbspaces* ‘S’表示 access_method 只支持 sbspace* 'A' indicates that the access_method supports both extspaces and sbspaces* ‘A’表示 access_method 同时支持 extspace 和 sbspace Important: You cannot use a dbspace (Dynamic Server table space storage)with a user-defined access_method. A user-defined access_method is one.

注意：不能使用 dbspace（动态服务器表空间存储）和用户定义的 access_method 。用户定义的 access_method 是一种。

For more information about the type of storage spaces that the access_method supports, refer to the access-method user guide.

有关 access_method 支持的存储空间类型的更多信息，请参阅 access_method 用户指南。

-9882 access_method AM_SPTYPE purpose value is invalid.

The operation failed because the access_method specified in the SQL statement has an invalid value, , for its AM_SPTYPE purpose value.

操作失败，因为 SQL 语句中指定的 access_method 的 AM_SPTYPE 目的值无效。

Because processing for the CREATE PRIMARY ACCESS_METHOD and CREATE SECONDARY ACCESS_METHOD SQL statements validates the AM_SPTYPE value, this error should only occur if the row associated with the access_method in the sysams system catalog table was explicitly updated after the access_method was created.

因为对 CREATE PRIMARY ACCESS_METHOD 和 CREATE SECONDARY ACCESS_METHOD SQL 语句的处理会验证 AM_SPTYPE 值，因此只有在创建 access_method 后显式更新与 sysams 系统目录表中的 access_method 关联的行时，才会发生此错误。

Ask the access-method provider or database administrator to change the AM_SPTYPE value for the access_method with the ALTER ACCESS_METHOD statement.

请 access_method 提供程序或数据库管理员使用 ALTER ACCESS_METHOD 语句更改access_method 的 AM_SPTYPE 值。

-9883 Could not determine the type of storage space .

An error occurred while the database server was looking up the type of the specified storage space (dbspace, sbspace, or extspace).

Usually this problem is related to accessing the sysmaster:sysextnames table.

For more information, refer to the accompanying ISAM error code.

数据库服务器查找指定存储空间的类型（dbspace、sbspace 或 extspace）时发生错误。

通常，这个问题与访问 sysmaster:sysextnames 表有关。有关更多信息，请参阅附带的ISAM 错误代码。

-9884 No default storage space exists for the access_method.

None of the storage-space types supported by the access_method has a default storage space.

access_method 支持的任何存储空间类型都没有默认的存储空间。

To correct this error, you can take either of the following actions:若要更正此错误，可以采取下列任一操作：* In your SQL statement, explicitly specify the storage spaces for the access_method to use.

* 在 SQL 语句中，显式指定 access_method 要使用的存储空间。

* If the access_method supports sbspaces, ask your database server administrator to create a sbspace with the onspaces utility and set the ONCONFIG parameter SBSPACENAME to that sbspace name.

* 如果 access_method 支持 sbspaces，请数据库服务器管理员使用 onspaces 实用程序创建一个 sbspace，并将 ONCONFIG 参数 SBSPACENAME 设置为该 sbspace名称。

* If the access_method supports only extspaces, the access_method software can create a default external storage space, such as a disk file.

* 如果 access_method 只支持 extspaces，则 access_method 软件可以创建缺省的外部存储空间，例如磁盘文件。

To find out whether the access_method supports an extspace (external storage) or sbspace (smart-large-object storage), query the sysams system catalog table for access_method name that you specify in the CREATE TABLE statement USING clause. Refer to the am_sptype value for that access_method.

The following values indicate the type of storage space that you can use with the access_method:若要了解 access_method 是否支持 extspaces（外部存储）或 sbspace（智能大对象存储），请查询 sysams 系统目录表以获取 USING 子句在 CREATE TABLE 语句中指定的access_method 名称。有关该 access_method ，请参考 am_sptype 值。以下值指示可以与 access_method 一起使用的存储空间类型：* 'X' indicates that the access_method supports only extspaces* “X”表示 access_method 只支持 extspaces。

* 'S' indicates that the access_method supports only sbspaces* “S”表示 access_method 只支持 sbspaces* 'A' indicates that the access_method supports both extspaces and sbspaces* “A”表示 access_method 支持 extspaces 和 sbspaces For information about how to determine if a storage space is of a type that an access_method supports or how to determine the storage space type that an access_method supports, refer to the access-method user guide.

有关如何确定存储空间是否为 access_method 支持的类型或如何确定 access_method 支持的存储空间类型的信息，请参阅 access_method 用户指南。

-9885 Variant user defined routine cannot be used in check constraint or fragment expression.

You cannot use a variant user-defined routine (UDR) in a check constraint or fragment expression.

不能在 Check 约束或分片表达式中使用变体用户定义例程（UDR）。

Check your statement to make sure that no variant UDR is used in a check constraint or fragment expression.

不能在 Check 约束或分片表达式中使用变体用户定义例程（UDR）。请检查语句以确保在Check 约束或分片表达式中没有使用变量 UDR 。

-9885 A check constraint or fragmentation expression cannot contain a variant user-defined routine.

A user-defined routine (UDR) in a check constraint or in a fragmentation expression cannot be variant. That is, the UDR must not return different results when passed the same arguments. Variant UDRs include routines that process queries and functions that return random results.

Check 约束或分段表达式中的用户定义例程(UDR)不能是变量。也就是说，当传递相同的参数时，UDR不能返回不同的结果。变量 UDR 包括处理查询和返回随机结果的函数的例程。

Verify that your statement does not have a variant UDR in a check constraint or in a fragmentation expression. If you want to alter a UDR that is currently in a check constraint or in a fragmentation expression from nonvariant to variant, you must drop its associated check constraints or its table or index fragments.

验证您的语句在 Check 约束或分段表达式中没有变量 UDR 。如果要更改当前处于 Check约束中的 UDR 或从非变量到变量的分片表达式，则必须删除其相关的 Check 约束或其表或索引分片。

-9886 A check constraint or fragmentation expression cannot contain a user-defined routine that generates an OUT parameter.

A check constraint or fragmentation expression cannot contain a user-defined function that generates an OUT parameter. That is, an OUT parameter cannot be passed back to a check constraint or a fragmentation expression from a user-defined function.

Check 约束或分片表达式不能包含生成 OUT 参数的用户定义函数。也就是说，OUT 参数不能从用户定义的函数中传回Check 约束或分片表达式。

Verify that your statement does not use a user-defined function that generates an OUT parameter in a check constraint or in a fragmentation expression.

请确认您的语句没有使用用户定义的函数，该函数在 Check 约束或分片表达式中生成 OUT 参数。

-9887 A check constraint or fragmentation expression cannot contain a cross-database or remote user-defined routine.

The check constraint or fragmentation expression contains a remote or cross-database user-defined routine (UDR).

Check 约束或分片表达式包含一个远程或跨数据库用户定义例程（UDR）。

Verify that a UDR in a check constraint or in a fragmentation expression is stored within the same database as the check constraint or the fragmentation expression.

验证 Check 约束或分片表达式中的 UDR 与Check 约束或分片表达式存储在同一个数据库中。

-9889 Cannot drop the user-defined routine <routine_name> because a check constraint or a fragmentation expression currently uses this routine.

To identify the check constraint that uses the routine that you are trying to drop, run this query:要标识使用尝试删除的例程的 Check 约束，请运行以下查询：SELECT constraint_id FROM syscheckudrdep x, sysprocedures y WHERE x.udr_id = y.procid AND y.procname = '<routine_name>';To identify the table or index that has a fragmentation expression that uses the routine that you are trying to drop, run this query:要标识使用尝试删除的例程的分片表达式的表或索引，请运行以下查询：SELECT tabid, idxname, owner FROM sysfragexpudrdep x, sysprocedures y WHERE x.udr_id = y.procid AND y.procname = '<routine_name>';-9904 Invalid extended type text.

Could not determine the internal SQL data type. If this error recurs,note all circumstances and contact GBase Technical Support.

无法确定内部 SQL 数据类型。如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-9905 No extended type information for domain.

Could not find the attribute information for a domain or type. If this error recurs, note all circumstances and contact GBase Technical Support.

找不到域或类型的属性信息。如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-9906 Cannot modify column data type to collection type.

You cannot use an ALTER statement to change a column type to a collection type.

不能使用 ALTER 语句将列类型更改为集合类型。

-9907 Not allowed to modify collection type column.

You cannot use an ALTER statement to change a column type from a collection type to another type.

不能使用 ALTER 语句将列类型从集合类型更改为其他类型。

-9908 Columns of a row type cannot contain fields of type TEXT, BYTE,SERIAL, SERIAL8 or BIGSERIAL.

You created a table that has a column with a named row of type TEXT,BYTE, SERIAL, SERIAL8 or BIGSERIAL. The following example should fail:您创建了一个表，其中有一个列，列的类型为 TEXT、BYTE、SERIAL、SERIAL8 或BIGSERIAL。

create row type rtype (col1 byte);create table tab1 (c1 rtype);Re-create the table with a different type of named row.

用不同类型的命名行重新创建表。

-9909 Nested row type not supported You cannot nest row types.

不能嵌套行类型。

-9910 Byte, Text, Serial or Serial8 or Bigserial data types in collection type not allowed.

The fields of a row within a collection and the elements of a collection cannot be of type TEXT, BYTE, SERIAL, or SERIAL8 or BIGSERIAL.

集合中的行字段和集合元素不能是 TEXT、BYTE、SERIAL 或 SERIAL 8 或 BIGSERIAL类型的字段。

-9911 Defaults on collection type column not allowed.

Default values are not supported in the definition a column of a collection type. Remove the default value clause.

集合类型的列的定义不支持缺省值。删除缺省值子句。

-9912 Constraints on collection type column not allowed.

Constraint expressions are not supported in the definition of a column of a collection type. Remove the constraint clause.

集合类型的列的定义不支持约束表达式。删除约束子句。

-9919 Cast already exists in database.

Casts must be unique with regard to their source and destination types,regardless of cast class. Use the DROP CAST statement to remove an existing cast.

无论类型是什么，强制转换对于源类型和目标类型都必须是唯一的。使用 DROP CAST语句删除现有的强制转换。

-9920 Cannot create a cast between identical types or between built-in types.

No cast is needed between identical types. Casts between built-in types are handled by internal system casts and cannot be overloaded.

在相同类型之间不需要强制转换。内置类型之间的转换由内部系统强制转换处理，不能重载。

-9922 Cast does not exist in database.

The requested cast does not exist. Use the CREATE CAST statement to define the cast.

所请求的强制转换不存在。使用CREATE CAST语句定义强制转换。

-9923 Cannot create cast between incompatible types.

An attempt was made to define a no-function cast between types with differing representations. Redefine the cast to use a function or redefine the types so that they share the same representation.

尝试在具有不同表示形式的类型之间定义非函数转换。重新定义转换以使用函数或重新定义类型，以便它们共享相同的表示形式。

-9926 The statement failed because row-type or collection columns were referenced in ORDER BY, DISTINCT, UNIQUE, INDEX, UNION, INTERSECT,or MINUS specifications, or in primary key, foreign key, or unique constraints.

Do not create or alter a table which makes columns of collection or row types into primary key, foreign key, or unique constraints. Do not create an index or UNION, INTERSECT, or MINUS that involves collection or row type columns. However, you can create a union that involves collection or row type columns if you use the UNION ALL operator instead of the UNION operator.

不要创建或更改使集合或行类型的列成为主键、外键或唯一约束的表。不要创建涉及集合或行类型列的索引或 UNION、INTERSECT 或 MINUS 。但是，如果使用 UNION All 运算符而不是 UNION 运算符，则可以创建涉及集合或行类型列的联合。

-9928 Must supply a cast function for cast between incompatible types.

An attempt was made to define a no-function cast between types with differing representations.

尝试定义具有不同表示形式的类型之间的无函数转换。

Redefine the cast to use a function, or redefine the types so that they share the same representation.

重新定义转换以使用函数，或重新定义类型，以便它们共享相同的表示形式。

-9930 Byte, Text, Serial or Serial8 or Bigserial datatypes in collection types not allowed.

You cannot use TEXT, BYTE, SERIAL, or SERIAL8 or BIGSERIAL data types in the fields of a row within a collection or the elements of a collection.

不能在集合或集合元素中的行字段中使用 TEXT、BYTE、SERIAL 或 SERIAL 8 或BIGSERIAL 数据类型。

-9931 Byte and Text datatypes in row and collection types not allowed.

You requested the construction of an object that contains a BYTE or TEXT data type. This is only supported for column types of a table or CREATE ROW TYPE statement. All other references to a named row type,unnamed row type, or collection type cannot contain BYTE or TEXT data types.

您请求构造包含 BYTE 或 TEXT 数据类型的对象。这仅支持表的列类型或 CREATE ROW TYPE 语句。对命名行类型、未命名行类型或集合类型的所有其他引用都不能包含 BYTE或 TEXT 数据类型。

-9932 External Directives feature is currently disabled.

You issued a statement that is valid only when the feature External Directives is enabled. Contact your DBA if you need to enable it.

您发出的语句只有在启用了功能外部指令时才有效。如果需要启用，请与 DBA 联系。

-9933 Invalid Directive specification for external directives.

The optimizer directives you specified are invalid.

您指定的优化器指令无效。

-9934 Only DBA is authorized to do this operation.

Only users with DBA privileges can perform this operation.

只有具有 DBA 权限的用户才能执行此操作。

-9935 External Directives already exist for the query.

There are external directives already saved for the specified query.

已经为指定的查询保存了外部指令。

Drop the existing external directives first, then the new external directives for the query can be saved in the database.

首先删除现有的外部指令，然后查询的新外部指令可以保存在数据库中。

-9944 Cannot seek in non-scrollable collection.

You have opened a collection with the flag MI_COLL_NOSCROLL and later attempted to seek within the collection. Open the collection without this flag or do not attempt to seek within the collection.

您已经使用标志 MI_COLL_NOSCROLL 打开了一个集合，然后尝试在集合中查找。在没有此标志的情况下打开集合，或不尝试在集合中查找。

-9945 Cannot modify a read only collection You have opened a collection with the flag MI_COLL_READONLY and then attempted to modify the collection. Do not open the collection with this flag or do not modify the collection.

您已经使用标志 MI_COLL_READONLY 打开了一个集合，然后尝试修改集合。不要使用此标志打开集合，也不要修改集合。

-9946 Cannot open subquery collection twice.

Subquery collections opened with the flags MI_COLL_READONLY and MI_COLL_NOSCROLL cannot be opened again.

不能再次打开带有标志 MI_COLL_READONLY 和 MI_COLL_NOSCROLL 标志的子查询集合。

-9950 Field referencing is not possible for non-row type expressions.

Only expressions of the form column.field are only meaningful for objects of type row.

只有表单列.字段的表达式才对行类型的对象有意义。

Remove the .field part of your expression.

删除表达式的 .field 部分。

-9953 An aggregate function is not allowed in this context.

You cannot use an aggregate function expression as an argument to a function or procedure.

不能将聚合函数表达式用作函数或存储过程的参数。

An aggregate function is valid only in these contexts:in the projection clause of the SELECT statement,in the projection clause or in the WHERE clause of a subquery.

聚合函数仅在以下上下文中有效：在 SELECT 语句的投影子句中、在投影子句中或在子查询的 WHERE 子句中。

An aggregate is not valid, however, in the WHERE clause of a subquery within a SELECT, DELETE, or UPDATE statement unless each of the following conditions is true:The aggregate is on a correlated column originating from a parent query.

The WHERE clause appears in a subquery within a HAVING clause.

但是，在 SELECT 、DELETE 或 UPDATE 语句中子查询的 WHERE 子句中，聚合无效，除非下列每一项条件都是正确的：聚合位于源自父查询的相关列上。

WHERE 子句出现在 HAVING 子句中的子查询中。

You can also include OLAP window aggregate functions in these clauses of the SELECT statement:The Select list of the Projection clause The ORDER BY clause of the SELECT statement Subquery specifications in the Projection clause还可以在SELECT语句的这些子句中包含OLAP窗口聚合函数：Projection 子句的 Select 列表SELECT 语句的 ORDER BY 子句投影子句中的子查询规范To be valid, the OLAP window aggregate function expression must immediately precede the OVER clause.

要想有效，OLAP 窗口聚合函数表达式必须紧跟在 OVER 子句之前。

To avoid this error, do not call any aggregate function outside the SELECT statement and subquery contexts that are listed above as allowing aggregate expressions.

为了避免此错误，请不要调用 SELECT 语句和子查询上下文之外的任何聚合函数，这些上下文允许聚合表达式。

-9960 Combination of table/index fragmentation not allowed.

If a table is fragmented by round-robin and its subtable specifies its own fragmentation scheme, you cannot create an index on the supertable without a fragmentation clause. Either create an index with an explicit fragmentation clause or let the subtable inherit its fragmentation scheme from the supertable.

如果一个表被循环分片，并且它的子表指定了它自己的分片方案，那么如果没有分片子句，就不能在超级表上创建索引。要么创建一个带有显式分片子句的索引，要么让子表从超级表继承它的分片方案。

-9965 The maximum number of allowable sbspaces maximum_number has been exceeded.

The maximum number of 64 sbspaces per table has been exceeded, so your operation failed. For more information on the number of sbspaces associated with the table, run the following queries:每个表的最大 sbspaces 数已超过 64 个，因此操作失败。有关与表关联的 sbspace 数量的更多信息，请运行以下查询：SELECT tabid FROM gbasedbt.systables WHERE tabname = `<user_table_name>';SELECT count(*) FROM gbasedbt.syscolattribs WHERE tabid = <tabid_from_previous_query>;-9967 Cannot find data type data_type_name.

The specified data type does not exist in the database. Check sysxtdtypes to make sure that the data type exists before you use it.

数据库中不存在指定的数据类型。检查 sysxtdtype ，以确保数据类型在使用之前存在。

-9969 Corrupted collection type information.

The type information for a collection is not consistent.

集合的类型信息不一致。

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-9970 Cannot determine host variable type during bind.

An ambiguous bind message was received. The database server could not infer the variable type from the context of the query. The host variable type must be explicitly defined.

接收到一条模糊绑定消息。数据库服务器无法从查询的上下文中推断变量类型。必须显式定义主机变量类型。

-9971 Cannot determine the return types of a query or return types are inconsistent.

The database server cannot determine the data type for one or more of the values that the query is to return.

数据库服务器无法确定查询要返回的一个或多个值的数据类型。

Check the specification of the data type for each return value,correct any errors in the specification, and retry the query.

请检查每个返回值的数据类型规范，更正规范中的任何错误，然后重试查询。

-9973 Row buffer for collection of fixed size elements not of correct size.

You attempted to insert a new or update an existing collection element with a value that is not the same size as was declared in the collection definition. This error occurs only when a collection contains fixed-length elements.

您试图插入一个新的或更新一个现有的集合元素，其值与集合定义中声明的值不同。只有当集合包含固定长度的元素时，才会发生此错误。

Check to make certain that the value you are inserting matches the collection declaration.

请检查以确保插入的值与集合声明匹配。

-9974 Cannot delete element from a ROW type.

You have attempted to delete a row from a host variable of type ROW.

Because a ROW host variable has only the single row as its contents,deletion is not allowed. If you want to construct a row with NULL values, use an UPDATE statement and set each field to a NULL value.

Otherwise, remove the request to execute the SQL DELETE for the row host variable in your embedded language program.

您已尝试从类型为 ROW 的宿主变量中删除一行。由于行宿主变量的内容仅为单行，因此不允许删除。如果要构造带有空值的行，请使用 UPDATE 语句并将每个字段设置为空值。

否则，删除对嵌入式语言程序中行主机变量执行 SQL DELETE 的请求。

-9975 Type of a table must be unique within a table hierarchy.

You cannot have siblings of the same type under the same parent. For example, assume that you create the following row types:您不能在同一父级下拥有相同类型的兄弟姐妹。例如，假设您创建了以下行类型：create row type r1 (a int);create row type r2 under r1;Now you attempt to create a supertable and two subtables. The third statement in the following set generates an error:现在，您尝试创建一个超级表和两个子表。以下集合中的第三条语句会生成一个错误：create table supertab of type r1;create table subtab1 of type r2 under r1;create table subtab2 of type r2 under r1;The third CREATE TABLE statement generates an error because subtab1 and subtab2 would be siblings under supertab. GBase 8s does not support this table hierarchy in this release. The current version of the database server restricts the table hierarchy to match the type hierarchy, and no type can appear more than once within a single hierarchy of tables.

第三个 CREATE TABLE 语句生成一个错误，因为 subtable 1 和 subtable 2 将是supertab 下的兄弟。GBase 8s 在此版本中不支持此表层次结构。数据库服务器的当前版本将表层次结构限制为与类型层次结构相匹配，并且在单个表层次结构中不能出现超过一次的类型。

-9976 Manipulation of NULL collection disallowed.

You attempted an action on a NULL collection. Examine your embedded language program to determine why you are attempting to operate on a NULL collection.

您尝试对空集合执行操作。检查嵌入式语言程序，以确定为什么要对空集合进行操作。

-9977 Internal Error: hash value out of sync.

This message indicates an error internal to the support of the GBase 8s database server for collection data types. If this error recurs,note all the circumstances and contact GBase Technical Support.

此消息表示 GBase 8s 数据库服务器支持收集数据类型的内部错误。如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-9978 Insertion of NULLs into a collection disallowed.

The statement attempted to insert one or more NULL values into a collection.

The elements of a collection must always be non-null. The fields of a row within a collection can be NULL, but the elements of the collection cannot be NULL. This error can occur, however, if a collection subquery specifies an ITEM select and one of the rows contains a NULL value.

该语句试图向集合中插入一个或多个 NULL 值。集合的元素必须始终为非空。集合中行的字段可以为 NULL ，但集合中的元素不能为 NULL 。但是，如果集合子查询指定项SELECT 且其中一行包含 NULL 值，则可能发生此错误。

The following example is valid for a collection defined with elements of type row. However, insert into table(:coll_hv2) values (NULL) is not valid for any collection.

下面的示例对使用 ROW 类型元素定义的集合有效。但是，insert into table(:coll_hv2) values (NULL) 对任何集合都无效。

INSERT INTO TABLE(:coll_hv) VALUES (row(NULL, NULL));Do not attempt to insert NULL values as elements of a collection.

不要尝试将 NULL 值作为集合的元素插入。

-9979 Updating of a collection element to NULL is disallowed.

The elements of a collection cannot be NULL. Do not attempt to update collection elements to NULL values. (See the corrective action for error message -9978.)集合的元素不能为 NULL。不要尝试将集合元素更新为 NULL 值。(请参见错误消息的纠正措施 -9978。)-9980 LIST expected when inserting AT position.

You can use a positional insert statement only with collection of type LIST. Remove the AT clause from your insert statement.

只能在类型列表的集合中使用位置插入语句。从 INSERT 语句中删除 AT 子句。

-9981 Delete disallowed on collection with other cursor references.

You attempted to delete a collection that is being referenced by more than one cursor. Review your program, determine the relevant cursor to keep, and remove the other cursor that is acting on the collection.

您试图删除多个游标正在引用的集合。检查您的程序，确定要保留的相关游标，并删除对集合进行操作的另一个游标。

-9982 Update disallowed on collection with other cursor references.

You attempted to update a collection that is being referenced by more than one cursor. Review your program, determine the relevant cursor to keep, and remove the other cursor that is acting on the collection.

您试图更新由多个游标引用的集合。检查您的程序，确定要保留的相关游标，并删除对集合进行操作的另一个游标。

-9983 Deleting a nonexisting element.

You positioned your cursor to an element of a collection that no longer exists and then requested that the element be updated or deleted. This problem occurs if you use a FETCH statement to position your cursor past the last record and then attempt an update or delete. An error results because you are not pointing to a valid record. Make sure your embedded language program is checking the SQLCODE value returned after a FETCH to determine that there are no more rows.

您将光标定位到集合中不再存在的元素，然后请求更新或删除该元素。如果使用 FETCH语句将光标定位到最后一个记录，然后尝试更新或删除，则会发生此问题。由于没有指向有效的记录，因此出现错误。确保您的嵌入式语言程序正在检查获取后返回的 SQLCODE值，以确定没有更多的行。

-9984 Cannot free a collection with other cursor references.

You attempted to free a collection reference while a cursor is still opened on the collection. Review your embedded language program to determine why you are prematurely freeing the collection reference before you close the cursor.

您试图在集合上打开游标时释放集合引用。检查您的嵌入式语言程序，以确定在关闭光标之前，您为什么过早地释放集合引用。

-9985 Internal Error: invalid change log.

This message indicates an error internal to the support of GBase 8s database server for collection data types. If this error recurs,note all the circumstances and contact GBase Technical Support.

此消息表示 GBase 8s 数据库服务器支持收集数据类型的内部错误。如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-9986 Internal Error: corrupted collection.

This message indicates an error internal to the support of GBase 8s database server for collection data types. If this error recurs,note all the circumstances and contact GBase Technical Support.

此消息表示 GBase 8s 数据库服务器支持收集数据类型的内部错误。如果再次出现此错误，请注意所有情况，并与GBase技术支持部门联系。

-9987 Cursor already registered.

You are attempting to open a cursor that is already open. Review your embedded language program to determine why you are re-opening the cursor before you close it.

您正在尝试打开已经打开的游标。检查您的嵌入式语言程序，以确定为什么要重新打开光标，然后再关闭它。

-9988 Cannot flatten a collection with other cursor references.

You attempted to store a collection host variable into a table column,or row field, but cursors are still open on the collection. You must close the other cursors before you attempt this operation.

尝试将集合宿主变量存储到表列或行字段中，但集合上仍打开游标。在尝试此操作之前，必须关闭其他游标。

-9989 Incorrect number of fields in the ROW type.

You attempted to store a row with incorrect field types into a collection. Verify that the row fields match those of the collection.

尝试将具有不正确字段类型的行存储到集合中。验证行字段与集合的字段匹配。

-9990 Cannot drop named row type <row_type_name>: still in use.

The row type that you are attempting to drop is being referenced by another type or table, or the row type is used in an SPL routine.

要删除的行类型由另一个类型或表引用，或者在 SPL 例程中使用行类型。

For example:例如：CREATE ROW TYPE MyType ...;CREATE FUNCTION f(param1 MyType) RETURNS INTEGER;...

END FUNCTION;DROP ROW TYPE MyType; -- Gets error -9990 Before you drop the row type, first drop any type or table that refers to the row type and drop any SPL routine that uses it.

在删除行类型之前，首先删除引用行类型的任何类型或表，并删除使用行类型的任何 SPL例程。

-9991 Named row type row_type_name already exists in database.

You are trying to create a named row type whose name is already used.

Use another name or drop the row type to reuse its name.

您正在尝试创建已命名的行类型，其名称已经被使用。使用另一个名称或删除行类型来重用其名称。

-9992 Named row type row_type_name not found.

The named row type specified does not exist in the database. Verify its existence by selecting from sysxtdtypes.

指定的命名行类型在数据库中不存在。通过从 sysxtdtype 中选择来验证它的存在。

-9993 Not owner of named row type.

You cannot drop the named row type unless you are the owner or have the DBA privilege. Verify the owner of the named row type by selecting from sysxtdtypes.

除非您是所有者或拥有DBA权限，否则不能删除命名行类型。通过从 sysxtdtypes 中选择来验证命名行类型的所有者。

-9994 Cannot use ONLY(TABLE(str)) over collections.

The ONLY syntax is not legal over TABLE expressions over collections.

Use ONLY on supertables; that is, parents in an inheritance chain.

对集合而言，TABLE 表达式的 ONLY 语法不是合法的。在超级表上使用 ONLY ；也就是说，继承链中的父母。

-9995 Table table_name is not typed.

Cannot alter a table to drop its type if the table is not typed. Make sure you are referring to the correct table.

如果表未键入，则无法更改表以删除其类型。确保您所指的是正确的表。

-9996 Distinct type () already exists in database.

Distinct types must be unique within the schema (ANSI mode) or database.

在架构（ANSI 模式）或数据库中，不同的类型必须是唯一的。

Redefine the type with a new name or remove the existing name before attempting to create your version.

使用新名称重新定义类型，或在尝试创建版本之前删除现有名称。

-9997 No usage privilege on data type ().

You do not hold the privilege to use this data type, which is a DISTINCT data type that is based on a built-in data type. The creator of this user-defined data type or a DBA must explicitly grant you the Usage privilege on this data type.

您不拥有使用此数据类型的权限，该数据类型是基于内置数据类型的一种不同的数据类型。此用户定义的数据类型或 DBA 的创建者必须显式授予此数据类型的使用权限。

You should ask a DBA or the owner of the cast to grant you the Usage privilege on the cast.

您应该要求 DBA 或强制转换的所有者授予您在强制转换上的使用权限。

-9998 No privilege to drop a cast of this DISTINCT data type.

You do not have the privilege to drop a cast of this DISTINCT type. By default, after a DISTINCT type is defined, only the owner of the DISTINCT type or a DBA can drop a cast for it. The owner of the DISTINCT type, however, can grant to other users, to PUBLIC, or to roles the Usage privilege on the DISTINCT type.

您没有权限删除此类型的强制转换。缺省情况下，在定义了不同类型之后，只有不同类型或 DBA 的所有者才能为其进行强制转换。但是，不同类型的所有者可以向其他用户、公共用户或角色授予不同类型上的使用权限。

You should ask the DBA or the owner of the cast to drop the cast, or else to grant you the Usage privilege on the cast so that you can drop it.

您应该要求DBA或强制转换的所有者放弃强制转换，或者授予您在强制转换上的使用权限，以便您可以放弃它。

-9999 Routine collcompare() is not supported.

This routine always returns -1 and an error. The semantics of the comparison are not defined.

这个例程总是返回 -1 和一个错误。没有定义比较的语义。

-10000 Argument must be a variable to be an OUT or INOUT parameter.

The corresponding arguments to UDRs with OUT or INOUT parameters must be specified as variables when the routine is called from a client such as DRDA. Constants cannot be used as an argument for an OUT or INOUT parameter in such cases.

当从客户端（如 DRDA）调用例程时，必须将带有 OUT 或 INOUT 参数的 UDR 的相应参数指定为变量。在这种情况下，常量不能用作 OUT 或 INOUT 参数的参数。

-11000 Success.

This GBase 8s CLI error code is the same as SQLSTATE value 00000. The following functions can return this error code: all GBase 8s CLI functions.

此 GBase 8s CLI 错误代码与 SQLSTATE 值 00000 相同。以下函数可以返回此错误代码：所有 GBase 8s CLI 函数。

The function completed successfully.

该函数成功完成。

-11001 General warning.

This GBase 8s CLI error code is the same as SQLSTATE value 01000. The following functions can return this error code: all GBase 8s CLI functions except SQLAllocEnv() and SQLError().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 01000 相同。以下函数可以返回此错误代码：all GBase 8s CLI functions except SQLAllocEnv() and SQLError().

The function returned SQL_SUCCESS_WITH_INFO, which means that the function completed successfully, and that a nonfatal error occurred. For more information, call SQLError().

函数返回 SQL_SUCCESS_WITH_INFO，这意味着函数成功完成，并且发生了非致命错误。有关更多信息，请调用 SQLError()。

-11001 General warning.

This CLI warning can be returned with any CLI function except SQLAllocEnv and SQLError when a nonspecific warning occurs. Additional text is appended to describe the specified warning in more detail. For detailed information associated with the appended text, check the GBase 8s CLI Programmer's Manual.

在发生非特定警告时，除了 SQLAllocEnv 和 SQLError 之外，任何 CLI 函数都可以返回此 CLI 警告。附加其他文本以更详细地描述指定的警告。有关附加文本的详细信息，请参阅 GBase 8s CLI 程序员手册。

-11002 Disconnect error.

This GBase 8s CLI error code is the same as SQLSTATE value 01002. The following function can return this error code: SQLDisconnect().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 01002 相同。以下函数可以返回此错误代码：SQLDisconnect()。

The function returned SQL_SUCCESS_WITH_INFO, which means that the function completed successfully, and that a nonfatal error occurred. For more information, call SQLError().

函数返回 SQL_SUCCESS_WITH_INFO，这意味着函数成功完成，并且发生了非致命错误。有关更多信息，请调用 SQLError()。

-11003 Data truncated.

This CLI message is issued when the data that a CLI function returns exceeds the defined buffer size. Increase the size of the allocated buffer.

当 CLI 函数返回的数据超过定义的缓冲区大小时，将发出此 CLI 消息。增加分配缓冲区的大小。

This GBase 8s CLI error code is the same as SQLSTATE value 01004. The following functions can return this error code: SQLBrowseConnect(),SQLColAttributes(), SQLDataSources(), SQLDescribeCol(), SQLDriverConnect(),SQLDrivers(), SQLExecDirect(), SQLExecute(), SQLExtendedFetch(), SQLFetch(),SQLGetCursorName(), SQLGetData(), SQLGetInfo(), SQLNativeSql(), and SQLPutData().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 01004 相同。以下函数可以返回此错误代码：SQLBrowseConnect()、SQLColAttributes()、SQLDataSources()、SQLDescribeCol()、SQLDriverConnect()、SQLDrivers()、SQLExecDirect()、SQLExecute()、SQLExtendedFetch()、SQLFetch()、SQLGetCursorName()、SQLGetData()、 SQLGetInfo()、SQLNativeSql() 和 SQLPutData()。

For SQLExecDirect(), SQLExecute(), or SQLPutData(), one of the following problems occurred for the SQL statement, the prepared statement, or the data sent: (1) The statement or data contained a binary or character parameter or literal that exceeded the maximum length of the associated column, or(2) The function truncated the fractional part of a numeric parameter or literal in the statement or data, or (3) The function truncated part of a date or time parameter or literal in the statement or data. Change the data or the parameters and literals in the statement so that they do not exceed the maximum length of the associated column, and set the data types for the parameters and literals so that they can accommodate the data.

对于 SQLExecDirect()、SQLExecute() 或 SQLPutData(), 下列问题之一会出现在 SQL语句、预准备语句或发送的数据出现：(1)语句或数据包含超过关联列最大长度的二进制或字符参数或文字，或(2)函数截断语句或数据中数值参数或文字的小数部分，或(3)语句或数据中日期或时间参数或文字的函数截断部分。更改语句中的数据或参数和文字，使其不超过关联列的最大长度，并设置参数和文字的数据类型，以便它们能够容纳数据。

For SQLExtendedFetch() or SQLFetch(), the function returned SQL_SUCCESS_WITH_INFO, which means that the function completed successfully,and that a nonfatal error occurred. To handle the nonfatal error, the function truncated the data that was returned for one or more columns. If the value was a string, the function right-truncated it. If the value was numeric, the function truncated the fractional part of the number. Set the data types for the return data so that they can accommodate the data. For more information,call SQLError().

对于 SQLExtendedFetch() 或 SQLFetch()，函数返回 SQL_SUCCESS_WITH_INFO，这意味着函数成功完成，并且发生了非致命错误。为了处理非致命错误，函数截断了一个或多个列返回的数据。如果值是字符串，则函数右截断它。如果值是数字，则函数截断数字的小数部分。设置返回数据的数据类型，以便它们能够容纳数据。有关更多信息，请调用SQLError()。

For SQLGetData(), the function returned SQL_SUCCESS_WITH_INFO, which means that the function completed successfully, and that a nonfatal error occurred.

The nonfatal error occurred because the function could not retrieve all the data for the specified column in one call. The pcbValue argument contains the length of the data that was left in the column before the current call to SQLGetData(). Call SQLGetData() repeatedly until all data is retrieved.

对于 SQLGetData()，函数返回 SQL_SUCCESS_WITH_INFO，这意味着函数成功完成，并且发生了非致命错误。发生非致命错误是因为函数无法在一次调用中检索指定列的所有数据。pcbValue 参数包含当前调用 SQLGetData() 之前保留在列中的数据的长度。反复调用 SQLGetData()，直到检索到所有数据。

For all other functions that can return this error code, the function returned SQL_SUCCESS_WITH_INFO, which means that the function completed successfully,and that a nonfatal error occurred. The nonfatal error occurred because the return buffer was not large enough to return all the requested information.

The function truncated the return data and set the total number of bytes returned to the length of the untruncated return data. Reallocate the return buffer so that it can accommodate the return data. For more information, call SQLError().

对于可以返回此错误代码的所有其他函数，该函数返回 SQL_SUCCESS_WITH_INFO，这意味着该函数已成功完成，并且发生了非致命错误。发生非致命错误是因为返回缓冲区不够大，无法返回所有请求的信息。函数截断返回数据，并将返回的字节总数设置为未截断返回数据的长度。重新分配返回缓冲区，以便它能够容纳返回数据。有关更多信息，请调用SQLError()。

-11004 Privilege not revoked.

This GBase 8s CLI error code is the same as SQLSTATE value 01006. The following functions can return this error code: SQLExecDirect() and SQLExecute().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 01006 相同。以下函数可以返回此错误代码：SQLExecDirect() 和 SQLExecute()。

The function returned SQL_SUCCESS_WITH_INFO, which means that the function completed successfully, and that a nonfatal error occurred. The nonfatal error occurred because the SQL statement or prepared statement contained a REVOKE statement, and the user does not have the access privilege to make this change. For more information, call SQLError().

函数返回 SQL_SUCCESS_WITH_INFO，这意味着函数成功完成，并且发生了非致命错误。发生非致命错误的原因是SQL语句或准备好的语句包含了 REVOKE 语句，而且用户没有进行此更改的访问权限。有关更多信息，请调用 SQLError()。

-11005 Invalid connection string attribute.

Specified connection string attribute is unsupported for SQLBrowseConnect and SQLDriverConnect. Check the list of valid attributes.

SQLBrowseConnect 和 SQLDRiverConnect 不支持指定的连接字符串属性。检查有效属性列表。

This GBase 8s CLI error code is the same as SQLSTATE value 01S00. The following functions can return this error code: SQLBrowseConnect() and SQLDriverConnect().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 01S00 相同。以下函数可以返回此错误代码：SQLBrowseConnect()和 SQLDRiverConnect()。

For SQLBrowseConnect(), the function returned SQL_NEED_DATA, which means that either the connection string contains an invalid attribute keyword, or the connection string contains an attribute keyword that does not apply to the current connection level. Set each attribute keyword in the connection string to a valid value that applies to the current connection level.

对于SQLBrowseConnect()，函数返回SQL_REUSE_DATA，这意味着连接字符串包含无效的属性关键字，或者连接字符串包含不适用于当前连接级别的属性关键字。将连接字符串中的每个属性关键字设置为适用于当前连接级别的有效值。

For SQLDriverConnect(), the function returned SQL_SUCCESS_WITH_INFO, which means that the function completed successfully, and that a nonfatal error occurred. The nonfatal error occurred because the connection string contains an invalid attribute keyword, but GBase 8s CLI connected to the data source anyway. For more information, call SQLError().

对于 SQLDRiverConnect()，函数返回 SQL_SUCCESS_WITH_INFO，这意味着函数成功完成，并且发生了非致命错误。发生非致命错误是因为连接字符串包含无效的属性关键字，但是 GBase 8s CLI 无论如何都连接到数据源。有关更多信息，请调用 SQLError()。

-11006 Error in row.

An error occurred while fetching one or more rows with SQLExtendedFetch. Check the rgfRowStatus array.

使用 SQLExtendedFetch 获取一行或多行时发生错误。检查 rgfRowStatus 数组。

This GBase 8s CLI error code is the same as SQLSTATE value 01S01. The following function can return this error code: SQLExtendedFetch().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 01S01 相同。以下函数可以返回此错误代码：SQLExtendedFetch()。

The function returned SQL_SUCCESS_WITH_INFO, which means that the function completed successfully, and that a nonfatal error occurred. The nonfatal error occurred while the function was fetching one or more rows. For more information, call SQLError().

函数返回 SQL_SUCCESS_WITH_INFO，这意味着函数成功完成，并且发生了非致命错误。非致命错误发生在函数获取一行或多行时。有关更多信息，请调用 SQLError()。

-11007 Option value changed.

The driver did not support the specified value of the VParam argument with the SQLSetConnectOption or SQLSetStatementOption. The driver substitutes a similar value and returns SQL_SUCCESS_WITH_INFO. To determine the new value of VParam, use SQLGetConnectionOption or SQLGetStatement.

驱动程序不支持 SQLSetConnectOption 或 SQLSetStatementOption VParam 参数的指定值。驱动程序替换一个类似的值，并返回 SQL_SUCCESS_WITH_INFO。若要确定 VParam 的新值，请使用 SQLGetConnectionOption 或 SQLGetStatement。

This GBase 8s CLI error code is the same as SQLSTATE value 01S02. The following functions can return this error code: SQLSetConnectOption() and SQLSetStmtOption().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 01S02 相同。以下函数可以返回此错误代码：SQLSetConnectOption() 和 SQLSetStmtOption()。

The function returned SQL_SUCCESS_WITH_INFO, which means that the function completed successfully, and that a nonfatal error occurred. The nonfatal error occurred because GBase 8s CLI does not support the vParam value for the option. The function substituted a similar value. For more information,call SQLError().

函数返回 SQL_SUCCESS_WITH_INFO，这意味着函数成功完成，并且发生了非致命错误。发生非致命错误是因为 GBase 8s CLI 不支持该选项的 vParam 值。该函数替换了一个类似的值。有关更多信息，请调用 SQLError()。

-11008 No rows updated or deleted.

This GBase 8s CLI error code is the same as SQLSTATE value 01S03. The following functions can return this error code: SQLExecDirect() and SQLExecute().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 01S03 相同。以下函数可以返回此错误代码：SQLExecDirect() 和 SQLExecute()。

The function returned SQL_SUCCESS_WITH_INFO, which means that the function completed successfully, and that a nonfatal error occurred. The nonfatal error occurred because the SQL statement or prepared statement contained a positioned UPDATE or DELETE statement, but the function did not update or delete any rows. For more information, call SQLError().

函数返回 SQL_SUCCESS_WITH_INFO，这意味着函数成功完成，并且发生了非致命错误。发生非致命错误是因为 SQL 语句或准备好的语句包含定位的 UPDATE 或 DELETE 语句，但函数没有更新或删除任何行。有关更多信息，请调用 SQLError()。

-11009 More than one row updated or deleted.

This GBase 8s CLI error code is the same as SQLSTATE value 01S04. The following functions can return this error code: SQLExecDirect() and SQLExecute().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 01S04 相同。以下函数可以返回此错误代码：SQLExecDirect()和SQLExecute()。

The function returned SQL_SUCCESS_WITH_INFO, which means that the function completed successfully, and that a nonfatal error occurred. The nonfatal error occurred because the SQL statement or prepared statement contained a positioned UPDATE or DELETE statement, and the function updated or deleted more than one row. For more information, call SQLError().

函数返回 SQL_SUCCESS__WITH_INFO，这意味着函数成功完成，并且发生了非致命错误。

发生非致命错误的原因是 SQL 语句或准备好的语句包含定位的 UPDATE 或 DELETE 语句，并且函数更新或删除了多行。有关更多信息，请调用 SQLError()。

-11010 Cancel treated as FreeStmt/Close.

This GBase 8s CLI error code is the same as SQLSTATE value 01S05. The following function can return this error code: SQLCancel().

这个 GBase 8s CLI 错误代码与 SQLSTATE 值 01S05 相同。下面的函数可以返回这个错误代码：SQLCancel()。

This message is issued whenever SQLCancel is used with an open statement handle. This warning is not returned when using the driver manager. Instead of using SQLCancel, close the statement handle with the SQLFree statement.

每当使用 SQL 语句与打开语句句柄时，就会发出此消息。使用驱动程序管理器时不会返回此警告。不使用 SQLCancel，而是使用 SQLFree 语句关闭语句句柄。

-11011 Attempt to fetch before the result returned the first rowset.

This GBase 8s ODBC error code is the same as SQLSTATE value 01S06. The following functions can return this error code: SQLExtendedFetch and SQLFetchScroll.

这个 GBase 8s ODBC 错误代码与 SQLSTATE 值 01S06 相同。下面的函数可以返回这个错误代码：SQLExtendedFetch 和 SQLFetchScroll 。

For SQLExtendedFetch(), the requested rowset overlapped the start of the result set when the current position was beyond the first row, and either FetchOrientation was SQL_PRIOR or FetchOrientation was SQL_RELATIVE with a negative FetchOffset whose absolute value was less than or equal to the current SQL_ROWSET_SIZE. (Function returns SQL_SUCCESS_WITH_INFO.)对于 SQLExtendedFetch()，当前位置超过第一行时，请求的行集与结果集的开始重叠，FetchOrientation 为 SQL_PRIOR 或 FetchOrientation 为带有负值FetchOffset 的SQL_RELATIVE ，其绝对值小于或等于当前 SQL_ROWSET_SIZE。（函数返回QL_SUCCESS_WITH_INFO。)For SQLFetchScroll, the requested rowset overlapped the start of the result set when FetchOrientation was SQL_FETCH_PRIOR, the current position was beyond the first row, and the number of the current row is less than or equal to the rowset size.

对于 SQLFetchScroll，请求的行集在 FetchOrientation 为 SQL_FETCH_PRIOR 时与结果集的开始重叠，当前位置超出第一行，并且当前行的数目小于或等于行集大小。

The requested rowset overlapped the start of the result set when FetchOrientation was SQL_FETCH_PRIOR, the current position was beyond the end of the result set, and the rowset size was greater than the result set size.

当 FetchOrientation 为 SQL_FETCH_PRIOR 时，所请求的行集与结果集的开始重叠，当前位置超出结果集的结尾，行集大小大于结果集大小。

The requested rowset overlapped the start of the result set when FetchOrientation was SQL_FETCH_RELATIVE, FetchOffset was negative, and the absolute value of FetchOffset was less than or equal to the rowset size.

当 FetchOrientation 为 SQL_FETCH_RELATIVE 时，请求的行集与结果集的开始重叠，FetchOffset 为负值，并且 FetchOffset 的绝对值小于或等于行集大小。

The requested rowset overlapped the start of the result set when FetchOrientation was SQL_FETCH_ABSOLUTE, FetchOffset was negative, and the absolute value of FetchOffset was greater than the result set size but less than or equal to the rowset size. (Function returns SQL_SUCCESS_WITH_INFO.)当 FetchOrientation 为 SQL_FETCH_ABSOLUTE 时，请求的行集与结果集的开始重叠，FetchOffset 为负值，且 FetchOffset 的绝对值大于结果集大小，但小于或等于行集大小。(函数返回 SQL_SUCCESS_WITH_INFO。)-11012 Wrong number of parameters.

This GBase 8s CLI error code is the same as SQLSTATE value 07001. The following functions can return this error code: SQLExecDirect() and SQLExecute().

此 GBase 8s CLI错误代码与 SQLSTATE 值 07001 相同。以下函数可以返回此错误代码：SQLExecDirect()和SQLExecute()。

The number of parameters that you used SQLBindParameter() to bind is less than the number of parameters in the SQL statement or prepared statement.

Bind the same number of parameters as the number of parameters in the statement.

使用 SQLBindParameters() 绑定的参数少于 SQL 语句或预准备语句中的参数。绑定与语句中的参数相同的参数。

-11013 Restricted data type attribute violation.

This GBase 8s CLI error code is the same as SQLSTATE value 07006. The following functions can return this error code: SQLBindParameter(),SQLExtendedFetch(), SQLFetch(), and SQLGetData().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 07006 相同。以下函数可以返回此错误代码：SQLBindParameter()、SQLExtendedFetch()、SQLFetch() 和 SQLGetData()。

A data value could not be converted to the C data type specified by the fCType argument of the SQLBindCol function. This error occurs when you try to retrieve data types that are unsupported by the CLI driver or the value in the fCType argument is not recognized. Confirm that the data type you are requesting is supported by the database server and confirm that the value you are supplying for the fCType argument is valid.

数据值无法转换为 SQLBindCol 函数的 fCType 参数指定的 C 数据类型。当您试图检索CLI 驱动程序不支持的数据类型或不识别 fCType 参数中的值时，会发生此错误。确认数据库服务器支持所请求的数据类型，并确认为 fCType 参数提供的值是有效的。

For SQLBindParameter(), it is not possible to convert the result data (the data value associated with the GBase 8s CLI C data type (fCType) argument)to the data type of the parameter (the data value associated with the GBase 8s CLI SQL data type (fSqlType) argument). Set the GBase 8s CLI C and SQL data types to values that make it possible to convert the result data to the data type of the parameter.

对于 SQLBindParameter()，不可能将结果数据（与 GBase 8s CLIC 数据类型(fCType)参数关联的数据值）转换为参数的数据类型（与 GBase 8s CLISQL 数据类型(fSqlType)参数关联的数据值）。将 GBase 8s CLIC 和 SQL数据类型设置为可以将结果数据转换为参数的数据类型的值。

For SQLExtendedFetch() or SQLFetch(), it is not possible to convert one of the result data values to the specified data type (the GBase 8s CLI C data type(fCType) argument for SQLBindCol()). For each data value that the function fetches, set the associated GBase 8s CLI C data type argument for SQLBindCol()to a value that makes it possible to convert the data value to the specified data type.

对于 SQLExtendedFetch() 或 SQLFetch()，不可能将其中一个结果数据值转换为指定的数据类型(SQLBindCol()的 GBase 8s CLIC 数据类型(fCType)参数)。对于函数获取的每个数据值，将 SQLBindCol()的相关联的 GBase 8s CLIC 数据类型参数设置为可以将数据值转换为指定数据类型的值。

For SQLGetData(), it is not possible to convert the data value to the specified data type (the GBase 8s CLI C data type (fCType) argument). Set GBase 8s CLI C data type to a value that makes it possible to convert the data value to the data type.

对于 SQLGetData()，不可能将数据值转换为指定的数据类型( GBase 8s CLIC 数据类型(fCType)参数)。将 GBase 8s CLIC 数据类型设置为可以将数据值转换为数据类型的值。

-11014 Invalid use of default parameter.

This GBase 8s CLI error code is the same as SQLSTATE value 07S01. The following functions can return this error code: SQLExecDirect(), SQLExecute(),and SQLPutData().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 07S01 相同。以下函数可以返回此错误代码：SQLExecDirect()、SQLExecute()和SQLPutData()。

You used SQL_DEFAULT_PARAM and the corresponding parameter does not have a default value. Use SQL_DEFAULT_PARAM only if the corresponding parameter has a default value.

您使用了 SQL_DEFAULT_PARAM，相应的参数没有默认值。只有在相应的参数具有默认值的情况下，才使用 SQL_DEFAULT_PARAM。

-11015 Unable to connect to data source.

This GBase 8s CLI error code is the same as SQLSTATE value 08001. The following functions can return this error code: SQLBrowseConnect(),SQLConnect(), and SQLDriverConnect().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 08001 相同。以下函数可以返回此错误代码：SQLBrowseConnect()、SQLConnect() 和 SQLDRiverConnect()。

The driver cannot establish a connection with the data source. Check that the database server name, user ID, and password are correctly specified and that the database server is available.

驱动程序无法与数据源建立连接。检查数据库服务器名称、用户 ID 和密码是否正确指定，以及数据库服务器是否可用。

-11016 Connection in use.

The specified connection with a data source is in conflict with another user's exclusive use of the database. Establish a connection when the data source is available.

与数据源的指定连接与其他用户对数据库的独占使用发生冲突。在数据源可用时建立连接。

-11017 Connection not open.

This GBase 8s CLI error code is the same as SQLSTATE value 08003. The following functions can return this error code: SQLAllocStmt(),SQLDisconnect(), SQLGetConnectOption(), SQLGetInfo(), SQLNativeSql(),SQLSetConnectOption(), and SQLTransact().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 08003 相同。以下函数可以返回此错误代码：SQLAllocStmt()、SQLDisconnect()、SQLGetConnectOption()、SQLGetInfo()、SQLNativeSql()、SQLSetConnectOption() 和 SQLTransact()。

The connection that the hdbc argument specifies is not open. Validate that the SQLConnect, SQLDriverConnect, or SQLBrowseConnect calls succeeded.

验证 SQLConnect、SQLDRiverConnect 或 SQLBrowseConnect 调用是否成功。

-11018 Data source rejected establishment of connection.

The data source rejected the establishment of the connection for implementation-defined reasons. Confirm that the password and user ID are correct.

由于实现定义的原因，数据源拒绝建立连接。确认密码和用户 ID 是正确的。

-11020 Communication link failure.

This GBase 8s CLI error code is the same as SQLSTATE value 08S01. The following functions can return this error code: SQLBrowseConnect(),SQLColumnPrivileges(), SQLColumns(), SQLConnect(), SQLDriverConnect(),SQLExecDirect(), SQLExecute(), SQLExtendedFetch(), SQLFetch(),SQLForeignKeys(), SQLFreeConnect(), SQLGetData(), SQLGetTypeInfo(),SQLParamData(), SQLPrepare(), SQLPrimaryKeys(), SQLProcedureColumns(),SQLProcedures(), SQLPutData(), SQLSetConnectOption(), SQLSetStmtOption(),SQLSpecialColumns(), SQLStatistics(), SQLTablePrivileges(), and SQLTables().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 08S01 相同。以下函数可以返回此错误代码：SQLBrowseConnect()、SQLColumnPrivileges()、SQLColumns()、SQLConnect()、SQLDriverConnect()、SQLExecDirect()、SQLExecute()、SQLExtendedFetch()、SQLFetch()、SQLForeignKeys()、SQLFreeConnect()、SQLGetData()、SQLGetTypeInfo()、SQLParamData()、SQLPrepare()、SQLPrimaryKeys()、SQLProcedureColumns()、SQLProcedures()、SQLPutData()、SQLSetConnectOption()、SQLSetStmtOption()、SQLSpecialColumns()、SQLStatistics()、SQLTablePrivileges() 和 SQLTables()。

The communication link between GBase 8s CLI and the data source failed before the function completed successfully. If this error occurs consistently,contact GBase Technical Support.

GBase 8s CLI 与数据源之间的通信链接在函数成功完成之前失败。如果此错误持续发生，请与 GBase 技术支持部门联系。

-11021 Insert value list does not match column list.

This GBase 8s CLI error code is the same as SQLSTATE value 21S01. The following functions can return this error code: SQLExecDirect() and SQLPrepare().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 21S01 相同。以下函数可以返回此错误代码：SQLExecDirect() 和 SQLPrepare()。

The SQL statement contained an INSERT statement, but the number of values to insert was not the same as the number of columns into which to insert values. Change the INSERT statement so that the number of values to insert is the same as the number of columns into which to insert values.

SQL 语句包含 INSERT 语句，但要插入的值数与要插入值的列数不相同。更改 INSERT 语句，使要插入的值数与要插入值的列数相同。

-11022 Degree of derived table does not match column list.

This GBase 8s CLI error code is the same as SQLSTATE value 21S02. The following functions can return this error code: SQLExecDirect() and SQLPrepare().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 21S02 相同。以下函数可以返回此错误代码：SQLExecDirect()和SQLPrepare()。

The SQL statement contained a CREATE VIEW statement, but the number of column names for the view was not the same as the number of columns that the SELECT statement returns. Change the CREATE VIEW statement so that the number of column names is the same as the number of columns.

SQL 语句包含一个 CREATE VIEW 语句，但是视图的列名数与 SELECT 语句返回的列数不同。更改 CREATE VIEW 语句，使列名数与列数相同。

-11023 String data right truncation.

This GBase 8s CLI error code is the same as SQLSTATE value 22001. The following function can return this error code: SQLPutData().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 22001 相同。以下函数可以返回此错误代码：SQLPutData()。

Before you called SQLPutData(), SQLGetInfo() returned "Y" when you called it with an information type of SQL_NEED_LONG_DATA_LEN. You then sent more data than the amount that the pcbValue argument specified in SQLBindParameter().

Send only the amount of data that pcbValue specifies.

在调用 SQLPutData() 之前，SQLGetInfo() 在使用 SQL_NEED_LONG_DATA_LEN 的信息类型调用它时返回“Y”。然后，您发送的数据比 SQLBindParameter() 中指定的 pcbValue参数的数量还要多。只发送 pcbValue 指定的数据量。

-11024 Indicator variable required but not supplied.

This GBase 8s CLI error code is the same as SQLSTATE value 22002. The following functions can return this error code: SQLExtendedFetch(),SQLFetch(), and SQLGetData().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 22002 相同。以下函数可以返回此错误代码：SQLExtendedFetch()、SQLFetch() 和 SQLGetData()。

For SQLExtendedFetch() or SQLFetch(), the value for a bound column was null but the INDICATOR_PTR field in the corresponding record was a null pointer.

For each column that can have a null value, set the corresponding pointer to a non-null value.

对于 SQLExtendedFetch() 或 SQLFetch()，绑定列的值为 NULL，而相应记录中的INDICATOR_PTR 字段为 NULL 指针。对于每个可以具有空值的列，将相应的指针设置为非空值。

For SQLGetData(), the column value was null but StrLen_or_Ind was a null pointer. For each column that can have a null value, set the corresponding StrLen_or_Ind value to a non-null value.

对于 SQLGetData()，列值为 NULL，而 StrLen_or_Ind 是空指针。对于每个可以具有空值的列，将相应的 StrLen_or_Ind 值设置为非空值。

-11025 Numeric value out of range.

This GBase 8s CLI error code is the same as SQLSTATE value 22003. The following functions can return this error code: SQLExecDirect(),SQLExecute(), SQLExtendedFetch(), SQLFetch(), SQLGetData(), SQLGetInfo(),and SQLPutData().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 22003 相同。以下函数可以返回此错误代码：SQLExecDirect()、SQLExecute()、SQLExtendedFetch()、SQLFetch()、SQLGetData()、SQLGetInfo() 和 SQLPutData()。

For SQLExecDirect() and SQLExecute(), the SQL statement contained a numeric parameter or literal that was too large. Therefore, the function truncated the whole (as opposed to fractional) part of the number before it assigned the number to the associated column. Change the SQL statement so that each numeric value fits into the associated column.

对于 SQLExecDirect() 和 SQLExecute()，SQL 语句包含一个太大的数值参数或文字。因此，函数在将数字分配给关联列之前，截断了整个数字(而不是小数)部分。更改 SQL 语句，以便每个数值都适合关联列。

For SQLExtendedFetch(), SQLFetch(), or SQLGetData(), the result set contains one or more columns that have values that are too large for the associated return parameters. If the function returned the value as a numeric value or string, the function truncated the whole (as opposed to fractional) part of the number. If the function returned the value as a binary value, the number lost binary significance. Change the return parameters so that each one can accommodate the associated value in the result set.

对于 SQLExtendedFetch()、SQLFetch() 或 SQLGetData()，结果集包含一个或多个列，这些列的值对于关联的返回参数来说太大。如果函数以数值或字符串的形式返回值，则函数截断数字的整个（而不是小数）部分。如果函数将该值作为二进制值返回，则该数字将失去二进制意义。更改返回参数，以便每个参数都能容纳结果集中的关联值。

For SQLGetInfo(), the requested information would lose numeric or binary significance if the function returned it. Set the storage for the requested information to a size that can accommodate the information.

对于 SQLGetInfo()，如果函数返回，请求的信息将失去数值或二进制意义。将请求的信息的存储设置为能够容纳该信息的大小。

For SQLPutData(), you called the function more than once for a parameter or column and one of the following problems occurred: (1) You called the function to send data to a column that does not have a character, binary, or data-source-specific data type, or (2) The function truncated the whole (as opposed to fractional) part of a number to assign it to the associated column.

Call SQLPutData() only for a column that has a character, binary, or data-source-specific data type, and change the data that you are sending so that it does not exceed the size of the column.

对于 SQLPutData()，您对参数或列多次调用该函数，出现了以下问题之一：(1)调用该函数将数据发送到不具有字符、二进制或数据源特定数据类型的列，或(2)该函数截断了数字的全部(而不是小数)部分，将其分配给相关的列。只对具有字符、二进制或数据源特定数据类型的列调用 SQLPutData()，并更改要发送的数据，使其不超过列的大小。

Returning the numeric value (as a numeric or string) for one or more columns causes the whole (as opposed to fractional) number to truncate.

For the range of values for the numeric parameter or column type that you tried to write or fetch, check the GBase 8s CLI Programmer's Manual.

返回一个或多个列的数值(作为数值或字符串)将导致整个(而不是小数)数字被截断。有关尝试编写或获取的数值参数或列类型的值范围，请检查 GBase 8s CLI 程序员手册。

-11026 Error in assignment.

The argument szSqlStr contains an SQL statement that contains a parameter or literal, and the value is incompatible with the data type of the associated table column. Check the list of compatible data types associated with the table column.

参数 szSqlStr 包含参数或文字的 SQL 语句，该值与关联表列的数据类型不兼容。检查与表列关联的兼容数据类型列表。

This GBase 8s CLI error code is the same as SQLSTATE value 22005. The following functions can return this error code: SQLExecDirect(), SQLExecute(),SQLExtendedFetch(), SQLFetch(), SQLGetData(), SQLPrepare(), and SQLPutData().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 22005 相同。以下函数可以返回此错误代码：SQLExecDirect()、SQLExecute()、SQLExtendedFetch()、SQLFetch()、SQLGetData()、SQLPrepare() 和 SQLPutData()。

For SQLExecDirect(), SQLExecute(), or SQLPrepare(), the SQL statement or prepared statement contained a parameter or literal that was incompatible with the data type of the associated column. Change the statement so that each parameter and literal is compatible with the data type of the column.

对于 SQLExecDirect()、SQLExecute() 或 SQLPrepare()，SQL 语句或准备好的语句包含与关联列的数据类型不兼容的参数或文字。更改语句，以便每个参数和文字与列的数据类型兼容。

For SQLExtendedFetch() or SQLFetch(), the function fetched a zero-length string that you had bound to a numeric data type, so the function converted the string to a zero. Change the data type of the parameter that is bound to the string.

对于 SQLExtendedFetch() 或 SQLFetch()，函数获取绑定到数字数据类型的零长度字符串，因此函数将字符串转换为零。更改绑定到字符串的参数的数据类型。

For SQLGetData() or SQLPutData(), the data type for the column is incompatible with the data type for the parameter. Change the data type for the parameter so that it is compatible with the data type for the column.

对于 SQLGetData() 或 SQLPutData()，列的数据类型与参数的数据类型不兼容。更改参数的数据类型，使其与列的数据类型兼容。

-11027 Datetime field overflow.

This GBase 8s CLI error code is the same as SQLSTATE value 22008. The following functions can return this error code: SQLExecDirect(), SQLExecute(),SQLExtendedFetch(), SQLFetch(), SQLGetData(), and SQLPutData().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 22008 相同。以下函数可以返回此错误代码：SQLExecDirect()、SQLExecute()、SQLExtendedFetch()、SQLFetch()、SQLGetData() 和 SQLPutData()。

The argument szSqlStr contains an SQL statement that contains a date,time, time-stamp parameter, or literal that is invalid. For the valid values of the szSqlStr argument, check the GBase 8s CLI Programmer's Manual.

参数 szSqlStr 包含一个包含日期、时间戳参数或无效的文字的 SQL 语句。有关szSqlStr 参数的有效值，请查看 GBase CLI 程序员手册。

For SQLExecDirect() or SQLExecute(), the function converted an SQL_C_DATE or SQL_C_TIMESTAMP value to an SQL_CHAR value, and the resulting value was not a valid date or time stamp. Change the SQL_C_DATE or SQL_C_TIMESTAMP value so that it will be a valid date or time stamp after the function converts it to an SQL_CHAR value.

对于 SQLExecDirect() 或 SQLExecute()，函数将 SQL_C_DATE 或 SQL_C_TIMSTAMP 值转换为 SQL_CHAR 值，其结果值不是有效的日期或时间戳。更改 SQL_C_DATE 或SQL_C_TIMESTAMP 值，使其在函数将其转换为SQL_CHAR值后成为有效的日期或时间戳。

For SQLExtendedFetch() or SQLFetch(), the SQL statement or prepared statement contained an invalid date or time stamp. Change the statement so that the date and time stamp values are valid.

对于 SQLExtendedFetch() 或 SQLFetch()，SQL 语句或准备好的语句包含无效的日期或时间戳。更改语句，以便日期和时间戳值有效。

For SQLGetData() or SQLPutData(), the data that the function sent or received was an invalid date or time stamp. For SQLPutData(), change the data so that it is a valid date or time stamp.

对于 SQLGetData() 或 SQLPutData()，函数发送或接收的数据是无效的日期或时间戳。

对于 SQLPutData()，更改数据，使其成为有效的日期或时间戳。

-11028 Division by zero.

This GBase 8s CLI error code is the same as SQLSTATE value 22012. The following functions can return this error code: SQLExecDirect(), SQLExecute(),SQLExtendedFetch(), SQLFetch(), and SQLGetData().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 22012 相同。以下函数可以返回此错误代码：SQLExecDirect()、SQLExecute()、SQLExtendedFetch()、SQLFetch()和SQLGetData()。

You either sent an arithmetic expression in an SQL statement or prepared statement to a database server, or a database server returned an arithmetic expression. This expression caused division by zero. Change the arithmetic expression so that it does not cause division by zero.

您可以在 SQL 语句中发送算术表达式，或者将准备好的语句发送到数据库服务器，或者数据库服务器返回算术表达式。这个表达式导致除以零。更改算术表达式，使其不会导致除以零。

-11029 String data, length mismatch.

This GBase 8s CLI error code is the same as SQLSTATE value 22026. The following function can return this error code: SQLParamData().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 22026 相同。以下函数可以返回此错误代码：SQLParamData()。

Before you called SQLParamData(), SQLGetInfo() returned "Y" when you called it with an information type of SQL_NEED_LONG_DATA_LEN. You then sent less data than the amount that the pcbValue argument specified in SQLBindParameter(). Send the amount of data that pcbValue specifies.

在调用 SQLParamData() 之前，SQLGetInfo() 在使用 SQL_NEED_LONG_DATA_LEN 的信息类型调用它时返回“Y”。然后，发送的数据少于 SQLBindParameter()中指定的pcbValue 参数的数量。发送 pcbValue 指定的数据量。

-11030 Integrity constraint violation.

This GBase 8s CLI error code is the same as SQLSTATE value 23000. The following functions can return this error code: SQLExecDirect() and SQLExecute().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 23000 相同。以下函数可以返回此错误代码：SQLExecDirect() 和 SQLExecute()。

One of the following problems occurred for one of the parameters in the SQL statement or prepared statement: (1) The parameter was null for a column that is defined as not null, or (2) The parameter provided a duplicate value for a column that can contain only unique values, or (3) The parameter violated some other integrity constraint. Change the parameter so that it does not violate any integrity constraints.

SQL 语句或准备语句中的参数之一出现下列问题：(1)对于定义为非空的列，参数为NULL；(2)该参数为只能包含唯一值的列提供了一个重复值，或者(3)该参数违反了其他完整性约束。更改参数，使其不违反任何完整性约束。

-11031 Invalid cursor state.

This GBase 8s CLI error code is the same as SQLSTATE value 24000. The following functions can return this error code: SQLColAttributes(),SQLColumnPrivileges(), SQLColumns(), SQLDescribeCol(), SQLExecDirect(),SQLExecute(), SQLExtendedFetch(), SQLFetch(), SQLForeignKeys(), SQLGetData(),SQLGetStmtOption(), SQLGetTypeInfo(), SQLPrepare(), SQLPrimaryKeys(),SQLProcedureColumns(), SQLProcedures(), SQLSetCursorName(),SQLSetStmtOption(), SQLSpecialColumns(), SQLStatistics(),SQLTablePrivileges(), and SQLTables().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 24000 相同。下面的函数可以返回这个错误代码：SQLColAttributes()、SQLColumnPrivileges(),、SQLColumns()、SQLDescribeCol()、SQLExecDirect()、SQLExecute()、SQLExtendedFetch()、SQLFetch()、SQLForeignKeys()、SQLGetData()、SQLGetStmtOption()、SQLGetTypeInfo()、SQLPrepare()、SQLPrimaryKeys()、SQLProcedureColumns()、SQLProcedures()、SQLSetCursorName()、SQLSetStmtOption()、SQLSpecialColumns()、SQLStatistics()、SQLTablePrivileges() 和 SQLTables()。

A cursor is open on hstmt, and SQLFetch or SQLExtendedFetch was not called. Check the sequence of operations. For example, confirm that you are not trying to execute an EXECUTE statement before the PREPARE statement finishes.

在 hstmt 上打开游标，未调用 SQLFetch 或 SQLExtendedFetch 。检查操作顺序。例如，在准备语句完成之前确认您没有尝试执行 EXECUTE 语句。

One of the following problems occurred:发生了以下问题之一：(1) The statement that is associated with the statement handle does not return a result set because there are no columns to describe. Change the statement so that it returns a result set. This problem can occur for SQLColAttributes()and SQLDescribeCol().

(1)与语句句柄关联的语句不返回结果集，因为没有要描述的列。更改语句，使其返回结果集。SQLColAttributes() 和 SQLDescribeCol() 可能会出现此问题。

(2) You already opened a cursor for the statement handle. Use the cursor that you already opened. This problem can occur for SQLColumnPrivileges(),SQLColumns(), SQLExecDirect(), SQLExecute(), SQLForeignKeys(),SQLGetTypeInfo(), SQLPrepare(), SQLPrimaryKeys(), SQLProcedureColumns(),SQLProcedures(), SQLSpecialColumns(), SQLStatistics(), SQLTablePrivileges(),and SQLTables().

(2)您已经为语句句柄打开了一个游标。使用您已经打开的光标。此问题可能发生在SQLColumnPrivileges()、SQLColumns()、SQLExecDirect()、SQLExecute()、SQLForeignKeys()、SQLGetTypeInfo()、SQLPrepare()、SQLPrimaryKeys()、SQLProcdureColumns()、SQLProcedures()、SQLSpecialColumns()、SQLStatistics()、SQLTablePrivileges() 和 SQLTables() 中。

(3) The cursor was positioned before the start of the result set or after the end of the result set. Make sure that the cursor is positioned within the result set. This problem can occur for SQLExecDirect(), SQLExecute(),SQLGetData(), and SQLGetStmtOption().

(3)光标位于结果集开始之前或结果集结束后。确保光标位于结果集中。对于SQLExecDirect()、SQLExecute()、SQLGetData() 和 SQLGetStmtOption()，可能会出现此问题。

(4) The statement handle was in an executed state, but no result set was associated with the statement handle. Make sure that a result set is associated with the statement handle. This problem can occur for SQLExtendedFetch(), SQLFetch(), and SQLGetData().

(4)语句句柄处于执行状态，但没有与语句句柄关联的结果集。确保结果集与语句句柄相关联。SQLExtendedFetch()、SQLFetch() 和 SQLGetData() 可能会出现此问题。

(5) You opened a cursor for the statement handle, but you did not call SQLFetch() or SQLExtendedFetch(). Call SQLFetch() or SQLExtendedFetch() after you open a cursor for a statement handle. This problem can occur for SQLGetData().

(5)打开语句句柄的游标，但没有调用 SQLFetch() 或 SQLExtendedFetch()。打开语句句柄的游标后，调用 SQLFetch() 或 SQLExtendedFetch()。SQLGetData() 可能会出现此问题。

(6) The fOption value was SQL_ROW_NUMBER, but the cursor was not open. Open a cursor before you use an fOption value of SQL_ROW_NUMBER. This problem can occur for SQLGetStmtOption().

(6)fOption 值为 SQL_ROW_NUMBER，但游标未打开。在使用 SQL_ROW_NUMBER 的 fOption值之前打开游标。SQLGetStmtOption() 可能会出现此问题。

(7) The statement handle was already in an executed state or a cursor-positioned state. Do not call this function for a statement handle that has already been executed or is already in a cursor-positioned state.

This problem can occur for SQLSetCursorName().

(7)语句句柄已经处于执行状态或光标定位状态。不要为已经执行或已处于游标定位状态的语句句柄调用此函数。SQLSetCursorName()可能会出现此问题。

(8) The fOption value was SQL_CONCURRENCY, SQL_SIMULATE_CURSOR, or SQL_CURSOR_TYPE, and the cursor was open. Do not use an open cursor for one of these fOption values. This problem can occur for SQLSetStmtOption().

(8)fOption 值为 SQL_CONCURRENCY、SQL_SIMULATE_CURSOR 或 SQL_CURSOR_TYPE，并且游标是打开的。不要使用打开的游标中的一个。SQLSetStmtOption()可能会出现此问题。

-11032 Invalid transaction state.

This GBase 8s CLI error code is the same as SQLSTATE value 25000. The following function can return this error code: SQLDisconnect().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 25000 相同。以下函数可以返回此错误代码：SQLDisconnect()。

A transaction is in process on the hdbc connection. The transaction remains active. Wait for the transaction to finish before you call SQLDisconnect()for the hdbc connection.

在 hdbc 连接上正在处理一个事务。事务仍然处于活动状态。在为 hdbc 连接调用SQLDisconnect() 之前，等待事务完成。

-11033 Invalid authorization specification.

This GBase 8s CLI error code is the same as SQLSTATE value 28000. The following functions can return this error code: SQLBrowseConnect(),SQLConnect(), and SQLDriverConnect().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 28000 相同。以下函数可以返回此错误代码：SQLBrowseConnect()、SQLConnect() 和 SQLDRiverConnect()。

Either the user identifier or the authorization string or both, as specified in the browse request connection string, violated restrictions that the data source defined. Confirm that you logged in correctly and that your password is current.

浏览请求连接字符串中指定的用户标识符或授权字符串或两者都违反了数据源定义的限制。确认您的登录正确，并且您的密码是当前的。

-11034 Invalid cursor name.

This GBase 8s CLI error code is the same as SQLSTATE value 34000. The following functions can return this error code: SQLExecDirect(), SQLPrepare(),and SQLSetCursorName().

此 GBase 8s CLI 错误代码与SQLSTATE值34000相同。以下函数可以返回此错误代码：SQLExecDirect()、SQLPrepare() 和 SQLSetCursorName()。

The argument szSqlStr contains a positioned update or delete statement,and the cursor referenced by the statement being executed is not open.

Check that the cursor is executed.

参数 szSqlStr 包含一个定位的 UPDATE 或 DELETE 语句，正在执行的语句引用的游标不打开。检查游标是否被执行。

For SQLExecDirect() or SQLPrepare(), the SQL statement contained a positioned UPDATE or DELETE, but the cursor that the statement references was not open.

Make sure that the cursor for an UPDATE or DELETE statement is open.

对于 SQLExecDirect() 或 SQLPrepare()，SQL 语句包含一个定位的 UPDATE 或DELETE，但是语句引用的游标没有打开。确保 UPDATE 或 DELETE 语句的游标是打开的。

For SQLSetCursorName(), the cursor name was invalid. For example, it might exceed the maximum allowable length. Make sure that the cursor name is valid.

对于 SQLSetCursorName()，游标名无效。例如，它可能超过允许的最大长度。确保游标名称有效。

-11035 Syntax error or access violation.

This GBase 8s CLI error code is the same as SQLSTATE value 37000. The following functions can return this error code: SQLExecDirect(),SQLNativeSql(), and SQLPrepare().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 37000 相同。以下函数可以返回此错误代码：SQLExecDirect()、SQLNativeSql() 和 SQLPrepare()。

The argument szSqlStr contains an SQL statement that is not preparable or contains a syntax error. Check the syntax of the SQL statement and make any necessary corrections.

参数 szSqlStr 包含一个无法准备或包含语法错误的 SQL 语句。检查 SQL 语句的语法并作出任何必要的更正。

-11036 Duplicate cursor name.

This GBase 8s CLI error code is the same as SQLSTATE value 3C000. The following function can return this error code: SQLSetCursorName().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 3C000 相同。以下函数可以返回此错误代码：SQLSetCursorName()。

The cursor name specified already exists. Specify a unique cursor name.

指定的游标名已经存在。指定唯一的游标名称。

-11037 Serialization failure.

This GBase 8s CLI error code is the same as SQLSTATE value 40001. The following functions can return this error code: SQLExecDirect(), SQLExecute(),SQLExtendedFetch(), and SQLFetch().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 40001 相同。以下函数可以返回此错误代码：SQLExecDirect()、SQLExecute()、SQLExtendedFetch()和SQLFetch()。

GBase 8s CLI terminated the transaction to prevent deadlock. If you consistently receive this error, a problem exists with the logic in your application.

GBase 8s CLI 终止事务以防止死锁。如果您始终收到此错误，则应用程序中的逻辑存在问题。

-11038 Syntax error or access violation.

This GBase 8s CLI error code is the same as SQLSTATE value 42000. The following functions can return this error code: SQLExecDirect(), SQLExecute(),and SQLPrepare().

此GBase 8s CLI错误代码与 SQLSTATE 值42000相同。以下函数可以返回此错误代码：SQLExecDirect()、SQLExecute()和SQLPrepare()。

The user does not have the privileges necessary to execute the SQL statement,or the SQL statement was not prepared, or the statement contained a syntax error. If you consistently receive this error, a problem exists with the logic in your application.

用户没有执行 SQL 语句所需的特权，或者 SQL 语句没有准备好，或者语句包含语法错误。如果您始终收到此错误，则应用程序中的逻辑存在问题。

-11039 Operation aborted.

This GBase 8s CLI error code is the same as SQLSTATE value 70100. The following function can return this error code: SQLCancel().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 70100 相同。以下函数可以返回此错误代码：SQLCancel()。

The data source did not process the cancel request because the database server does not support this function.

数据源没有处理取消请求，因为数据库服务器不支持此函数。

-11040 Driver does not support this function.

This GBase 8s CLI error code is the same as SQLSTATE value IM001. The following functions can return this error code: all ODBC functions except SQLAllocEnv(), SQLDataSources(), SQLDrivers(), SQLError(), SQLFreeConnect(),SQLFreeEnv(), and SQLGetFunctions().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 IM001 相同。以下函数可以返回此错误代码：所有 ODBC 函数，除了 SQLAllocEnv()、SQLDataSources()、SQLDrivers()、SQLError()、SQLFreeConnect()、SQLFreeEnv() 和 SQLGetFunctions()。

GBase 8s CLI does not support this function. Do not call this function.

GBase 8s CLI 不支持此功能。不要调用此函数。

-11041 Data source name not found and no default driver specified.

This GBase 8s CLI error code is the same as SQLSTATE value IM002. The following functions can return this error code: SQLBrowseConnect(),SQLConnect(), and SQLDriverConnect().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 IM002 相同。以下函数可以返回此错误代码：SQLBrowseConnect()、SQLConnect()和SQLDRiverConnect()。

One of the following problems occurred: (1) The function cannot find the initialization file, or (2) The data source that the szConnStrn string specified does not exist in the initialization file, and a default driver specification does not exist. Make sure that the initialization file exists.

Add the specified data source to the initialization file or create a default driver specification.

发生以下问题之一：(1)函数找不到初始化文件，或者(2)初始化文件中不存在指定的szConnStrn 字符串的数据源，并且不存在默认驱动程序规范。确保初始化文件存在。将指定的数据源添加到初始化文件或创建默认驱动程序规范。

The data source name specified in the connection request is not found in the ODBC.INI file or registry, and there is no default driver specification. Confirm that the data source name is registered. You can also provide a default data source.

连接请求中指定的数据源名称在 ODBC.INI 文件或注册表中找不到，也没有默认的驱动程序规范。确认数据源名称已注册。还可以提供默认数据源。

-11042 Specified driver could not be loaded.

This GBase 8s CLI error code is the same as SQLSTATE value IM003. The following functions can return this error code: SQLBrowseConnect(),SQLConnect(), and SQLDriverConnect().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 IM003 相同。以下函数可以返回此错误代码：SQLBrowseConnect()、SQLConnect()和SQLDRiverConnect()。

The driver listed in the data source specification in the ODBC.INI file or registry or the driver that the DRIVER keyword specifies is not found or cannot be loaded. Make sure that the specified driver exists. Confirm that you entered the correct spelling and path for the driver.

未找到或无法加载 ODBC.INI 文件或注册表中的数据源规范中列出的驱动程序或驱动程序关键字指定的驱动程序。确保指定的驱动程序存在。确认输入了驱动程序的正确拼写和路径。

-11043 Driver's SQLAllocEnv failed.

This GBase 8s CLI error code is the same as SQLSTATE value IM004. The following GBase 8s CLI functions can return this error code:SQLBrowseConnect(), SQLConnect(), and SQLDriverConnect(). The function called the driver version of SQLAllocEnv(), which returned an error. The CLI driver does not return this error.

此 GBase 8s CLI 错误代码与 SQLSTATE 值 IM004 相同。以下 GBase 8s CLI 函数可以返回此错误代码：SQLBrowseConnect()、SQLConnect()和SQLDRiverConnect()。函数调用SQLAllocEnv() 的驱动程序版本，它返回一个错误。CLI 驱动程序不返回此错误。

The most common failure could be attributed to a memory allocation failure.

Driver Manager's call to SQLAllocEnv could not succeed. See the error message returned by SQLError in the szErrorMsg to describe any driver specific SQLSTATE or error message if returned for other reasons.

最常见的故障可归因于内存分配失败。驱动程序管理器对 SQLAllocEnv 的调用无法成功。请参阅 szErrorMsg 中 SQLError 返回的错误消息，以描述任何特定于驱动程序的SQLSTATE 或由于其他原因返回的错误消息。

-11044 Driver's SQLAllocConnect failed.

This GBase 8s CLI error code is the same as SQLSTATE value IM005. The following functions can return this error code: SQLBrowseConnect(),SQLConnect(), and SQLDriverConnect(). The function called the driver version of SQLAllocConnect(), which returned an error. The CLI driver does not return this error.

此 GBase 8s CLI 错误代码与 SQLSTATE 值 IM005 相同。以下函数可以返回此错误代码：SQLBrowseConnect()、SQLConnect() 和 SQLDRiverConnect()。函数调用SQLAllocConnect() 的驱动程序版本，它返回一个错误。CLI 驱动程序不返回此错误。

The allocation of a connection handle may fail due to insufficient memory or initialization of new Database Connection handle (DBC). See the error message returned by SQLError in the szErrorMsg to describe driver specific SQLSTATE or error message if returned for other reasons.

由于内存不足或新的数据库连接句柄 (DBC) 初始化，连接句柄的分配可能会失败。请参阅 szErrorMsg 中 SQLError 返回的错误消息，以描述驱动程序特定的 SQLSTATE ，或者如果出于其他原因返回错误消息。

-11045 Driver's SQLSetConnectOption failed.

This GBase 8s CLI error code is the same as SQLSTATE value IM006. The following functions can return this error code: SQLBrowseConnect(),SQLConnect(), and SQLDriverConnect(). The function called the driver version of SQLSetConnectOption(), which returned an error. The CLI driver does not return this error.

此 GBase 8s CLI 错误代码与 SQLSTATE 值 IM006 相同。以下函数可以返回此错误代码：SQLBrowseConnect()、SQLConnect() 和 SQLDRiverConnect()。函数调用SQLSetConnectOption()的驱动程序版本，它返回一个错误。

See the error message returned by SQLError in the szErrorMsg to describe driver specific SQLSTATE or error message if returned for other reasons.

请参阅 szErrorMsg 中 SQLError 返回的错误消息，以描述驱动程序特定的 SQLSTATE 或由于其他原因返回的错误消息。

-11046 No data source or driver specified; dialog prohibited.

This GBase 8s CLI error code is the same as SQLSTATE value IM007. The following function can return this error code: SQLDriverConnect().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 IM007 相同。以下函数可以返回此错误代码：SQLDRiverConnect()。

The connection information flag, fDriverCompletion, is SQL_DRIVER_NOPROMPT,but the connection string does not provide enough information. Ensure that the driver keyword is in the connection string, or set the fDriverCompletion flag to SQLDriver prompt to have the driver prompt for additional connection information.

连接信息标志 fDriverCompletion 是 SQL_DRIVER_NOPROMPT，但是连接字符串没有提供足够的信息。确保驱动程序关键字在连接字符串中，或者将 fDriverCompletion 标志设置为 SQLDriver 提示符，以获得其他连接信息。

-11047 Dialog failed.

This GBase 8s CLI error code is the same as SQLSTATE value IM008. The following function can return this error code: SQLDriverConnect().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 IM008 相同。以下函数可以返回此错误代码：SQLDRiverConnect()。

GBase 8s CLI could not display the SQL Data Sources dialog box or the login dialog box because the hwnd value is null and the fDriverCompletion value is not SQL_DRIVER_NO_PROMPT. Use different values for hwnd and fDriverCompletion.

GBase 8s CLI 无法显示 SQL 数据源对话框或登录对话框，因为 hwnd 值为 NULL，fDriverCompletion 值不是 SQL_DRIVER_NO_PROMPT。对 hwnd 和 fDriverCompletion 使用不同的值。

-11048 Unable to load translation shared library (DLL).

This GBase 8s CLI error code is the same as SQLSTATE value IM009. The following functions can return this error code: SQLBrowseConnect(),SQLConnect(), SQLDriverConnect(), and SQLSetConnectOption().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 IM009 相同。以下函数可以返回此错误代码：SQLBrowseConnect()、SQLConnect()、SQLDRiverConnect() 和 SQLSetConnectOption()。

The driver is unable to load the translation DLL that is specified for the data source or for the connection. Check that the name and path for the DLL are correct.

驱动程序无法加载为数据源或连接指定的转换DLL。检查 DLL 的名称和路径是否正确。

-11049 Data source name too long.

This GBase 8s CLI error code is the same as SQLSTATE value IM010. The following functions can return this error code: SQLBrowseConnect() and SQLDriverConnect().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 IM010 相同。以下函数可以返回此错误代码：SQLBrowseConnect() 和 SQLDRiverConnect()。

A data source name that is in the initialization file is too long. Change any data source name that is too long.

初始化文件中的数据源名称太长了。更改任何太长的数据源名称。

-11049 Data source name too long.

The attribute value for DSN name is more than the maximum number of characters. For the accepted number of characters in the DSN name,check the GBase 8s CLI Programmer's Manual.

DSN 名称的属性值大于最大字符数。有关 DSN 名称中可接受的字符数，请查看 GBase 8s CLI 程序员手册。

-11050 Driver name too long.

This GBase 8s CLI error code is the same as SQLSTATE value IM011. The following functions can return this error code: SQLBrowseConnect() and SQLDriverConnect().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 IM011 相同。以下函数可以返回此错误代码：SQLBrowseConnect() 和 SQLDRiverConnect()。

The attribute value for the DRIVER keyword is more than 255 characters.

Use a keyword that is less than 255 characters.

Driver 关键字的属性值超过 255 个字符。使用小于 255 个字符的关键字。

-11051 DRIVER keyword syntax error.

This GBase 8s CLI error code is the same as SQLSTATE value IM012. The following functions can return this error code: SQLBrowseConnect() and SQLDriverConnect().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 IM012 相同。以下函数可以返回此错误代码：SQLBrowseConnect() 和 SQLDRiverConnect()。

In the initialization file, the syntax for the line that sets the driver path is incorrect. The keyword-value pair for the DRIVER keyword contains a syntax error.

Check that you entered the correct spelling and path for the driver.

在初始化文件中，设置驱动程序路径的行的语法不正确。Driver 关键字的关键字值对包含一个语法错误。检查是否为驱动程序输入了正确的拼写和路径。

-11053 Base table or view already exists.

This GBase 8s CLI error code is the same as SQLSTATE value S0001. The following functions can return this error code: SQLExecDirect() and SQLPrepare().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S0001 相同。以下函数可以返回此错误代码：SQLExecDirect() 和 SQLPrepare()。

The SQL statement contained a CREATE TABLE or CREATE VIEW statement, but the table name or view name already exists. Reword the query to use a unique table name or a unique view name.

SQL 语句包含 CREATE TABLE 或 CREATE VIEW 语句，但表名或视图名称已经存在。将查询重命名为使用唯一表名或唯一视图名称。

-11054 Base table not found.

This GBase 8s CLI error code is the same as SQLSTATE value S0002. The following functions can return this error code: SQLExecDirect() and SQLPrepare().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S0002 相同。以下函数可以返回此错误代码：SQLExecDirect() 和 SQLPrepare()。

The SQL statement contained a DROP TABLE, DROP VIEW, ALTER TABLE, CREATE VIEW,CREATE INDEX, GRANT, REVOKE, SELECT, DELETE, INSERT, UPDATE, or CREATE TABLE statement, but the table name or view name does not exist. Make sure that the necessary tables and views already exist.

SQL 语句包含一个 DROP TABLE、DROP VIEW、ALTER TABLE、CREATE VIEW、CREATE INDEX、GRANT、REVOKE、SELECT、DELETE、INSERT、UPDATE 或 CREATE TABLE 语句，确保必要的表和视图已经存在。

-11055 Index already exists.

This GBase 8s CLI error code is the same as SQLSTATE value S0011. The following functions can return this error code: SQLExecDirect() and SQLPrepare().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S0011 相同。以下函数可以返回此错误代码：SQLExecDirect()和 SQLPrepare()。

The SQL statement contained a CREATE INDEX statement, but the index name exists already. Reword the statement to use a unique index name.

SQL 语句包含一个 CREATE INDEX 语句，但索引名已经存在。将语句重命名为使用唯一索引名称。

-11056 Index not found.

This GBase 8s CLI error code is the same as SQLSTATE value S0012. The following functions can return this error code: SQLExecDirect() and SQLPrepare().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S0012 相同。以下函数可以返回此错误代码：SQLExecDirect() 和 SQLPrepare()。

The SQL statement contained a DROP INDEX statement, but the specified index name did not exist. Use an index name that exists already.

SQL 语句包含一个 DROP INDEX 语句，但指定的索引名不存在。使用已经存在的索引名称。

-11057 Column already exists.

This GBase 8s CLI error code is the same as SQLSTATE value S0021. The following functions can return this error code: SQLExecDirect() and SQLPrepare().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S0021 相同。以下函数可以返回此错误代码：SQLExecDirect() 和 SQLPrepare()。

The SQL statement contained an ALTER TABLE statement, but the column name specified in the ADD clause is not unique or identifies a column that already exists. Use column names that do not exist already.

SQL 语句包含 ALTER TABLE 语句，但 ADD 子句中指定的列名并不是唯一的，也不标识已经存在的列。使用不存在的列名。

-11058 Column not found.

This GBase 8s CLI error code is the same as SQLSTATE value S0022. The following functions can return this error code: SQLExecDirect() and SQLPrepare().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S0022 相同。以下函数可以返回此错误代码：SQLExecDirect() 和 SQLPrepare()。

The column cannot be associated with the table in the SQL statement.

Verify that you are using an existing table name in your SQL statement.

列不能与 SQL 语句中的表关联。验证您正在 SQL 语句中使用现有表名。

The SQL statement contained a CREATE INDEX, GRANT, REVOKE, SELECT, DELETE,INSERT, UPDATE, or CREATE TABLE statement, but one or more of the column names did not exist. Use column names that exist already.

SQL 语句包含一个 CREATE INDEX、GRANT、REVOKE、SELECT、DELETE、INSERT、UPDATE或 CREATE TABLE 语句，但不存在一个或多个列名。使用已经存在的列名。

-11060 General error.

An error occurred that has no specific SQL_STATE. In this case,additional text is provided that identifies the source of the problem.

This GBase 8s CLI error code is the same as SQLSTATE value S1000.

没有特定 SQL_STATE 的错误发生。在这种情况下，将提供更多的文本来标识问题的根源。此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1000 相同。

-11061 Memory allocation failure.

This GBase 8s CLI error code is the same as SQLSTATE value S1001. The following functions can return this error code: all GBase 8s CLI functions except SQLError(), SQLFreeConnect(), and SQLFreeEnv().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1001 相同。以下函数可以返回此错误代码：除了 SQLError()、SQLFreeConnect()和 SQLFreeEnv() 之外，所有 GBase 8s CLI函数都可以返回。

The driver or driver manager cannot allocate memory for the connection handle. Try to reduce the number of processes currently running or provide more memory.

驱动程序或驱动程序管理器无法为连接句柄分配内存。尽量减少当前正在运行的进程的数量，或者提供更多的内存。

-11062 Invalid column number.

This GBase 8s CLI error code is the same as SQLSTATE value S1002. The following functions can return this error code: SQLBindCol(),SQLColAttributes(), SQLDescribeCol(), SQLExtendedFetch(), SQLFetch(), and SQLGetData().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1002相同。以下函数可以返回此错误代码：SQLBindCol()、SQLColAttributes()、SQLDescribeCol()、SQLExtendedFetch()、SQLFetch()和 SQLGetData()。

The value specified for the argument icol exceeds the maximum number of columns that the cursor defines. Confirm that the column number you are fetching is in the result set of the cursor.

为参数 icol 指定的值超过游标定义的最大列数。确认您要获取的列号在游标的结果集中。

For all functions except SQLGetData(), a column number was 0, exceeded the number of columns in the result set, or exceeded the number of columns that the data source supports. For SQLBindCol(), make sure that the column number does not exceed the maximum number of columns that the data source can support. For SQLColAttributes(), use a descriptor type of SQL_COLUMN_COUNT if the column number is 0 or exceeds the number of columns in the result set.

For SQLDescribeCol() and SQLFetch(), make sure that the column numbers are not 0 and do not exceed the number of columns in the result set. For SQLExtendedFetch(), set SQL_USE_BOOKMARKS to SQL_UB_OFF if column 0 is bound,and make sure that the bound column numbers do not exceed the number of columns in the result set.

对于除 SQLGetData() 以外的所有函数，列号为 0，超过结果集中的列数，或超过数据源支持的列数。对于 SQLBindCol()，请确保列号不超过数据源可以支持的最大列数。对于SQLColAttributes()，如果列号为 0 或超过结果集中的列数，则使用SQL_COLUMN_COUNT的描述符类型。对于 SQLDescribeCol() 和 SQLFetch()，请确保列号不为 0，并且不超过结果集中的列数。对于 SQLExtendedFetch()，如果绑定了 0 列，则将SQL_USE_BOOKMARKS 设置为 SQL_UB_OFF，并确保绑定的列号不超过结果集中的列数。

For SQLGetData(), one of the following problems occurred: (1) The column number was 0 and you either called SQLFetch() to get the data or you set SQL_USER_BOOKMARKS to SQL_UB_OFF, (2) The column number exceeded the number of columns in the result set, or (3) You already called SQLGetData() for the current row. Make sure that you do not call SQLFetch() or set SQL_USER_BOOKMARKS to SQL_UB_OFF if the column number is 0, that the column number does not exceed the number of columns in the result set, and that you have not already called SQLGetData() for the current row.

对于 SQLGetData()，出现了以下问题之一：(1)列号为0，您可以调用 SQLFetch() 来获取数据，也可以将 SQL_USER_BOOKMARKS 设置为 SQL_UB_OFF，(2)列号超过结果集中的列数，或者(3)您已经为当前行调用了SQLGetData()。如果列号为 0 时，请确保不调用SQLFetch() 或将 SQL_USER__BOOKMARKS 设置为 SQL_UB_OFF，且列号不超过结果集中的列数，并且尚未为当前行调用 SQLGetData()。

-11063 Program type out of range.

This GBase 8s CLI error code is the same as SQLSTATE value S1003. The following functions can return this error code: SQLBindCol(),SQLBindParameter(), and SQLGetData().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1003 相同。以下函数可以返回此错误代码：SQLBindCol()、SQLBindParameters()和SQLGetData()。

The GBase 8s CLI C data type (fCType) argument was not a valid GBase 8s CLI C data type or SQL_C_DEFAULT. Set the GBase 8s CLI C data type to a valid value.

GBase 8s CLIC 数据类型(FCType)参数不是有效的 GBase 8s CLIC 数据类型或SQL_C_DEFAULT。将 GBase 8s CLIC 数据类型设置为有效值。

For SQLBindCol(), it is also possible that the column number was 0 and the GBase 8s CLI C data type was not SQL_C_BOOKMARK. If the column number is 0,set the GBase 8s CLI C data type to SQL_C_BOOKMARK.

对于 SQLBindCol()，还可能列号为 0，而 GBase 8s CLIC 数据类型不是SQL_C_BOOKMARK。如果列号为 0，则将 GBase 8s CLIC 数据类型设置为SQL_C_BOOKMARK。

-11064 SQL data type out of range.

This GBase 8s CLI error code is the same as SQLSTATE value S1004. The following functions can return this error code: SQLBindParameter() and SQLGetTypeInfo().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1004 相同。以下函数可以返回此错误代码：SQLBindParameter() 和 SQLGetTypeInfo()。

The value specified for the argument fSqlType is in the block of numbers reserved for CLI SQL data type indicators but is not a valid ODBC SQL data type indicator. Check that you are referring to an ODBC SQL data type that this driver and this server support.

为参数 fSqlType 指定的值位于为 CLI SQL 数据类型指示符保留的数字块中，但不是有效的 ODBC SQL 数据类型指示符。检查是否引用此驱动程序和此服务器支持的 ODBC SQL数据类型。

The GBase 8s CLI SQL data type (fSqlType) argument was not a valid GBase 8s CLI SQL data type. Set GBase 8s CLI SQL data type to a valid value.

GBase 8s CLI SQL 数据类型(fSqlType)参数不是有效的 GBase 8s CLI SQL 数据类型。

将 GBase 8s CLI SQL 数据类型设置为有效值。

-11065 Operation canceled.

This GBase 8s CLI error code is the same as SQLSTATE value S1008. The following functions can return this error code: SQLAllocConnect(),SQLAllocStmt(), SQLBindCol(), SQLBindParameter(), SQLColumns(),SQLExecDirect(), SQLForeignKeys(), SQLGetData(), SQLGetInfo(),SQLNativeSql(), SQLParamData(), SQLPrepare(), SQLProcedureColumns(),SQLPutData(), SQLSetConnectOption(), SQLSetCursorName(), and SQLSetStmtOption().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1008 相同。以下函数可以返回此错误代码：SQLAllocConnect()、SQLAllocStmt()、SQLBindCol()、SQLBindParameter()、SQLColumns()、SQLExecDirect()、SQLForeignKeys()、SQLGetData()、SQLInfo()、SQLNativeSql()、SQLParamData()、SQLPrepare()、SQLProcdureColumns()、SQLPutData()、SQLSetConnectOption()、SQLSetCursorName() 和 SQLSetsttOption()。

Before the function could complete execution, a different thread called SQLCancel() for the statement handle. Fix your application logic.

在函数完成执行之前，语句句柄有一个不同的线程名为 SQLCancel()。修复您的应用程序逻辑。

For SQLParamData() and SQLPutData(), one of the following problems can also occur: (1) You called SQLExecute() or SQLExecDirect() for the statement handle and the function returned SQL_NEED_DATA, or (2) You called SQLCancel()before data was sent for all data-at-execution parameters or columns. Fix your application logic.

对于 SQLParamData() 和 SQLPutData()，也可能出现以下问题之一：(1)对于语句句柄和返回的函数，您调用 SQLExecute() 或 SQLExecDirect()，或者(2)在为所有数据执行参数或列发送数据之前调用 SQLCancel()。修复您的应用程序逻辑。

-11066 Invalid argument value.

This GBase 8s CLI error code is the same as SQLSTATE value S1009. The following functions can return this error code: SQLAllocConnect(),SQLAllocStmt(), SQLBindParameter(), SQLGetData(), SQLGetInfo(),SQLExecDirect(), SQLForeignKeys(), SQLNativeSql(), SQLPrepare(), SQLPutData(),SQLSetConnectOption(), SQLSetCursorName(), and SQLSetStmtOption().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1009 相同。以下函数可以返回此错误代码：SQLAllocConnect()、SQLAllocStmt()、SQLBindParameter()、SQLGetData()、SQLGetInfo()、SQLExecDirect()、SQLForeignKeys()、SQLNativeSql()、SQLPrepare()、SQLPutData()、SQLSetConnectOption()、SQLSetCursorName()和SQLSetStmtOption()。

Check that the arguments passed with the CLI request are correct.

检查随 CLI 请求传递的参数是否正确。

For SQLAllocConnect(), SQLAllocStmt(), SQLExecDirect(), SQLGetData(),SQLNativeSql, SQLPrepare(), and SQLSetCursorName(), the pointer argument(phdbc, phstmt, rgbValue, szCursor, szSqlStr, or szSqlStrIn) was a null pointer. Set the pointer argument to a non-null value.

对于SQLAllocConnect()、SQLAllocStmt()、SQLExecDirect()、SQLGetData()、SQLNativeSql、SQLPrepare()和SQLSetCursorName()，指针参数(phdbc、phstmt、rgbValue、szCursor、szSqlStr或szSqlStrIn)是空指针。将指针参数设置为非空值。

For SQLBindParameter(), rgbValue and pcbValue were null pointers and fParamType was not SQL_PARAM_OUTPUT. Set rgbValue or pcbValue to a non-null pointer or set fParamType to SQL_PARAM_OUTPUT.

对于 SQLBindParameter()，rgbValue 和 pcbValue 是空指针，fParamType 不是SQL_PARAM_OUTPUT。将 rgbValue 或 pcbValue 设置为非空指针，或将 fParamType 设置为 SQL_PARAM_OUTPUT。

For SQLForeignKeys(), szPkTableName and szFkTableName were null pointers. Set szPkTableName or szFkTableName to a non-null pointer.

对于 SQLForeignKeys()，szPkTableName 和 szFkTableName 是空指针。将szPkTableName 或 szFkTableName 设置为非空指针。

For SQLGetInfo(), fInfoType was SQL_DRIVER_HSTMT and rgbInfoValue did not point to a valid statement handle. Change rgbInfoValue to point to a valid statement handle.

对于 SQLGetInfo()，fInfoType 是 SQL_DRIVER_HSTMT，rgbInfoValue 没有指向有效的语句句柄。将 rgbInfoValue 更改为指向有效的语句句柄。

For SQLPutData(), rgbValue was a null pointer and cbValue was not 0,SQL_DEFAULT_PARAM, or SQL_NULL_DATA. Change cbValue to 0, SQL_DEFAULT_PARAM,or SQL_NULL_DATA.

对于 SQLPutData()，rgbValue 是空指针，cbValue 不是 0、SQL_DEFAULT_PARAM 或SQL_NULL_DATA。将 cbValue 更改为 0、SQL_DEFAULT_PARAM 或 SQL_NULL_DATA。

For SQLSetConnectOption() and SQLSetStmtOption(), vParam was not valid for the specified fOption value. Change vParam to a valid value.

对于 SQLSetConnectOption() 和 SQLSetStmtOption()，vParam 对于指定的 fOption 值无效。将 vParam 更改为有效值。

-11067 Function sequence error.

An asynchronously executing function is called for the hstmt and is still executing when this function is called, or an attempt was made to use an hstmt out of sequence. Check the sequence of operations. For example, check that you are not trying to execute an EXECUTE statement before the PREPARE statement is finished.

对 hstmt 调用异步执行函数，在调用此函数时仍在执行，或尝试使用不符合顺序的hstmt。检查操作顺序。例如，在准备语句完成之前，检查是否试图执行 EXECUTE 语句。

This GBase 8s CLI error code is the same as SQLSTATE value S1010. The following functions can return this error code: SQLBindCol(),SQLBindParameter(), SQLColAttributes(), SQLColumnPrivilages(), SQLColumns(),SQLDescribeCol(), SQLDisconnect(), SQLExecDirect(), SQLExecute(),SQLExtendedFetch(), SQLFetch(), SQLFreeConnect(), SQLFreeEnv(), SQLFreeStmt(),SQLForeignKeys(), SQLGetConnectOption(), SQLGetCursorName(), SQLGetData(),SQLGetFunctions(), SQLGetStmtOption(), SQLGetTypeInfo(), SQLMoreResults(),SQLNumParams(), SQLNumResultCols(), SQLParamData(), SQLPrepare(),SQLPrimaryKeys(), SQLProcedureColumns(), SQLProcedures(), SQLPutData(),SQLRowCount(), SQLSetConnectOption(), SQLSetCursorName(), SQLSetStmtOption(),SQLSpecialColumns(), SQLStatistics(), SQLTablePrivileges(), SQLTables(), and SQLTransact().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1010 相同。以下函数可以返回此错误代码：SQLBindCol()、SQLBindParameter()、SQLColAttributes()、SQLColumnPrivilages()、SQLColumns()、SQLDescribeCol()、SQLDisconnect()、SQLExecDirect()、SQLExecute()、SQLExtendedFetch()、SQLFetch()、SQLFreeConnect()、SQLFreeEnv()、SQLFreeStmt()、SQLForeignKeys()、SQLGetConnectOption()、SQLGetCursorName()、SQLGetData()、SQLGetFunctions()、SQLGetStmtOption()、SQLGetTypeInfo()、SQLMoreResults()、SQLNumParams()、SQLNumResultCols()、SQLParamData()、SQLPrepare()、SQLPrimaryKeys()、SQLProcedureColumns()、SQLProcedures()、SQLPutData()、SQLRowCount()、SQLSetConnectOption()、SQLSetCursorName()、SQLSetStmtOption()、SQLSpecialColumns()、SQLStatistics()、SQLTablePrivileges()、SQLTables()和 SQLTransact()。

For SQLBindCol(), SQLBindParameter(), SQLColAttributes(),SQLColumnPrivilages(), SQLColumns(), SQLDescribeCol(), SQLDisconnect(),SQLExecDirect(), SQLExecute(), SQLExtendedFetch(), SQLFetch(), SQLFreeStmt(),SQLForeignKeys(), SQLGetCursorName(), SQLGetData(), SQLGetStmtOption(),SQLGetTypeInfo(), SQLMoreResults(), SQLNumParams(), SQLNumResultCols(),SQLPrepare(), SQLPrimaryKeys(), SQLProcedureColumns(), SQLProcedures(),SQLRowCount(), SQLSetConnectOption(), SQLSetCursorName(), SQLSetStmtOption(),SQLSpecialColumns(), SQLStatistics(), SQLTablePrivileges(), SQLTables(), and SQLTransact(), GBase 8s CLI called SQLExecute(), SQLExecDirect(), or SQLSetPos() for the statement handle and returned SQL_NEED_DATA, which means that you called this function before data was sent for the data-at-execution parameters or columns. Wait until data is sent for all the data-at-execution parameters or columns before you call this function.

对于 SQLBindCol()、SQLBindParameter()、SQLColAttributes()、SQLColumnPrivilages()、SQLColumns()、SQLDescribeCol()、SQLDisconnect()、SQLExecDirect()、SQLExecute()、SQLExtendedFetch()、SQLFetch()、SQLFreeStmt()、SQLForeignKeys()、SQLGetCursorName()、SQLGetData()、SQLGetStmtOption()、SQLGetTypeInfo()、SQLMoreResults()、SQLNumParams()、SQLNumResultCols()、SQLPrepare()、SQLPrimaryKeys()、SQLProcedureColumns()、SQLProcedures()、SQLRowCount()、SQLSetConnectOption()、SQLSetCursorName()、SQLSetStmtOption()、SQLSpecialColumns()、SQLStatistics()、SQLTablePrivileges()、SQLTables() 和SQLTransact()。对于语句句柄，GBase 8s CLI 调用 SQLExecute()、SQLExecDirect()或SQLSetPos()，并返回 SQL_NEED_DATA，这意味着在数据被发送到数据执行参数或列之前调用此函数。在调用此函数之前，要等待所有数据执行参数或列的数据被发送。

Additionally for SQLColAttributes(), SQLDescribeCol(), SQLNumParams(), and SQLNumResultCols(), you called this function before you called SQLPrepare()or SQLExecDirect for the statement handle. Do not call this function before SQLPrepare() or SQLExecDirect().

另外，对于 SQLColAttributes()、SQLDescribeCol()、SQLNumParams() 和SQLNumResultCols()，在为语句句柄调用 SQLPrepare() 或 SQLExecDirect 之前调用了此函数。不要在 SQLPrepare() 或 SQLExecDirect() 之前调用此函数。

Additionally for SQLExecute(), the statement handle was not prepared due to one of the following conditions: (1) The statement handle was not in an executed state, (2) You opened a cursor on the statement handle and called SQLFetch() or SQLExtendedFetch(), (3) The statement handle was in an executed state but did not have a result set associated with it, or (4) The statement handle was in an executed state but you did not call SQLFetch() or SQLExtendedFetch(). Make sure that none of these conditions occurs.

另外，对于 SQLExecute()，由于以下条件之一，语句句柄没有准备好：(1)语句句柄没有处于执行状态，(2)在语句句柄上打开游标，调用 SQLFetch() 或 SQLExtendedFetch()，(3)语句句柄处于执行状态，但没有与其关联的结果集，或者(4)语句句柄处于执行状态，但没有调用 SQLFetch() 或 SQLExtendedFetch()。确保没有发生这些情况。

Additionally for SQLExtendedFetch(), SQLFetch(), and SQLGetData(), one of the following problems occurred: (1) The statement handle was not in an executed state because you did not call SQLExecDirect(), SQLExecute(), or a catalog function before you called this function, or (2) You called this function after you called SQLFetch() and before you called SQLFreeStmt() with the SQL_CLOSE option. Make sure that neither of these conditions occurs.

另外，对于 SQLExtendedFetch()、SQLFetch() 和 SQLGetData()，出现了以下问题之一：(1)语句句柄没有处于执行状态，因为在调用此函数之前没有调用SQLExecDirect()、SQLExecute()或目录函数，或者(2)在调用 SQLFetch() 之后和使用 SQL_CLOSE 选项调用SQLFreeStmt() 之前调用此函数。确保这两种情况都不会发生。

For SQLFreeConnect(), you called this function before you called SQLDisconnect() for the connection handle.

对于 SQLFreeConnect()，在为连接句柄调用 SQLDisconnect() 之前调用了此函数。

For SQLFreeEnv(), at least one connection handle was in an allocated or connected state. Call SQLDisconnect() and SQLFreeConnect() for each connection handle before you call this function.

对于 SQLFreeEnv()，至少有一个连接句柄处于已分配或连接状态。在调用此函数之前，对每个连接句柄调用 SQLDisconnect() 和 SQLFreeConnect()。

For SQLGetConnectOption(), SQLGetFunctions(), and additionally for SQLSetConnectOption(), GBase 8s CLI called SQLBrowseConnect() for the connection handle and returned SQL_NEED_DATA, which means that you called this function before SQLBrowseConnect() returned SQL_SUCCESS_WITH_INFO or SQL_SUCCESS. Wait until SQLBrowseConnect() returns SQL_SUCCESS_WITH_INFO or SQL_SUCCESS before you call this function.

对于SQLGetConnectOption()、SQLGetFunctions()和SQLSetConnectOption()，GBase 8s为连接句柄调用 SQLBrowseConnect()，并返回 SQL_NEED_DATA，这意味着在SQLBrowseConnect() 返回 SQL_SUCCESS_WITH_INFO 或 SQL_SUCCESS 之前调用该函数。

在调用此函数之前，请等待 SQLBrowseConnect() 返回SQL_SUCCESS_WITH_INFO 或SQL_SUCCESS。

Additionally for SQLGetFunctions(), you called this function before you called SQLConnect(), SQLBrowseConnect(), or SQLDriverConnect(). Do not call this function before SQLConnect(), SQLBrowseConnect(), or SQLDriverConnect().

另外，对于 SQLGetFunctions()，在调用 SQLConnect()、SQLBrowseConnect() 或SQLDRiverConnect() 之前调用了这个函数。不要在 SQLConnect()、SQLBrowseConnect()或 SQLDRiverConnect() 之前调用此函数。

For SQLParamData(), the previous function call was to this function. Call this function only after you call SQLExecDirect() or SQLExecute() where the return code is SQL_NEED_DATA or after you call SQLPutData().

对于 SQLParamData()，前面的函数调用是对该函数的调用。只有在调用 SQLExecDirect() 或 SQLExecute() (其中返回代码为 SQL_NEED_DATA )或调用SQLPutData() 之后，才调用此函数。

For SQLPutData(), the previous function call was to SQLExecDirect() or SQLExecute() where the return code was SQL_NEED_DATA. Call this function only after you call SQLParamData() or SQLPutData().

对于 SQLPutData()，前面的函数调用是对 SQLExecDirect()或 SQLExecute() 的函数调用，其中返回代码为 SQL_NEED_DATA。只有在调用 SQLParamData() 或 SQLPutData()之后才调用此函数。

Additionally for SQLRowCount(), you called this function before you called SQLExecute() or SQLExecDirect() for the statement handle. Do not call this function before SQLExecute() or SQLExecDirect().

另外，对于 SQLRowCount()，在为语句句柄调用 SQLExecute() 或 SQLExecDirect()之前调用了此函数。不要在 SQLExecute() 或 SQLExecDirect() 之前调用此函数。

-11068 Operation invalid at this time.

This GBase 8s CLI error code is the same as SQLSTATE value S1011. The following functions can return this error code: SQLGetStmtOption(),SQLSetConnectOption(), and SQLSetStmtOption().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1011相同。以下函数可以返回此错误代码：SQLGetStmtOption()、SQLSetConnectOption() 和 SQLSetStmtOption()。

For SQLGetStmtOption(), fOption was SQL_GET_BOOKMARK and SQL_USE_BOOKMARKS was SQL_UB_OFF. If SQL_USE_BOOKMARKS is SQL_UB_OFF, do not use this option value.

对于 SQLGetStmtOption()，fOption 是 SQL_GET_BOOKMARK ，SQL_USE_BOOKMARKS 是SQL_UB_OFF。如果 SQL_USE_BOOKMARKS 是 SQL_UB_OFF，则不要使用此选项值。

For SQLSetConnectOption(), fOption was SQL_TXN_ISOLATION and a transaction was open. Make sure that no transactions are open before you use this option value.

对于 SQLSetConnectOption()，fOption 是 SQL_TXN_ISOLATION，并打开了一个事务。在使用此选项值之前，请确保没有打开任何事务。

For SQLSetStmtOption(), fOption was SQL_CONCURRENCY, SQL_SIMULATE_CURSOR, or SQL_CURSOR_TYPE and the statement was prepared. If the statement is prepared,do not use one of these option values.

对于 SQLSetStmtOption()，fOption 是 SQL_CONCURRENCY、SQL_SIMULATE_CURSOR 或SQL_CURSOR_TYPE ，并准备好了语句。如果语句已准备好，请不要使用这些选项值之一。

-11069 Invalid transaction operation code specified.

This GBase 8s CLI error code is the same as SQLSTATE value S1012. The following function can return this error code: SQLTransact().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1012 相同。以下函数可以返回此错误代码：SQLTransact()。

The value specified for the argument fType is neither SQL_COMMIT nor SQL_ROLLBACK. Check the value and verify that it is valid for the ftype parameter.

为参数 fType 指定的值既不是 SQL_COMMIT 也不是 SQL_ROLLLBACK。检查该值并验证它对于 ftype 参数是否有效。

-11070 No cursor name available.

This GBase 8s CLI error code is the same as SQLSTATE value S1015. The following function can return this error code: SQLGetCursorName().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1015相同。以下函数可以返回此错误代码：SQLGetCursorName()。

No open cursor exists on the hstmt, and no cursor name has been set with SQLSetCursorName. Check the sequence of operations. For example,check that you are not trying to execute an EXECUTE statement before the PREPARE statement is finished.

hstmt上不存在打开的游标，也没有用SQLSetCursorName设置游标名。检查操作顺序。

例如，在准备语句完成之前，检查是否试图执行EXECUTE语句。

The statement handle does not have an open cursor and did not previously call SQLSetCursorName() to set a cursor name. Open a cursor or set a cursor name.

语句句柄没有打开的游标，以前也没有调用 SQLSetCursorName() 来设置游标名。打开游标或设置游标名称。

-11071 Invalid string or buffer length.

This GBase 8s CLI error code is the same as SQLSTATE value S1090. The following functions can return this error code: SQLBindCol(),SQLBindParameter(), SQLBrowseConnect(), SQLColAttributes(),SQLColumnPrivileges(), SQLColumns(), SQLConnect(), SQLDataSources(),SQLDescribeCol(), SQLDriverConnect(), SQLDrivers(), SQLExecDirect(),SQLExecute(), SQLForeignKeys(), SQLGetCursorName(), SQLGetData(),SQLGetInfo(), SQLNativeSql(), SQLPrepare(), SQLPrimaryKeys(),SQLProcedureColumns(), SQLProcedures(), SQLPutData(), SQLSetCursorName(),SQLSpecialColumns(), SQLStatistics(), SQLTablePrivileges(), and SQLTables().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1090 相同。以下函数可以返回此错误代码：SQLBindCol()、SQLBindParameter()、SQLBrowseConnect()、SQLColAttributes()、SQLColumnPrivileges()、SQLColumns()、SQLConnect()、SQLDataSources()、SQLDescribeCol()、SQLDriverConnect()、SQLDrivers()、SQLExecDirect()、SQLExecute()、SQLForeignKeys()、SQLGetCursorName()、SQLGetData()、SQLGetInfo()、SQLNativeSql()、SQLPrepare()、SQLPrimaryKeys()、SQLProcedureColumns()、SQLProcedures()、SQLPutData()、SQLSetCursorName()、SQLSpecialColumns()、SQLStatistics()、SQLTablePrivileges()和 SQLTables()。

The value specified for the argument cbValueMax is less than zero.

Supply a value for the argument cbValueMax that is zero or greater.

为参数 cbValueMax 指定的值小于零。为参数 cbValueMax 提供一个为零或更大的值。

For all functions, an argument that specified a string or buffer length, such as cbCursor, cbConnStrIn, or cbSqlStr, had one or more of the following problems: (1) It was less than 0, (2) It was less than 0 but not equal to SQL_NTS or SQL_NULL_DATA, (3) It was less than 0 but the corresponding pointer was not a null pointer, (4) It was equal to 1, or (5) It was too large. Set the string or buffer length to a valid value.

对于所有函数，指定字符串或缓冲区长度的参数（如cbCursor、cbConnStrIn 或cbSqlStr）存在以下一个或多个问题：(1)小于0，(2)小于 0，但不等于 SQL_NTS 或SQL_NULL_DATA；(3)它小于 0，但对应的指针不是空指针，(4)等于 1，或者(5)它太大。

将字符串或缓冲区长度设置为有效值。

Additionally for SQLExecDirect() and SQLExecute(), a parameter value that was set with SQLBindParameter() had one of the following problems: (1) It was a null pointer, and the parameter length was not 0, SQL_NULL_DATA,SQL_DATA_AT_EXEC, or less than or equal to SQL_LEN_DATA_AT_EXEC_OFFSET, or(2) It was not a null pointer, and the parameter length was less than 0 but was not SQL_NTS, SQL_NULL_DATA, SQL_DATA_AT_EXEC, or less than or equal to SQL_LEN_EXEC_DATA_AT_EXEC_OFFSET. Set the parameter value to a valid value.

此外，对于 SQLExecDirect() 和 SQLExecute()，参数值与 SQLBindParameter() 一起设置有以下问题：（1）它是空指针，参数长度不是 0，SQL_NULL_DATA，SQL_DATA_AT_EXEC，或者小于或等于 SQL_LEN_DATA_AT_EXEC_OFFSET，或者（2）它不是空指针，并且参数长度小于 0，但不是 SQL NTS、SQL_NULL_DATA、SQL_DATA_AT_EXEC，或小于或等于 SQL_LEN_EXEC_DATA_AT_EXEC_OFFSET。将参数值设置为有效值。

-11072 Descriptor type out of range.

This GBase 8s CLI error code is the same as SQLSTATE value S1091. The following function can return this error code: SQLColAttributes().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1091 相同。以下函数可以返回此错误代码：SQLColAttributes()。

The value specified for the argument fDescType is in the block of numbers reserved for driver-specific descriptor types but is unsupported by the driver. For a list of accepted descriptor types,check the GBase 8s CLI Programmer's Manual.

为参数 fDescType 指定的值位于为特定于驱动程序的描述符类型保留的数字块中，但不受驱动程序的支持。要获得可接受描述符类型的列表，请查看 GBase 8s CLI 程序员手册。

The fDescType argument was not a valid descriptor type. Set fDescType to a valid value.

fDescType 参数不是有效的描述符类型。将 fDescType 设置为有效值。

-11073 Option type out of range.

This GBase 8s CLI error code is the same as SQLSTATE value S1092. The following functions can return this error code: SQLFreeStmt(),SQLGetConnectOption(), SQLGetStmtOption(), SQLSetConnectOption(), and SQLSetStmtOption().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1092 相同。以下函数可以返回此错误代码：SQLFreeStmt()、SQLGetConnectOption()、SQLGetStmtOption()、SQLSetConnectOption() 和 SQLSetStmtOption()。

The value specified for the argument fOption is in the block of numbers reserved for CLI connection and statement option but is not valid for the version of ODBC that the driver supports. For a list of accepted descriptor types, check the GBase 8s CLI Programmer's Manual.

为参数 fOption 指定的值位于为 CLI 连接和语句选项保留的数字块中，但对于驱动程序支持的 ODBC 版本无效。有关可接受描述符类型的列表，请查看 GBase CLI 程序员手册。

The fOption argument was not a valid option value. Set fOption to a valid value.

fOption 参数不是有效的选项值。将 fOption 设置为有效值。

-11074 Invalid parameter number.

This GBase 8s CLI error code is the same as SQLSTATE value S1093. The following function can return this error code: SQLBindParameter().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1093 相同。以下函数可以返回此错误代码：SQLBindParameter()。

The value specified for the argument ipar is less than one or is greater than the maximum number of parameters that the data source supports. To verify that the value is in the correct range for the statement, check the SQL statement.

为参数 iPar 指定的值小于一个或大于数据源支持的最大参数。若要验证该值在语句的正确范围内，请检查 SQL 语句。

Either the ipar value was less than 1, or the ipar value exceeded the maximum number of parameters that the data source supports. Set ipar to a valid value.

或者 iPar 值小于1，或者 ipar 值超过数据源支持的最大参数。将 iPar 设置为有效值。

-11075 Invalid scale value.

The value that the argument ibScale specifies is outside the range of values supported by the data source for a column of the SQL data type that the fSqlType argument specifies. For a list of supported values for the column type that fSqlType specifies, check the GBase 8s CLI Programmer's Manual.

参数 ibScale 指定的值超出了数据源为 fSqlType 参数指定的 SQL 数据类型的列所支持的值范围。有关 fSqlType 指定的列类型的受支持值列表，请检查 GBase 8s CLI 程序员手册。

This GBase 8s CLI error code is the same as SQLSTATE value S1094. The following function can return this error code: SQLBindParameter().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1094相同。以下函数可以返回此错误代码：SQLBindParameters()。

The ibScale value was invalid for the GBase 8s CLI SQL data type (fSqlType)argument. Set ibScale to a valid value.

ibScale 值对于 GBase 8s CLI SQL 数据类型（fSqlType）参数无效。将 ibScale 设置为有效值。

-11076 Function type out of range.

This GBase 8s CLI error code is the same as SQLSTATE value S1095. The following function can return this error code: SQLGetFunctions().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1095 相同。以下函数可以返回此错误代码：SQLGetFunctions()。

An invalid fFunction value is specified. For a list of valid values for the fFunction parameter, check the GBase 8s CLI Programmer's Manual.

指定了一个无效的 fFunction 值。有关 fFunction 参数的有效值列表，请查看 GBase 8s CLI 程序员手册。

-11077 Information type out of range.

This GBase 8s CLI error code is the same as SQLSTATE value S1096. The following function can return this error code: SQLGetInfo().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1096 相同。以下函数可以返回此错误代码：SQLGetInfo()。

The value specified for the argument fOption is in the block of numbers reserved for CLI information types but is not valid for the version of ODBC that the driver supports. For a list of supported features for your driver version, check the GBase 8s CLI Programmer's Manual.

为参数 fOption 指定的值位于为 CLI 信息类型保留的数字块中，但对于驱动程序支持的ODBC 版本无效。要获得驱动程序版本所支持的特性列表，请查看 GBase 8s CLI 程序员手册。

-11078 Column type out of range.

This GBase 8s CLI error code is the same as SQLSTATE value S1097. The following function can return this error code: SQLSpecialColumns().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1097 相同。以下函数可以返回此错误代码：SQLSpecialColumns()。

An invalid fColType value is specified. For a list of valid values for the fColType parameter, check the GBase 8s CLI Programmer's Manual.

指定无效的 fColType 值。有关 fColType 参数的有效值列表，请查看 GBase 8s CLI程序员手册。

-11079 Scope type out of range.

This GBase 8s CLI error code is the same as SQLSTATE value S1098. The following function can return this error code: SQLSpecialColumns().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1098 相同。以下函数可以返回此错误代码：SQLSpecialColumns()。

An invalid fScope value is specified. For a list of valid values for the fScope parameter, check the GBase 8s CLI Programmer's Manual.

指定了无效的 fScope 值。有关 fScope 参数的有效值列表，请查看 GBase 8s CLI 程序员手册。

-11080 Nullable type out of range.

This GBase 8s CLI error code is the same as SQLSTATE value S1099. The following function can return this error code: SQLSpecialColumns().

此 GBase 8s CLI错误代码与 SQLSTATE 值 S1099相同。以下函数可以返回此错误代码：SQLSpecialColumns()。

An invalid fNullable value is specified. For a list of valid values for the fNullable parameter, check the GBase 8s CLI Programmer's Manual.

指定无效的 fNullable 值。有关 fNullable 参数的有效值列表，请查看 GBase 8s CLI程序员手册。

-11081 Uniqueness option type out of range.

This GBase 8s CLI error code is the same as SQLSTATE value S1100. The following function can return this error code: SQLStatistics().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1100 相同。以下函数可以返回此错误代码：SQLStatistics()。

An invalid fUnique value is specified. For a list of valid values for the fUnique parameter, check the GBase 8s CLI Programmer's Manual.

指定了无效的 fUnique 值。有关 fUnique 参数的有效值列表，请查看 GBase 8s CLI程序员手册。

-11082 Accuracy option type out of range.

This GBase 8s CLI error code is the same as SQLSTATE value S1101. The following function can return this error code: SQLStatistics().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1101 相同。以下函数可以返回此错误代码：SQLStatistics()。

An invalid fAccuracy value is specified. For a list of valid values for the fAccuracy parameter, check the GBase 8s CLI Programmer's Manual.

指定了无效的 fAccuracy 值。有关 fAccuracy 参数的有效值列表，请查看 GBase 8s CLI程序员手册。

-11083 Direction option out of range.

This GBase 8s CLI error code is the same as SQLSTATE value S1103. The following functions can return this error code: SQLDataSources() and SQLDrivers().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1103 相同。以下函数可以返回此错误代码：SQLDataSources() 和 SQLDRivers()。

The value specified for argument fDirection is not equal to zero. For a list of valid values for the fDirection parameter, check the GBase 8s CLI Programmer's Manual.

为参数 fDirections 指定的值不等于零。有关 fDirection 参数的有效值列表，请查看GBase 8s CLI 程序员手册。

-11084 Invalid precision value.

This GBase 8s CLI error code is the same as SQLSTATE value S1104. The following function can return this error code: SQLBindParameter().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1104 相同。以下函数可以返回此错误代码：SQLBindParameter()。

The value specified for the argument cbColDef is outside the range of values supported by the data source for a column of the SQL data type that the fSqlType argument specifies. For a list of valid values for the column type that the fSqlType argument specifies, check the GBase 8s CLI Programmer's Manual.

为参数 cbColDef 指定的值超出了 fSqlType 参数指定的 SQL 数据类型列的数据源支持的值范围。有关 fSqlType 参数指定的列类型的有效值列表，请检查 GBase 8s CLI 程序员手册。

-11085 Invalid parameter type.

This GBase 8s CLI error code is the same as SQLSTATE value S1105. The following function can return this error code: SQLBindParameter().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1105 相同。以下函数可以返回此错误代码：SQLBindParameter()。

The value specified for the argument fParamType is invalid. For a list of valid values for the fParamType parameter, check the GBase 8s CLI Programmer's Manual.

为参数 fParamType 指定的值无效。有关 fParamType 参数的有效值列表，请查看 GBase 8s CLI程序员手册。

One of the following problems occurred: (1) The fParamType argument was not a valid parameter type, or (2) fParamType was SQL_PARAM_OUTPUT and the parameter is not an output parameter, or (3) fParamType was SQL_PARAM_INPUT and the parameter is an output parameter. Set fParamType to a valid value that corresponds to the type of parameter.

出现以下问题之一：(1)fParamType 参数不是有效的参数类型，或者(2) fParamType 是SQL_PARAM_OUTPUT，而该参数不是输出参数，或者(3) fParamType 是SQL_PARAM_INPUT，参数是输出参数。将 fParamType 设置为与参数类型相对应的有效值。

-11086 Fetch type out of range.

This GBase 8s CLI error code is the same as SQLSTATE value S1106. The following function can return this error code: SQLExtendedFetch().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1106 相同。以下函数可以返回此错误代码：SQLExtendedFetch()。

The value specified for the argument fFetchType is invalid. For a list of valid values for the fFetchType parameter, check the GBase 8s CLI Programmer's Manual.

为参数 fFetchType 指定的值无效。有关 fFetchType 参数的有效值列表，请检查 GBase 8s CLI 程序员手册。

One of the following problems occurred: (1) The fFetchType argument was not a valid fetch type, or (2) SQL_CURSOR_TYPE was SQL_CURSOR_FORWARD_ONLY but fFetchType was not SQL_FETCH_NEXT. Set fFetchType to a valid value that corresponds to the cursor type.

发生以下问题之一：(1) fFetchType 参数不是有效的提取类型，或者(2)SQL_CURSOR_TYPE 是 SQL_CURSOR_FORWARD_ONLY，但 fFetchType 不是SQL_FETCH_NEXT。

将 fFetchType 设置为对应于光标类型的有效值。

-11087 Row value out of range.

This GBase 8s CLI error code is the same as SQLSTATE value S1107. The following function can return this error code: SQLExtendedFetch().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1107 相同。以下函数可以返回此错误代码：SQLExtendedFetch()。

SQL_CURSOR_TYPE was SQL_CURSOR_KEYSET_DRIVEN but the SQL_KEYSET_SIZE value was greater than 0 and less than the SQL_ROWSET_SIZE value. Set SQL_KEYSET_SIZE to a value that is valid for the SQL_CURSOR_TYPE value.

SQL_CURSOR_TYPE 是 SQL_CURSOR_KEKSET_DRIVEN，但 SQL_KEYSET_SIZE 值大于 0，小于SQL_ROWSET_SIZE 值。将 SQL_KEYSET_SIZE 设置为对 SQL_CURSOR_TYPE 值有效的值。

-11088 Concurrency option out of range.

The value specified for the argument fConcurrency is not equal to SQL_CONCUR_READ_ONLY, SQL_CONCUR_LOCK, SQL_CONCUR_ROWVER, or SQL_CONCUR_VALUES. Check that the SQL statement uses one of the listed accepted values for the fConcurrency parameter.

为参数 fConcurrency 指定的值不等于 SQL_CONCUR_READ_ONLY、SQL_CONCUR_LOCK、SQL_CONCUR_ROWVER 或 SQL_CONCUR_VALUES。检查 SQL 语句是否使用 fConcurrency 参数的列表接受值之一。

-11089 Invalid cursor position.

This GBase 8s CLI error code is the same as SQLSTATE value S1109. The following functions can return this error code: SQLExecute(), SQLExecDirect(),SQLGetData(), and SQLGetStmtOption().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1109 相同。以下函数可以返回此错误代码：SQLExecute()、SQLExecDirect()、SQLGetData() 和 SQLGetStmtOption()。

The cursor is on a row that was deleted or that has an error. Do not try to perform an action on a row that was deleted or that has an error.

游标位于已删除或有错误的行上。不要尝试对已删除或有错误的行执行操作。

-11090 Invalid driver completion.

This GBase 8s CLI error code is the same as SQLSTATE value S1110. The following function can return this error code: SQLDriverConnect().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1110 相同。以下函数可以返回此错误代码：SQLDRiverConnect()。

The value specified for the fDriverCompletion argument is not equal to SQL_DRIVER_PROMPT, SQL_DRIVER_COMPLETE, SQL_DRIVER_COMPLETE_REQUIRED,or SQL_DRIVER_NOPROMPT. Check that the SQL statement uses one of the listed accepted values for the fDriverCompletion parameter.

为 fDriverCompletion 参数指定的值不等于 SQL_DRIVER_PROMPT、SQL_DRIVER_COMPLETE、SQL_DRIVER_COMPLETE_REQUIRED 或 SQL_DRIVER_NOPROMPT。检查SQL 语句是否使用 fDriverCompletion 参数中列出的接受值之一。

-11091 Invalid bookmark value This GBase 8s ODBC error code is the same as SQLSTATE value HY111(ODBC2.x state is S1111). The following functions can return this error code: SQLExtendedFetch and SQLFetchScroll.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 HY111 相同（ODBC2.x 状态为 S1111）。以下函数可以返回此错误代码：SQLExtendedFetch 和 SQLFetchScroll。

For SQLExtendedFetch, the argument FetchOrientation was SQL_FETCH_BOOKMARK, and the bookmark specified in the FetchOffset argument was not valid.

对于 SQLExtendedFetch，参数 FetchOrition 为 SQL_FETCH_BOOKMARK，而在FetchOffset 参数中指定的书签无效。

For SQLFetchScroll, the argument FetchOrientation was SQL_FETCH_BOOKMARK,and the bookmark pointed to by the value in the SQL_ATTR_FETCH_BOOKMARK_PTR statement attribute was not valid or was a null pointer.

对于 SQLFetchScroll，参数 FetchOrientation 为SQL_FETCH_BOOKMARK，并且由SQL_ATTR_FETCH_BOOKMARK_PTR 语句属性中的值指向的书签无效或为空指针。

-11092 Driver not capable.

The driver or data source does not support the function requested. For a list of supported driver functions, check the GBase 8s CLI Programmer's Manual.

驱动程序或数据源不支持所请求的函数。有关支持的驱动程序函数的列表，请查看 GBase 8s CLI 程序员手册。

This GBase 8s CLI error code is the same as SQLSTATE value S1C00. The following functions can return this error code:SQLBindCol(), SQLBindParameter(), SQLColAttributes(), SQLColumnPrivileges(),SQLColumns(), SQLExecDirect(), SQLExecute(), SQLExtendedFetch(), SQLFetch(),SQLForeignKeys(), SQLGetConnectOption(), SQLGetData(), SQLGetInfo(),SQLGetStmtOption(), SQLGetTypeInfo(), SQLPrepare(), SQLPrimaryKeys(),SQLProcedureColumns(), SQLProcedures(), SQLSetConnectOption(),SQLSetScrollOptions(), SQLSetStmtOption(), SQLSpecialColumns(),SQLStatistics(), SQLTablePrivileges(), SQLTables(), and SQLTransact().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1C00 相同。以下函数可以返回此错误代码：SQLBindCol()、SQLBindParameter()、SQLColAttributes()、 SQLColumnPrivileges()、SQLColumns()、 SQLExecDirect()、SQLExecute()、SQLExtendedFetch()、SQLFetch()、SQLForeignKeys()、SQLGetConnectOption()、SQLGetData()、SQLGetInfo()、SQLGetStmtOption()、SQLGetTypeInfo()、SQLPrepare()、SQLPrimaryKeys()、SQLProcedureColumns()、SQLProcedures()、SQLSetConnectOption()、SQLSetScrollOptions()、SQLSetStmtOption()、SQLSpecialColumns()、SQLStatistics()、SQLTablePrivileges()、SQLTables() 和 SQLTransact()。

For SQLBindCol(), the data source does not support the GBase 8s CLI C data type (fCType) argument, or the icol value was 0. Set the GBase 8s CLI C data type to a value that the data source supports and set icol to a valid value.

对于 SQLBindCol()，数据源不支持 GBase 8s CLIC 数据类型（fCType）参数，或者icol 值为 0。将 GBase 8s CLIC 数据类型设置为数据源支持的值，并将 icol 设置为有效值。

For SQLBindParameter(), SQLExtendedFetch(), SQLFetch(), and SQLGetData(), one of the following problems occurred: (1) It is not possible to convert the result data (the data value associated with the GBase 8s CLI C data type(fCType) argument) to the data type of the parameter (the data value associated with the GBase 8s CLI SQL data type (fSqlType) argument), or(2) The data source does not support the GBase 8s CLI SQL data type or(3) The data source does not support the fetch type. Set the GBase 8s CLI C and SQL data types to values that make it possible to convert the result data to the data type of the parameter and set the GBase 8s CLI SQL data type and fetch type to values that the data source supports.

对于 SQLBindParameter()、SQLExtendedFetch()、SQLFetch() 和 SQLGetData()，出现下列问题之一：(1)无法将结果数据（与 GBase 8s CLIC 数据类型关联的数据值（fCType）参数）转换为参数的数据类型（与 GBase 8s CLI SQL 数据类（fSqlType）参数关联的数据值），或者(2)数据源不支持 GBase 8s CLI SQL 数据类型或(3)数据源不支持获取类型。将 GBase 8s CLIC 和 SQL 数据类型设置为可以将结果数据转换为参数的数据类型的值，并将 GBase 8s CLI SQL 数据类型和 FETCH 类型设置为数据源支持的值。

For SQLColAttributes(), the fDescType value is not a valid descriptor type.

Use a valid value for fDescType.

对于 SQLColAttributes()，fDescType 值不是有效的描述符类型。对 fescType 使用有效值。

For SQLColumnPrivileges(), SQLColumns(), SQLExecDirect(), SQLExecute(),SQLForeignKeys(), SQLPrepare(), SQLPrimaryKeys(), SQLProcedureColumns(),SQLProcedures(), SQLSpecialColumns(), SQLStatistics(), SQLTables(), and SQLTablePrivileges(), one of the following problems occurred: (1) You specified a qualifier for the procedure or table, but the data source does not support qualifiers, or (2) You specified an owner for the procedure or table,but the data source does not support owners, or (3) You specified a string search pattern for the procedure owner, procedure name, or column name, but the data source does not support search patterns for that argument, or (4) The combination of the SQL_CONCURRENCY value and the SQL_CURSOR_TYPE value is invalid. Do not set a qualifier, owner, or search pattern for a data source that does not support them and set the concurrency and cursor type values so that the combination of the values is valid.

对于 SQLColumnPrivileges()、SQLColumns()、SQLExecDirect()、SQLExecute()、SQLForeignKeys()、SQLPrepare()、SQLPrimaryKeys()、SQLProcedureColumns()、SQLProcedures()、SQLSpecialColumns()、SQLStatistics()、SQLTables() 和SQLTablePrivileges(), 发生以下问题之一：（1）指定存储过程或表的限定符，但数据源不支持限定符，或（2）为存储过程或表指定了所有者，但数据源不支持所有者，或(3)为存储过程所有者、过程名称或列名指定了字符串搜索模式，但数据源不支持该参数的搜索模式，或(4) SQL_CONCURRENCY 值和 SQL_CURSOR_TYPE 值的组合无效。不要为不支持的数据源设置限定符、所有者或搜索模式，并设置并发和游标类型值，以使值的组合有效。

For SQLGetConnectOption(), SQLGetStmtOption(), SQLSetConnectOption(), and SQLSetStmtOption(), the fOption value is not a valid option value. Set fOption to a valid value.

对于 SQLGetConnectOption()、SQLGetStmtOption()、SQLSetConnectOption() 和SQLSetStmtOption()，fOption 值不是有效的选项值。将 fOption 设置为有效值。

Additionally for SQLGetData(), the data source does not support the use of SQLGetData() with multiple rows in SQLExtendedFetch(), or the icol value was 0.

Use SQLGetData() with multiple rows in SQLExtendedFetch() only if the data source supports this task and do not set icol to 0.

另外，对于 SQLGetData()，数据源不支持使用 SQLExtendedFetch() 中多行的SQLGetData()，或者 icol 值为 0。只有当数据源支持此任务且不将 icol 设置为 0时，才可在 SQLExtendedFetch() 中使用带有多行的 SQLGetData()。

For SQLGetInfo(), the fInfoType value was not a valid information type. Set fInfoType to a valid value.

对于 SQLGetInfo()，fInfoType 值不是有效的信息类型。将 fInfoType 设置为有效值。

For SQLGetTypeInfo(), the data source does not support the GBase 8s CLI SQL data type (fSqlType) argument), or the combination of the SQL_CONCURRENCY value and the SQL_CURSOR_TYPE value is invalid. Set the GBase 8s CLI SQL data type to a value that the data source supports, and set the concurrency and cursor type values so that the combination of the values is valid.

对于 SQLGetTypeInfo()，数据源不支持 GBase 8s CLI SQL 数据类型(fFSqlType)参数，也不支持 SQL_CONCURRENCY 值和 SQL_CURSOR_TYPE 值的组合。将 GBase 8s CLI SQL 数据类型设置为数据源支持的值，并设置并发和游标类型值，以便这些值的组合是有效的。

For SQLTransact(), the data source does not support the ROLLBACK operation. Do not set fType to SQL_ROLLBACK.

对于 SQLTransact()，数据源不支持回滚操作。不要将 fType 设置为 SQL_ROLLBACK。

-11094 Timeout expired.

The time-out period expired before the connection to the data source completed. The time-out period is set through SQL_SetConnectionOption,SQL_LOGIN_TIMEOUT.

在与数据源的连接完成之前，超时时间已过期。超时时间是通过SQL_SetConnectionOption，SQL_LOGIN_TIMOUT 设置的。

This GBase 8s CLI error code is the same as SQLSTATE value S1T00. The following functions can return this error code: SQLBrowseConnect(),SQLColAttributes(), SQLColumnPrivileges(), SQLColumns(), SQLConnect(),SQLDescribeCol(), SQLDriverConnect(), SQLExecDirect(), SQLExecute(),SQLExtendedFetch(), SQLFetch(), SQLForeignKeys(), SQLGetData(),SQLGetInfo(), SQLGetTypeInfo(), SQLMoreResults(), SQLNumParams(),SQLNumResultCols(), SQLParamData(), SQLPrepare(), SQLPrimaryKeys(),SQLProcedureColumns(), SQLProcedures(), SQLPutData(), SQLSpecialColumns(),SQLStatistics(), SQLTablePrivileges(), and SQLTables().

此 GBase 8s CLI 错误代码与 SQLSTATE 值 S1T00 相同。以下函数可以返回此错误代码：SQLBrowseConnect()、SQLColAttributes()、SQLColumnPrivileges()、SQLColumns()、SQLConnect()、SQLDescribeCol()、SQLDriverConnect()、SQLExecDirect()、SQLExecute()、SQLExtendedFetch()、SQLFetch()、SQLForeignKeys()、SQLGetData()、SQLGetInfo()、SQLGetTypeInfo()、SQLMoreResults()、SQLNumParams()、SQLNumResultCols()、SQLParamData()、SQLPrepare()、SQLPrimaryKeys()、SQLProcedureColumns()、SQLProcedures()、 SQLPutData()、SQLSpecialColumns()、SQLStatistics()、SQLTablePrivileges() 和 SQLTables()。

For SQLBrowseConnect(), SQLConnect(), and SQLDriverConnect(), the time-out period expired before the function could complete the connection to the data source. Call SQLSetConnectOption() to change SQL_LOGIN_TIMEOUT.

对于 SQLBrowseConnect()、SQLConnect() 和 SQLDRiverConnect()，超时时间在函数完成到数据源的连接之前就已经过期。调用 SQLSetConnectOption() 来更改SQL_LOGIN_TIMEOUT。

For all other functions, the time-out period expired before the data source could process the information and, if necessary, return a result set or requested information. Call SQLSetConnectOption() to change SQL_QUERY_TIMEOUT.

对于所有其他函数，在数据源处理信息之前超时时间已经过期，并在必要时返回结果集或请求的信息。调用 SQLSetConnectOption()来更改 SQL_QUERY_TIMEOUT。

-11095 Invalid attribute value This GBase 8s ODBC error code is the same as SQLSTATE value. The following functions can return this error code: SQLSetConnectAttr,SQLSetEnvAttr, and SQLSetStmtAttr.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值相同。以下函数可以返回此错误代码：SQLSetConnectAttr、SQLSetEnvAttr 和 SQLSetStmtAttr。

For SQLSetConnectAttr, given the specified Attribute value, an invalid value was specified in ValuePtr. (The Driver Manager returns this SQLSTATE only for connection and statement attributes that accept a discrete set of values, such as SQL_ATTR_ACCESS_MODE or SQL_ATTR_ASYNC_ENABLE. For all other connection and statement attributes,the driver must verify the value specified in ValuePtr.) The Attribute argument was SQL_ATTR_TRACEFILE or SQL_ATTR_TRANSLATE_LIB, and ValuePtr was an empty string.

对于 SQLSetConnectAttr ，给定指定的属性值，在 ValuePtr 中指定无效值。（驱动程序管理器只对接受离散值集的连接和语句属性返回此 SQLSTATE，如SQL_ATTR_ACCESS_MODE 或 SQL_ATTR_ASYNC_ENABLE。对于所有其他连接和语句属性，驱动程序必须验证 ValuePtr 中指定的值。）属性参数是 SQL_ATTR_TRACEFILE 或SQL_ATTR_TRANSLATE_LIB，而 ValuePtr 是空字符串。

For SQLSetEnvAttr, given the specified Attribute value, an invalid value was specified in ValuePtr.

对于 SQLSetEnvAttr，给定指定的属性值，在 ValuePtr 中指定无效值。

For SQLSetStmtAttr, given the specified Attribute value, an invalid value was specified in ValuePtr. (The Driver Manager returns this SQLSTATE only for connection and statement attributes that accept a discrete set of values, such as SQL_ATTR_ACCESS_MODE or SQL_ ATTR_ASYNC_ENABLE. For all other connection and statement attributes, the driver must verify the value specified in ValuePtr.) The Attribute argument was SQL_ATTR_APP_ROW_DESC or SQL_ATTR_APP_PARAM_DESC, and ValuePtr was an explicitly allocated descriptor handle that is not on the same connection as the StatementHandle argument.

对于 SQLSetStmtAttr ，给定指定的属性值，在 ValuePtr 中指定无效值。（驱动程序管理器只对接受离散值集的连接和语句属性返回此 SQLSTATE，如SQL_ATTR_ACCESS_MODE 或SQL_ATTR_ASYNC_ENABLE。对于所有其他连接和语句属性，驱动程序必须验证 ValuePtr指定的值。)属性参数是 SQL_ATTR_APP_ROW_DESC 或 SQL_ATTR_APP_PARAM_DESC，而ValuePtr 是显式分配的描述符句柄，与 StatementHandle 参数的连接不同。

-11097 Optional feature not implemented.

This GBase 8s ODBC error code is the same as SQLSTATE value HYC00. The following functions can return this error code: SQLBindCol,SQLBindParameter, SQLBulkOperations, SQLColAttribute,SQLColumnPrivileges, SQLColumns, SQLDriverConnect, SQLEndTran,SQLExecDirect, SQLExecute, SQLExtendedFetch, SQLFetch, SQLFetchScroll,SQLForeignKeys, SQLGetConnectAttr, SQLGetData, SQLGetEnvAttr, SQLGetInfo,SQLGetStmtAttr, SQLGetTypeInfo, SQLParamData, SQLPrepare, SQLPrimaryKeys,SQLProcedureColumns, SQLProcedures, SQLSetConnectAttr, SQLSetEnvAttr,SQLSetPos, SQLSetStmtAttr, SQLSpecialColumns, SQLStatistics,SQLTablePrivileges, and SQLTables.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 HYC00 相同。以下函数可以返回此错误代码：SQLBindCol、SQLBindParameter、SQLBulkOperations、SQLColAttribute、SQLColumnPrivileges、SQLColumns、SQLDriverConnect、SQLEndTran、SQLExecDirect、SQLExecute、SQLExtendedFetch、SQLFetch、SQLFetchScroll、SQLForeignKeys、SQLGetConnectAttr、SQLGetData、SQLGetEnvAttr、SQLGetInfo、SQLGetStmtAttr、SQLGetTypeInfo、SQLParamData、SQLPrepare、 SQLPrimaryKeys、SQLProcedureColumns、SQLProcedures、SQLSetConnectAttr、SQLSetEnvAttr、SQLSetPos、SQLSetStmtAttr、SQLSpecialColumns、SQLStatistics、SQLTablePrivileges 和 SQLTables。

The value specified for the argument Attribute was a valid ODBC environment attribute for the version of ODBC supported by the driver,but the attribute was not supported by the driver. For more detailed information, see the ODBC Reference Manual.

为参数属性指定的值是驱动程序支持的 ODBC 版本的有效 ODBC 环境属性，但驱动程序不支持该属性。有关详细信息，请参阅 ODBC 参考手册。

-11099 Invalid name of File DSN This GBase 8s ODBC error code is the same as SQLSTATE value IM014. The following function can return this error code: SQLDriverConnect.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 IM014 相同。以下函数可以返回此错误代码：SQLDRiverConnect。

For SQLDriverConnect, the string in InConnectionString contained a FILEDSN keyword, but the name of the .DSN file was invalid.

对于 SQLDRiverConnect ，InConnectionString 中的字符串包含一个 FILEDSN 关键字，但 .DSN 文件的名称无效。

-11103 Invalid descriptor index This GBase 8s ODBC error code is the same as SQLSTATE value 07009. The following functions can return this error code: SQLBindCol,SQLBindParameter, SQLBulkOperations, SQLColAttribute, SQLDescribeCol,SQLFetch, SQLFetchScroll, SQLGetData, SQLGetDescField, SQLGetDescRec,SQLSetDescField, SQLSetDescRec, and SQLSetPos.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 07009 相同。以下函数可以返回此错误代码：SQLBindCol、SQLBindParameter、SQLBulkOperations、SQLColAttribute、SQLDescribeCol、SQLFetch、SQLFetchScroll、SQLGetData、SQLGetDescField、SQLGetDescRec、SQLSetDescField、SQLSetDescRec 和 SQLSetPos。

For SQLBindCol, SQLBindParameter, SQLColAttribute, SQLGetData, and SQLDescribeCol, the value specified for column exceeded the maximum number of columns in the result set.

对于 SQLBindCol、SQLBindParameter、SQLColAttribute、SQLGetData 和SQLDescribeCol ，为列指定的值超过结果集中的最大列数。

For SQLBulkOperations, the argument Operation was SQL_ADD, and a column was bound with a column number greater than the number of columns in the result set.

对于 SQLBulkOperations ，参数操作是 SQL_ADD，并且一个列被绑定的列号大于结果集中的列数。

For SQLFetch, the driver was an ODBC 2.x driver that does not support SQLExtendedFetch, and a column number specified in the binding for a column was 0.

对于 SQLFetch ，驱动程序是一个 ODBC 2.x 驱动程序，它不支持 SQLExtendedFetch，并且在列绑定中指定的列号为 0。

For SQLFetchScroll, Column 0 was bound, and the SQL_ATTR_USE_BOOKMARKS statement attribute was set to SQL_UB_OFF.

对于 SQLFetchScroll ，第 0 列被绑定，SQL_ATTR_USE_BOOKMARKS 语句属性被设置为 SQL_UB_OFF。

For SQLSetDescField and SQLGetDescField, the RecNumber argument was equal to 0, the SQL_ATTR_USE_BOOKMARK statement attribute was SQL_UB_OFF, and the DescriptorHandle argument was an IRD handle. (This error can be returned for an explicitly allocated descriptor only if the descriptor is associated with a statement handle.) The FieldIdentifier argument was a record field, the RecNumber argument was 0, and the DescriptorHandle argument was an IPD handle. The RecNumber argument was less than 0.

对于 SQLSetDescField 和 SQLGetDescField ，RecNumber 参数等于 0，SQL_ATTR_USE_BOOKMARK 语句属性为 SQL_UB_off，DescriptorHandle 参数是 IRD 句柄。(只有当描述符与语句句柄相关联时，才能返回显式分配描述符的错误。)FieldIdentifier 参数是一个记录字段，RecNumber 参数是 0，DescriptorHandle 参数是一个 IPD 句柄。RecNumber 参数小于0。

For SQLSetDescRec and SQLGetDescRec, the FieldIdentifier argument was a record field, the RecNumber argument was set to 0, and the DescriptorHandle argument was an IPD handle. The RecNumber argument was set to 0, the SQL_ATTR_USE_BOOKMARKS statement attribute was set to SQL_UB_OFF, and the DescriptorHandle argument was an IRD handle.(DM) The RecNumber argument was less than 0.

对于 SQLSetDescRec 和 SQLGetDescRec，FieldIdentifier 参数是记录字段，RecNumber参数设置为 0，DescriptorHandle 参数是 IPD 句柄。RecNumber 参数设置为 0，SQL_ATTR_USE_BOOKMARKS 语句属性设置为 SQL_UB_OFF，DescriptorHandle 参数是 IRD句柄。(DM) RecNumber 参数小于 0。

For SQLSetPos, the argument Operation was SQL_REFRESH or SQL_UPDATE, and a column was bound with a column number greater than the number of columns in the result set.

对于 SQLSetPos ，参数操作是 SQL_REFRESH 或 SQL_UPDATE，并且一个列被绑定的列号大于结果集中的列数。

-11104 Invalid datetime format This GBase 8s ODBC error code is the same as SQLSTATE value 22007. The following functions can return this error code: SQLBulkOperations,SQLExecDirect, SQLExecute, SQLExtendedFetch, SQLFetch, SQLFetchScroll,SQLGetData, SQLPutData, and SQLSetPos.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 22007 相同。以下函数可以返回此错误代码：SQLBulkOperations、SQLExecDirect、SQLExecute、SQLExtendedFetch、SQLFetch、SQLFetchScroll、SQLGetData、SQLPutData 和 SQLSetPos。

For SQLBulkOperations, the Operation argument was SQL_ADD, and the assignment of a date or timestamp value to a column in the result set caused the year, month, or day field to be out of range.

对于 SQLBulkOperations ，操作参数为 SQL_ADD，将日期或时间戳值分配给结果集中的列会导致年份、月份或日字段超出范围。

For SQLExecDirect and SQLExecute, StatementText contained an SQL statement that contained a date, time, or timestamp structure as a bound parameter, and the parameter was, respectively, an invalid date,time, or timestamp.

对于 SQLExecDirect 和 SQLExecute ，StatementText 包含日期、时间或时间戳结构作为绑定参数的 SQL 语句，并且该参数分别是无效的日期、时间或时间戳。

For SQLFetch, SQLExtendedFetch, SQLGetData, and SQLFetchScroll, a character column in the result set was bound to a date, time, or timestamp C structure, and a value in the column was, respectively, an invalid date, time, or timestamp.

对于 SQLFetch、SQLExtendedFetch、SQLGetData 和 SQLFetchScroll ，结果集中的字符列绑定到日期、时间或时间戳C结构，列中的值分别为无效日期、时间或时间戳。

For SQLPutData, an input/output or output parameter was bound to a date,time, or timestamp C structure, and a value in the returned parameter was, respectively, an invalid date, time, or timestamp. (Function returns SQL_SUCCESS_WITH_INFO.)对于 SQLPutData ，输入/输出或输出参数绑定到日期、时间或时间戳C结构，返回参数中的值分别为无效日期、时间或时间戳。(函数返回 SQL_SUCCESS_WITH_INFO。)For SQLSetPos, the argument Operation was SQL_UPDATE, and the assignment of a date or timestamp value to a column in the result set caused the year, month, or day field to be out of range. The argument Operation was SQL_REFRESH, and returning the date or timestamp value for one or more bound columns would have caused the year, month, or day field to be out of range.

对于 SQLSetPos ，参数操作是 SQL_UPDATE，将日期或时间戳值分配给结果集中的列会导致年份、月份或日字段超出范围。参数操作是 SQL_REFRESH，返回一个或多个绑定列的日期或时间戳值会导致年份、月份或日字段超出范围。

-11105 Interval field overflow This GBase 8s ODBC error code is the same as SQLSTATE value 22015. The following functions can return this error code: SQLBulkOperations,SQLExecDirect, SQLExecute, SQLExtendedFetch, SQLFetch, SQLFetchScroll,SQLGetData, SQLPutData, and SQLSetPos.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 22015 相同。以下函数可以返回此错误代码：SQLBulkOperations、SQLExecDirect、SQLExecute、SQLExtendedFetch、SQLFetch、SQLFetchScroll、SQLGetData、SQLPutData 和 SQLSetPos。

For SQLBulkOperations, the Operation argument was SQL_ADD or SQL_UPDATE_BY_BOOKMARK, and the assignment of a date or timestamp value to a column in the result set caused the year, month, or day field to be out of range.

对于 SQLBulkOperations ，操作参数为SQL_ADD 或 SQL_UPDATE_BY_BOOKMARK，将日期或时间戳值分配给结果集中的列将导致年份、月份或日字段超出范围。

For SQLExecute and SQLExecDirect, StatementText contained an exact numeric or interval parameter that when converted to an interval SQL data type caused a loss of significant digits. *StatementText contained an interval parameter with more than one field that when converted to a numeric data type in a column had no representation in the numeric data type. StatementText contained parameter data that was assigned to an interval SQL type, and there was no representation of the value of the C type in the interval SQL type. Assigning an input/output or output parameter that was an exact numeric or interval SQL type to an interval C type caused a loss of significant digits. When an input/output or output parameter was assigned to an interval C structure, there was no representation of the data in the interval data structure.

对于 SQLExecute 和 SQLExecDirect ，StatementText 包含一个确切的数字或间隔参数，转换为间隔 SQL 数据类型时会导致有效数字的丢失。*StatementText 包含一个包含多个字段的 Interval 参数，当在列中转换为数字数据类型时，该参数在数值数据类型中没有表示。StatementText 包含分配给间隔 SQL 类型的参数数据，并且在 Interval SQL类型中没有 C 类型值的表示形式。将确切的数字或间隔 SQL 类型的输入/输出或输出参数分配给区间 C 类型会导致重大数字的丢失。当将输入/输出或输出参数分配给区间 C结构时，区间数据结构中没有数据的表示。

SQLExtendedFetch, SQLFetch, SQLGetData, and SQLFetchScroll, assigning from an exact numeric or interval SQL type to an interval C type caused a loss of significant digits in the leading field. When data was fetched to an interval C type, there was no representation of the value of the SQL type in the interval C type.

SQLExtendedFetch、SQLFetch、SQLGetData 和 SQLFetchScroll 从精确的数字或间隔SQL 类型分配给区间 C 类型，导致前导字段中的有效数字丢失。当数据被取到区间 C 类型时，区间C 类型中没有 SQL 类型值的表示。

For SQLPutData, the data sent for an exact numeric or interval column or parameter to an interval SQL data type caused a loss of significant digits. Data was sent for an interval column or parameter with more than one field, was converted to a numeric data type, and had no representation in the numeric data type. The data sent for column or parameter data was assigned to an interval SQL type, and there was no representation of the value of the C type in the interval SQL type. The data sent for an exact numeric or interval C column or parameter to an interval C type caused a loss of significant digits. The data sent for column or parameter data was assigned to an interval C structure, and there was no representation of the data in the interval data structure.

对于 SQLPutData，发送给区间 SQL 数据类型的确切数字或间隔列或参数的数据会导致有效数字的丢失。为具有多个字段的间隔列或参数发送数据，将其转换为数字数据类型，并且在数值数据类型中没有表示形式。为列或参数数据发送的数据被分配给间隔 SQL 类型，并且在区间 SQL 类型中没有 C 类型值的表示形式。发送给区间 C 类型的精确数字或间隔 C 列或参数的数据会导致有效数字的丢失。发送给列或参数数据的数据被分配给区间 C 结构，并且在间隔数据结构中没有数据的表示。

For SQLSetPos, the Operation argument was SQL_UPDATE, and the assignment of an exact numeric or interval C type to an interval SQL data type caused a loss of significant digits. The Operation argument was SQL_UPDATE; when a value was assigned to an interval SQL type, there was no representation of the value of the C type in the interval SQL type.

The Operation argument was SQL_REFRESH, and assigning from an exact numeric or interval SQL type to an interval C type caused a loss of significant digits in the leading field. The Operation argument was SQL_REFRESH; when a value was assigned to an interval C type, there was no representation of the value of the SQL type in the interval C type.

对于 SQLSetPos ，发送给区间 SQL 数据类型的确切数字或间隔列或参数的数据会导致有效数字的丢失。为具有多个字段的间隔列或参数发送数据，将其转换为数字数据类型，并且在数值数据类型中没有表示形式。为列或参数数据发送的数据被分配给间隔 SQL 类型，并且在区间 SQL 类型中没有 C 类型值的表示形式。发送给区间 C 类型的精确数字或间隔C列或参数的数据会导致有效数字的丢失。发送给列或参数数据的数据被分配给区间 C 结构，并且在间隔数据结构中没有数据的表示。

-11106 Invalid character value for cast specification This GBase 8s ODBC error code is the same as SQLSTATE value 22018. The following functions can return this error code: SQLBulkOperations,SQLExecDirect, SQLExecute, SQLExtendedFetch, SQLFetch, SQLFetchScroll,SQLGetData, SQLPutData, and SQLSetPos.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 22018 相同。以下函数可以返回此错误代码：SQLBulkOperations、SQLExecDirect、SQLExecute、SQLExtendedFetch、SQLFetch、SQLFetchScroll、SQLGetData、SQLPutData 和 SQLSetPos 。

For SQLBulkOperations, the argument Operation was SQL_ADD; the SQL type was an exact or approximate numeric, a datetime, or an interval data type; the C type was SQL_C_CHAR; and the value in the column was not a valid literal of the bound SQL type.

对于 SQLBulkOperations，参数操作是 SQL_ADD；SQL 类型是精确或近似的数字、日期时间或间隔数据类型；C 类型是 SQL_C_CHAR；列中的值不是绑定 SQL 类型的有效文字。

For SQLExecute and SQLExecDirect, StatementText contained a C type that was an exact or approximate numeric, a datetime, or an interval data type; the SQL type of the column was a character data type; and the value in the column was not a valid literal of the bound C type. When an input/output or output parameter was returned, the SQL type was an exact or approximate numeric, a datetime, or an interval data type; the C type was SQL_C_CHAR; and the value in the column was not a valid literal of the bound SQL type.

对于 SQLExecute 和 SQLExecDirect，StatementText 包含精确或近似数字、日期时间或间隔数据类型的 C 类型；列的 SQL 类型是字符数据类型；列中的值不是绑定 C 类型的有效文字。当返回输入/输出或输出参数时，SQL 类型是精确或近似数字、日期时间或间隔数据类型；C 类型是 SQL_C_CHAR ；列中的值不是绑定 SQL 类型的有效文字。

For SQLExtendedFetch, SQLFetch, SQLFetchScroll, and SQLGetData, a character column in the result set was returned to a character C buffer,and the column contained a character for which there was no representation in the character set of the buffer. The C type was an exact or approximate numeric, a datetime, or an interval data type; the SQL type of the column was a character data type; and the value in the column was not a valid literal of the bound C type.

对于 SQLExtendedFetch、SQLFetch、SQLFetchScroll 和 SQLGetData，结果集中的字符列返回给字符 C 缓冲区，该列包含缓冲区字符集中没有表示的字符。C 类型是精确或近似数字、日期时间或间隔数据类型；列的 SQL 类型是字符数据类型；列中的值不是绑定C 类型的有效文字。

For SQLPutData, the C type was an exact or approximate numeric, a datetime, or an interval data type; the SQL type of the column was a character data type; and the value in the column or parameter was not a valid literal of the bound C type. The SQL type was an exact or approximate numeric, a datetime, or an interval data type; the C type was SQL_C_CHAR; and the value in the column or parameter was not a valid literal of the bound SQL type.

对于 SQLPutData，C 类型是精确或近似数字、日期时间或间隔数据类型；列的 SQL 类型是字符数据类型；列或参数中的值不是绑定 C 类型的有效文字。SQL 类型是精确或近似数字、日期时间或间隔数据类型；C 类型是 SQL_C_CHAR；列或参数中的值不是绑定 SQL类型的有效文字。

For SQLSetPos, the Operation argument was SQL_REFRESH; the C type was an exact or approximate numeric, a datetime, or an interval data type;the SQL type of the column was a character data type; and the value in the column was not a valid literal of the bound C type. The argument Operation was SQL_UPDATE; the SQL type was an exact or approximate numeric, a datetime, or an interval data type; the C type was SQL_C_CHAR;and the value in the column was not a valid literal of the bound SQL type.

对于 SQLSetPos，操作参数为 SQL_REFRESH；C 类型是精确或近似的数字、日期时间或间隔数据类型；列的 SQL 类型是字符数据类型；列中的值不是绑定 C 类型的有效文字。参数操作是 SQL_UPDATE；SQL 类型是精确或近似数字、日期时间或间隔数据类型；C 类型是 SQL_C_CHAR；列中的值不是绑定 SQL 类型的有效文字。

-11116 Invalid application buffer type This GBase 8s ODBC error code is the same as SQLSTATE value HY003. The following functions can return this error code: SQLBindCol,SQLBindParameter, and SQLGetData.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 HY003 相同。以下函数可以返回此错误代码：SQLBindCol、SQLBindParameter 和 SQLGetData。

For SQLBindCol and SQLGetData, the argument TargetType was neither a valid data type nor SQL_C_DEFAULT.

对于 SQLBindCol 和 SQLGetData，参数 TargetType 既不是有效的数据类型，也不是SQL_C_DEFAULT。

For SQLBindParameter, the value specified by the argument ValueType was not a valid C data type or SQL_C_DEFAULT.

对于 SQLBindParameter，参数 ValueType 指定的值不是有效的 C 数据类型或SQL_C_DEFAULT。

-11117 Associated statement is not prepared.

This GBase 8s ODBC error code is the same as SQLSTATE value HY007. The following functions can return this error code: SQLCopyDesc,SQLGetDescField, and SQLGetDescRec.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 HY007 相同。以下函数可以返回此错误代码：SQLCopyDesc、SQLGetDescField 和 SQLGetDescRec。

For SQLCopyDesc, SQLGetDescField, and SQLGetDescRec, DescriptorHandle was associated with a StatementHandle as an IRD, and the associated statement handle had not been prepared or executed.

对于 SQLCopyDesc、SQLGetDescField 和 SQLGetDescRec，DescriptorHandle 作为 IRD与 StatementHandle 相关联，并且关联的语句句柄尚未准备或执行。

-11118 Invalid use of null pointer This GBase 8s ODBC error code is the same as SQLSTATE value HY009. The following functions can return this error code: SQLAllocHandle,SQLBindParameter, SQLColumnPrivileges, SQLColumns, SQLExecDirect,SQLForeignKeys, SQLNativeSql, SQLPrepare, SQLPrimaryKeys,SQLProcedureColumns, SQLProcedures, SQLPutData, SQLSetConnectAttr,SQLSetCursorName, SQLSetEnvAttr, SQLSetStmtAttr, SQLSpecialColumns,SQLStatistics, SQLTablePrivileges, and SQLTables.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 HY009 相同。以下函数可以返回此错误代码：SQLAllocHandle、SQLBindParameter、SQLColumnPrivileges、SQLColumns、SQLExecDirect、SQLForeignKeys、SQLNativeSql、SQLPrepare、SQLPrimaryKeys、SQLProcedureColumns、SQLProcedures、SQLPutData、SQLSetConnectAttr、SQLSetCursorName、SQLSetEnvAttr、SQLSetStmtAttr、SQLSpecialColumns、SQLStatistics、SQLTablePrivileges 和 SQLTables。

For SQLAllocHandle, SQLExecDirect, SQLNativeSql, SQLPrepare, SQLPutData,SQLSetConnectAttr, SQLSetCursorName, SQLSetEnvAttr, and SQLSetStmtAttr,the argument was a null pointer.

对于 SQLAllocHandle、SQLExecDirect、SQLNativeSql、SQLPrepare、SQLPutData、SQLSetConnectAttr、SQLSetCursorName、SQLSetEnvAttr 和 SQLSetStmtAttr，参数为空指针。

For SQLForeignKeys, SQLPrimaryKeys, SQLStatistics, SQLTablePrivileges,and SQLTables, the TableName argument was a null pointer. The SQL_ATTR_METADATA_ID statement attribute was set to SQL_TRUE, the CatalogName argument was a null pointer, and the SQL_CATALOG_NAME InfoType returns that catalog names are supported. The SQL_ATTR_METADATA_ID statement attribute was set to SQL_TRUE, and the SchemaName or ColumnName argument was a null pointer.

对于 SQLForeignKeys、SQLPrimaryKeys、SQLStatistics、SQLTablePrivileges 和SQLTable，TableName 参数是一个空指针。SQL_ATTR_METADATA_ID 语句属性设置为SQL_TRUE，CatalogName 参数为空指针，SQL_CATALOG_NAME InfoType 返回支持目录名称的内容。SQL_ATTR_METADATA_ID 语句属性被设置为 SQL_TRUE，SchemaName 或ColumnName 参数是空指针。

For SQLColumn, SQLColumnPrivileges, SQLProcedures, SQLProcedureColumns,and SQLSpecialColumns, the SQL_ATTR_METADATA_ID statement attribute was set to SQL_TRUE, the CatalogName argument was a null pointer, and the SQL_CATALOG_NAME InfoType returns that catalog names are supported.(DM)The SQL_ATTR_METADATA_ID statement attribute was set to SQL_TRUE, and the SchemaName, ProcName, or ColumnName argument was a null pointer.

对于 SQLColumn、SQLColumnPrivileges、SQLProcedures、SQLProcdureColumns 和SQLSpecialColumns，SQL_ATTR_METADATA_ID 语句属性被设置为 SQL_TRUE，CatalogName参数是空指针，SQL_CATALOG_NAME InfoType 返回支持目录名称的目录名称。(DM)SQL_ATTR_METADATA_ID 语句属性设置为 SQL_TRUE，SchemaName、ProcName 或ColumnName 参数为空指针。

-11119 Attribute cannot be set now.

This GBase 8s ODBC error code is the same as SQLSTATE value HY011. The following functions can return this error code: SQLBulkOperations,SQLSetConnectAttr, SQLSetEnvAttr, SQLSetPos, and SQLSetStmtAttr.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 HY011 相同。以下函数可以返回此错误代码：SQLBulkOperations、SQLSetConnectAttr、SQLSetEnvAttr、SQLSetPos 和SQLSetStmtAttr。

For SQLBulkOperations and SQLSetPos, the driver was an ODBC 2.x driver;the SQL_ATTR_ROW_STATUS_PTR statement attribute was set; then SQLSetPos was called before SQLFetch, SQLFetchScroll, or SQLExtendedFetch was called.

对于 SQLBulkOperations 和 SQLSetPos，驱动程序是 ODBC 2.x 驱动程序；设置了SQL_ATTR_ROW_STATUS_PTR 语句属性；然后在调用 SQLFetch、SQLFetchScroll 或SQLExtendedFetch 之前调用 SQLSetPos。

For SQLSetConnectAttr, the Attribute argument was SQL_ATTR_TXN_ISOLATION,and a transaction was open.

对于 SQLSetConnectAttr，属性参数是 SQL_ATTR_TXN_ISOLATN，并且打开了一个事务。

For SQLSetEnvAttr, a connection handle has been allocated on EnvironmentHandle.(DM) The Attribute argument was SQL_ATTR_OUTPUT_NTS,and the SQL_ATTR_ODBC_VERSION attribute had not been set.

对于 SQLSetEnvAttr，在 Environment Handle 上分配了一个连接句柄。(DM)属性参数为SQL_ATTR_OUTPUT_NTS，而 SQL_ATTR_ODBC_VERSION 属性尚未设置。

For SQLSetStmtAttr, the Attribute was SQL_ATTR_CONCURRENCY,SQL_ATTR_CURSOR_TYPE, SQL_ATTR_SIMULATE_CURSOR, or SQL_ATTR_USE_BOOKMARKS, and the statement was prepared.

对于 SQLSetStmtAttr，属性为 SQL_ATTR_CONCOUNITY、SQL_ATTR_COURSOR_TYPE、SQL_ATTR_SIMULATE_COSOR 或 SQL_ATTR_USE_BOOKMARKS，并准备了语句。

-11120 Memory management error This GBase 8s ODBC error code is the same as SQLSTATE value HY013. The following functions can return this error code: all ODBC functions except: SQLGetDiagField and SQLGetDiagRec.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 HY013 相同。以下函数可以返回此错误代码：除 SQLGetDiagField 和 SQLGetDiagRec 以外的所有 ODBC 函数。

The function call could not be processed because the underlying memory objects could not be accessed, possibly because of low memory conditions.

由于无法访问底层内存对象，可能是由于内存条件较低，因此无法处理函数调用。

-11122 Cannot modify an implementation row descriptor.

This GBase 8s ODBC error code is the same as SQLSTATE value HY016. The following functions can return this error code: SQLCopyDesc,SQLSetDescField, and SQLSetDescRec.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 HY016 相同。以下函数可以返回此错误代码：SQLCopyDesc、SQLSetDescField 和 SQLSetDescRec。

For SQLCopyDesc and SQLSetDescRec, DescHandle was associated with an IRD.

对于 SQLCopyDesc 和 SQLSetDescRec，DescHandle 与 IRD 相关联。

For SQLSetDescField, the DescriptorHandle argument was associated with an IRD, and the FieldIdentifier argument was not SQL_DESC_ARRAY_STATUS_PTR or SQL_DESC_ROWS_PROCESSED_PTR.

对于 SQLSetDescField，DescriptorHandle 参数与 IRD 相关联，而 FieldIdentifier参数不是 SQL_DESC_ARRAY_STATUS_PTR 或 SQL_DESC_ROWS_PROCESSED_PTR。

-11123 Invalid use of an automatically allocated descriptor handle This GBase 8s ODBC error code is the same as SQLSTATE value HY017. The following functions can return this error code: SQLFreeHandle and SQLSetStmtAttr.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 HY017 相同。以下函数可以返回此错误代码：SQLFreeHandle 和 SQLSetstmtAttr。

For SQLFreeHandle, the Handle argument was set to the handle for an automatically allocated descriptor.

对于 SQLFreeHandle，句柄参数设置为自动分配描述符的句柄。

For SQLSetStmtAttr, the Attribute argument was SQL_ATTR_IMP_ROW_DESC or SQL_ATTR_IMP_PARAM_DESC.(DM) The Attribute argument was SQL_ATTR_APP_ROW_DESC or SQL_ATTR_APP_PARAM_DESC, and the value in ValuePtr was an implicitly allocated descriptor handle other than the handle originally allocated for the ARD or APD.

对于 SQLSetStmtAttr，属性参数为 SQL_ATTR_IMP_ROW_DESC 或SQL_ATTR_IMP_PARAM_DESC。(DM)属性参数为 SQL_ATTR_APP_ROW_DESC 或SQL_ATTR_APP_PARAM_DESC，而 ValuePtr 中的值是为 ARD 或 APD 分配的句柄以外的一个隐式分配句柄。

-11127 Inconsistent descriptor information This GBase 8s ODBC error code is the same as SQLSTATE value HY021. The following functions can return this error code: SQLBindParameter,SQLCopyDesc, SQLGetDescField, SQLSetDescField, and SQLSetDescRec.

此 ODBC错误代码与 SQLSTATE 值 HY021 相同。以下函数可以返回此错误代码：SQLBindParameter、SQLCopyDesc、SQLGetDescField、SQLSetDescField 和SQLSetDescRec。

For SQLBindParameter, the descriptor information checked during a consistency check was not consistent. The value specified for the argument DecimalDigits was outside the range of values supported by the data source for a column of the SQL data type specified by the ParameterType argument.

对于 SQLBindParameter，在一致性检查期间检查的描述符信息不一致。为参数DecimalDigits 指定的值超出了由 ParameterType 参数指定的 SQL 数据类型列的数据源支持的值范围。

For SQLCopyDesc, SQLSetDescField, and SQLSetDescRec, the descriptor information checked during a consistency check was not consistent.

对于 SQLCopyDesc、SQLSetDescField 和 SQLSetDescRec，在一致性检查期间检查的描述符信息不一致。

For SQLGetDescField, the SQL_DESC_TYPE and SQL_DESC_DATETIME_INTERVAL_CODE fields do not form a valid ODBC SQL type,a valid driver-specific SQL type (for IPDs), or a valid ODBC C type (for APDs or ARDs).

对于 SQLGetDescField，SQL_DESC_TYPE 和 SQL_DESC_DATETIME_INTERVAL_CODE 字段不构成有效的 ODBC SQL 类型、有效的特定于驱动程序的 SQL类型（用于 IPDS）或有效的ODBC C 类型(用于 APDS 或 ARD)。

-11275 Cursor operation conflict This GBase 8s ODBC error code is the same as SQLSTATE value 01001. The following functions can return this error code: SQLExecDirect,SQLExecute, and SQLSetPos.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 01001 相同。以下函数可以返回此错误代码：SQLExecDirect、SQLExecute 和 SQLSetPos。

For SQLExecute and SQLExecDirect, StatementText contained a positioned update or delete statement and no rows or more than one row were updated or deleted. (For more information about updates to more than one row, see the description of the SQL_ATTR_SIMULATE_CURSOR Attribute in SQLSetStmtAttr.) (Function returns SQL_SUCCESS_WITH_INFO.)对于 SQLExecute 和 SQLExecDirect，StatementText 包含一个定位的 UPDATE 或DELETE 语句，并且没有更新或删除任何行或多行。(有关多行更新的更多信息，请参见SQLSetStmtAttr 中的 SQL_ATTR_SIMULATE_CURSOR 属性的说明。)(函数返回SQL_SUCCESS_WITH_INFO。)For SQLSetPos, the Operation argument was SQL_DELETE or SQL_UPDATE, and no rows or more than one row were deleted or updated. (For more information about updates to more than one row, see the description of the SQL_ATTR_SIMULATE_CURSOR Attribute in SQLSetStmtAttr.) (Function returns SQL_SUCCESS_WITH_INFO.)对于 SQLSetPos，操作参数为 SQL_DELETE 或 SQL_UPDATE，没有删除或更新任何行或多行。(有关多行更新的更多信息，请参见 SQLSetStmtAttr 中的SQL_ATTR_SIMULATE_CURSOR 属性的说明。)(函数返回 SQL_SUCCESS_WITH_INFO。)-11278 Fractional truncation.

This GBase 8s ODBC error code is the same as SQLSTATE value 01S07. The following functions can return this error code: SQLExecDirect,SQLExecute, SQLExtendedFetch, SQLFetch, SQLFetchScroll, SQLGetData, and SQLSetPos.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 01S07 相同。以下函数可以返回此错误代码：SQLExecDirect、SQLExecute、SQLExtendedFetch、SQLFetch、SQLFetchScroll、SQLGetData 和 SQLSetPos。

For SQLExecDirect, SQLExecute, SQLExtendedFetch, SQLFetch,SQLFetchScroll, and SQLGetData, the data returned for an input/output or output parameter was truncated such that the fractional part of a numeric data type was truncated or the fractional portion of the time component of a time, timestamp, or interval data type was truncated.

对于 SQLExecDirect、SQLExecute、SQLExtendedFetch、SQLFetch、SQLFetchScroll 和SQLGetData，输入/输出或输出参数返回的数据被截断，以便截断数字数据类型的小数部分或截断时间、时间戳或间隔数据类型的时间分量的小数部分。

For SQLSetPos, the Operation argument was SQL_REFRESH, the data type of the application buffer was not SQL_C_CHAR or SQL_C_BINARY, and the data returned to application buffers for one or more columns was truncated.

For numeric data types, the fractional part of the number was truncated.

For time, timestamp, and interval data types that contain a time component, the fractional portion of the time was truncated.

对于 SQLSetPos，操作参数为 SQL_REFRESH，应用程序缓冲区的数据类型不是SQL_C_CHAR 或 SQL_C_BINARY，返回到应用程序缓冲区的一个或多个列的数据被截断。对于数值数据类型，数字的小数部分被截断。对于包含时间组件的时间、时间戳和间隔数据类型，时间的小数部分被截断。

-11280 Invalid keyword.

This GBase 8s ODBC error code is the same as SQLSTATE value 01S09. The following function can return this error code: SQLDriverConnect.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 01S09 相同。以下函数可以返回此错误代码：SQLDRiverConnect。

For SQLDriverConnect, the string in *InConnectionString contained a SAVEFILE keyword but not a DRIVER or FILEDSN keyword. (Function returns SQL_SUCCESS_WITH_INFO.)对于 SQLDRiverConnect，*InConnectionString 中的字符串包含 SAVEFILE 关键字，但不包含 DRIVER 或 FILEDSN 关键字。(函数返回 SQL_SUCCESS_WITH_INFO。)-11301 A protocol error has been detected. Current connection is closed.

This GBase 8s ODBC error code is the same as SQLSTATE value 08S01.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 08S01 相同。

Connection is closed by the database server.

数据库服务器关闭连接。

Try running the client application again.

再次尝试运行客户端应用程序。

-11305 SQLGetTypeInfo supported for FORWARD_ONLY Cursors This GBase 8s ODBC error code is the same as SQLSTATE value S1000. The following function can return this error code: SQLGetTypeInfo.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 S1000 相同。以下函数可以返回此错误代码：SQLGetTypeInfo。

Change your cursor type to SQL_CURSOR_FORWARD_ONLY.

将游标类型更改为 SQL_CURSOR__FORWARD_ONLY。

-11307 In SQLExtendedFetch, only SQL_FETCH_NEXT is supported for SQL_SCROLL_FORWARD_ONLY cursors.

This GBase 8s ODBC error code is the same as SQLSTATE value S1000. The following function can return this error code: SQLExtendedFetch.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 S1000 相同。以下函数可以返回此错误代码：SQLExtendedFetch。

-11310 Create and Drop database must be executed within a ServerOnly connection.

This GBase 8s ODBC error code is the same as SQLSTATE value S1000. The following function can return this error code: SQLPrepare.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 S1000 相同。以下函数可以返回此错误代码：SQLPrepare。

Change your CONNECTDATABASE option to YES in the connect string for SQLDriverConnect or remove this option from the connect string, as default value of CONNECTDATABASE is YES.

将 CONNECTDATABASE 选项在 SQLDRiverConnect 的连接字符串中更改为“是”，或者从连接字符串中删除此选项，因为 CONNECTDATABASE 的缺省值是“是”。

-11320 Syntax Error This GBase 8s ODBC error code is the same as SQLSTATE value S1000. The following functions can return this error code: SQLNativeSQL,SQLExecDirect, and SQLPrepare.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 S1000 相同。以下函数可以返回此错误代码：SQLNativeSQL、SQLExecDirect 和 SQLPrepare。

Check your statement string for syntax error. Consult ODBC Reference Manual for SQL syntax.

检查语句字符串是否有语法错误。有关 SQL 语法，请参阅 ODBC 参考手册。

-11323 The statement contained an escape clause not supported by this database driver.

This GBase 8s ODBC error code is the same as SQLSTATE value S1000. The following functions can return this error code: SQLNativeSQL,SQLExecDirect, and SQLPrepare.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 S1000 相同。以下函数可以返回此错误代码：SQLNativeSQL、SQLExecDirect 和 SQLPrepare。

Remove the escape clause from the statement string argument for the above functions.

从上述函数的语句字符串参数中删除 escape 子句。

-11330 Invalid lo_stat structure.

This GBase 8s ODBC error code is the same as SQLSTATE value S1000. The following function can return this error code: SQLExecDirect.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 S1000 相同。以下函数可以返回此错误代码：SQLExecDirect。

Reopen the large object and then refetch the lo_stat structure.

重新打开大对象，然后重新获取 lo_stat 结构。

-11331 Describe Parameter supported only for INSERT and UPDATE statements.

This GBase 8s ODBC error code is the same as SQLSTATE value S1000. The following function can return this error code: SQLDescribeParam.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 S1000 相同。以下函数可以返回此错误代码：SQLDescribeParam。

-11332 Expected number of parameters does not match parameters returned from server.

This GBase 8s ODBC error code is the same as SQLSTATE value S1000. The following functions can return this error code: SQLExecDirect and SQLExecute.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 S1000 相同。以下函数可以返回此错误代码：SQLExecDirect 和 SQLExecute。

Check the number of output parameters bound for that statement.

请检查为该语句绑定的输出参数的数量。

-11353 Database is not capable of supporting transactions. Check logging mode.

This GBase 8s ODBC error code is the same as SQLSTATE value 01S02. The following function can return this error code: SQLSetConnectAttr.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 01S02 相同。以下函数可以返回此错误代码：SQLSetConnectAttr。

-11354 Any open cursors are now invalid and must be closed before being used.

This GBase 8s ODBC error code is the same as SQLSTATE value 01000. The following functions can return this error code: SQLExecDirect,SQLExecute, and SQLSetConnectAttr.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 01000 相同。以下函数可以返回此错误代码：SQLExecDirect、SQLExecute 和 SQLSetConnectAttr。

-11414 Already in transaction. SPL routine could not get executed.

This GBase 8s ODBC error code is the same as SQLSTATE value S1000. The following functions can return this error code: SQLExecDirect,SQLExecute, SQLFetch, SQLFetchScroll, SQLExtendedFetch,SQLBulkOperations, SQLParamData, and SQLSetPos.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 S1000 相同。以下函数可以返回此错误代码：SQLExecDirect、SQLExecute、SQLFetch、SQLFetchScroll、SQLExtendedFetch、SQLBulkOperations、SQLParamData 和 SQLSetPos。

Remove any redundant Begin Commit from the client application.

从客户端应用程序中删除任何多余的 Begin Commit 。

-11415 Cannot set LO Automatic option OFF when Standard ODBC Types only is ON.

This GBase 8s ODBC error code is the same as SQLSTATE value S1000. The following functions can return this error code: SQLSetStmtAttr and SQLSetConnectAttr.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 S1000 相同。以下函数可以返回此错误代码：SQLSetStmtAttr 和 SQLSetConnectAttr。

Turn the SQL_INFX_ATTR_ODBC_TYPES_ONLY off first before turning the SQL_INFX_LO_AUTOMATIC_ATTR off for a statement or connection.

首先关闭 SQL_INFX_ATTR_ODBC_TYPES_ONLY，然后在语句或连接中关闭SQL_INFX_LO_AUTOMATIC_ATTR 。

-11416 Cannot set Standard ODBC Types only to ON when LO Automatic option is OFF.

This GBase 8s ODBC error code is the same as SQLSTATE value S1000. The following functions can return this error code: SQLSetStmtAttr and SQLSetConnectAttr.

此 GBase 8s ODBC 错误代码与 SQLSTATE 值 S1000 相同。以下函数可以返回此错误代码：SQLSetStmtAttr 和 SQLSetConnectAttr。

Turn the SQL_INFX_LO_AUTOMATIC_ATTR on first before turning the SQL_INFX_ATTR_ODBC_TYPES_ONLY on for a statement or connection.

首先打开 SQL_INFX_LO_AUTOMATIC_ATTR，然后在语句或连接中打开SQL_INFX_ATTR_ODBC_TYPES_ONLY。

-11302 Insufficient Connection information was supplied.

This GBase 8s CLI error code is an extended message to SQLSTATE value S1000.

GBase 8s CLI functions that can generate this error: SQLConnect and SQLDriverConnect.

此 GBase 8s CLI 错误代码是对 SQLSTATE 值 S1000 的扩展消息。GBase 8s CLI 函数可以生成此错误：SQLConnect 和 SQLDRiverConnect。

Check the connect string passed to SQLDriverConnect for accurate information or check the DSN entries. You must supply the required values to connect.

检查传递给 SQLDRiverConnect 的连接字符串以获得准确的信息或检查 DSN 条目。必须提供连接所需的值。

-11303 Input Connection string too large.

This GBase 8s CLI error code is an extended message to SQLSTATE value S1000.

GBase 8s CLI functions that can generate this error: SQLDriverConnect and SQLBrowseConnect.

此 GBase 8s CLI 错误代码是对 SQLSTATE 值 S1000的扩展消息。GBase 8s CLI 函数可以生成此错误：SQLDRiverConnect 和 SQLBrowseConnect。

Length of the connection string should be less than 1024 bytes.

连接字符串的长度应该小于 1024 字节。

-11317 Invalid CONNECTDATABASE value specified.

This is an extended message to SQLSTATE value S1000. Functions that can generate this error: SQLBrowseConnect and SQLDriverConnect.

这是对 SQLSTATE 值 S1000 的扩展消息。可产生此错误的函数：SQLBrowseConnect和 SQLDRiverConnect。

Valid values are YES and NO (not case-sensitive).

有效值为“是”和“否”(不区分大小写)。

-11318 Invalid VMBCHARLENEXACT value specified.

This is an extended message to SQLSTATE value S1000. Functions that can generate this error: SQLBrowseConnect and SQLDriverConnect.

这是对 SQLSTATE 值 S1000 的扩展消息。可产生此错误的函数：SQLBrowseConnect 和SQLDRiverConnect。

The valid values are 0 and 1.

有效值为 0 和 1。

-11400 Cannot rollback the transaction.

The application has faulty logic or the database server is down. Check the native error for more information.

应用程序有错误的逻辑，或者数据库服务器出现故障。有关更多信息，请检查本机错误。

-11401 TM down not successful.

TM did not shut down gracefully. Shut down and restart the MS DTC.

TM 没有优雅地关闭。关闭并重新启动 MS DTC。

-11402 Not in DTC transaction.

You are trying to unenlist a transaction that is not in the MS DTC. This situation occurs if the transaction timeout value is low. Use the MTS explorer to increase the transaction timeout.

您正在尝试取消一个不在 MS DTC 中的事务。如果事务超时值较低，则会发生此情况。使用 MTS 资源管理器增加事务超时。

-11403 DSN required for DTC transactions.

Report this error to GBase Technical Support.

向 GBase 技术支持部门报告此错误。

-11404 Failed to create RM in DTC transactions.

The amount of available memory is insufficient or the MS DTC log has become corrupted. Check the amount of available memory and the MS DTC log.

可用内存量不足，或者 MS DTC 日志已损坏。检查可用内存量和 MS DTC 日志。

-11405 Filed to get Resource Manager Object.

Report this error to GBase Technical Support.

向 GBase 技术支持部门报告此错误。

-11406 Filed to get XID.

The MS DTC failed or the transaction timeout value is low. If the MS DTC failed, restart it. Otherwise, use the MTS explorer to increase the transaction timeout.

MS DTC 失败或事务超时值低。如果 MS DTC 失败，请重新启动它。否则，使用 MTS 资源管理器增加事务超时。

-11407 Opening of the database created error.

Check the GBase 8s CLI error code. This problem might indicate that the database was not created with a log.

检查 GBase 8s CLI 错误代码。此问题可能表明数据库不是用日志创建的。

-11408 Cannot enlist with RM.

The MS DTC might have failed. If so, restart it.

MS DTC 可能失败了。如果是的话，重新启动它。

-11409 Failed to create Enlistment object out of memory.

The system has insufficient memory. Install more memory.

系统内存不足。安装更多内存。

-11410 Prepare failed.

Report this error to GBase Technical Support.

向 GBase 技术支持部门报告此错误。

-11411 Commit failed.

Report this error to GBase Technical Support.

向 GBase 技术支持部门报告此错误。

-11412 Recover failed.

Report this error to GBase Technical Support.

向 GBase 技术支持部门报告此错误。

-11413 Failed to connect to the server.

The database server might be down. If so, restart it.

数据库服务器可能被关闭。如果是，请重新启动它。

-12000 Smart Large Objects: Cannot add entry to lofd table.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12001 Smart Large Objects: Cannot add entry to lohd table.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12002 Smart Large Objects: Cannot add entry to sbspace table.

Sbspace entry might already be in the table.

Sbspace 条目可能已经在表中了。

-12003 Smart Large Objects: Cannot add entry to chunkadj table.

Chunk with this number might already be in the table.

这个编号的 chunk 可能已经在表中了。

-12004 Smart Large Objects: Cannot add entry to arcreg table.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12005 Smart Large Objects: Cannot add entry to arcspace table.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12006 Smart Large Objects: Cannot add smart large object to truncation Q.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12007 Smart Large Objects: Cannot add smart large object to delete Q.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12008 Smart Large Objects: Cannot delete entry in lofd table.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12009 Smart Large Objects: Cannot delete entry in lohd table.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12010 Smart Large Objects: Cannot delete entry in sbspace table.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12011 Smart Large Objects: Cannot delete entry in chunkadj table.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12012 Smart Large Objects: Cannot delete entry in arcrec table.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12013 Smart Large Objects: Cannot delete entry in arcspace table.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12014 Smart Large Objects: Cannot find entry in lofd table.

An attempt was made to access a smart large object using an invalid LO file descriptor.

尝试使用无效的 LO 文件描述符访问智能大对象。

Check that the LO file descriptor you supplied is correct and that the smart large object is still open.

请检查您提供的 LO 文件描述符是否正确，以及智能大对象是否仍处于打开状态。

-12015 Smart Large Objects: Cannot find entry in lohd table.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12016 Smart Large Objects: Cannot find entry in sbspace table.

Sbspace might not exist or invalid pointer.

Sbspace 可能不存在或无效指针。

-12017 Smart Large Objects: Cannot find entry in chunkadj table.

This error is an internal error.

此错误是一个内部错误。

If this error recurs, refer to your Administrator's Guide to acquire additional diagnostics. Contact GBase Technical Support with the diagnostic information.

如果再次出现此错误，请参考“管理员指南”获取其他诊断信息。请与 GBase 技术支持部门联系，了解诊断信息。

-12018 Smart Large Objects: Cannot find entry in arcrec table.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12019 Smart Large Objects: Cannot find entry in arcspace table.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12020 Smart Large Objects: Cannot unlock table entry.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12021 Smart Large Objects: Duplicate keys not allowed.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12022 Smart Large Objects: Duplicate entry in chunk adjtab.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12023 Smart Large Objects: chunk size is too small.

The smart-large-object chunk is less than the minimum required size.

Increase the chunk size in the onspaces command line. Check that you are using the correct units.

智能大对象 chunk 小于所需的最小大小。在 onspaces 命令行中增加 chunk 大小。检查是否使用正确的单位。

-12024 Smart Large Objects: Chunk dropped from sbspace.

You attempted to reference a chunk that is being dropped from the sbspace. If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12025 Smart Large Objects: Chunk not empty.

You attempted to drop a smart-large-object chunk that still contained data. The chunk was not dropped. To ensure that chunks you want to drop are empty, delete the rows that contain pointers to smart large objects in the chunk or remove the smart-large-object pointers in the rows.

您试图删除仍然包含数据的智能大对象 chunk 。chunk 没有被删除。若要确保要删除的chunk 为空，请删除 chunk 中包含指向智能大对象的指针的行，或删除行中的智能大对象指针。

-12026 Smart Large Objects: Cannot delete smart large object.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12027 Smart Large Objects: Cannot delete SB_LOHD_SLOT.

You cannot delete the LO header page for a smart large object. The chunk or sbspace might be inaccessible or the LO address might be invalid. Ensure that the chunk is accessible. Ensure that the smart-large-object address is still valid--that is, the smart large object has not already been removed.

不能删除智能大对象的 LO 标题页。chunk 或 sbspace 可能无法访问，或者 LO 地址可能无效。确保 chunk 是可访问的。确保智能大对象地址仍然有效，也就是说，智能大对象尚未被删除。

-12028 Smart Large Objects: Cannot delete SB_LOMAP_SLOT.

You cannot delete an extent map for a smart large object. Ensure that the chunk is accessible. If this error recurs, note all circumstances and contact GBase Technical Support.

不能删除智能大对象的区域映射。确保块是可访问的。如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12029 Smart Large Objects: Cannot delete SB_USERDATA_SLOT.

Cannot delete user data slot. First ensure that the chunk is accessible.

If this error recurs, note all circumstances and contact GBase Technical Support.

无法删除用户数据槽。首先，确保块是可访问的。如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12030 Smart Large Objects: Cannot release memory buffer.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12031 Smart Large Objects: Sbspace is full.

The user data area or areas have insufficient storage for a write request.

Delete some smart large objects or add a chunk to the sbspace.

用户数据区域对于写请求没有足够的存储空间。删除一些智能大对象或向 sbspace 添加chunk。

-12032 Smart Large Objects: Table is full.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12033 Smart Large Objects: Cannot insert SB_LOHD_SLOT.

You cannot insert a smart-large-object header page into the smart-large-object header partition. Add a chunk to the smart-large-object space with a metadata area.

不能将智能大对象标头页插入到智能大对象标头分区中。在具有元数据区域的智能大对象空间中添加一个 chunk。

-12034 Smart Large Objects: Invalid buffer size.

A smart-large-object read or write request specified an invalid length for the input or output buffer. The length was likely less than 0.

Correct the smart-large-object application program.

智能大对象读或写请求指定输入或输出缓冲区的无效长度.长度可能小于 0。更正智能大对象应用程序。

-12035 Smart Large Objects: Invalid lock type.

You either passed an invalid lock type or tried to lock a byte range exclusively after you opened the smart large object in read-only mode.

您可以传递无效的锁定类型，或者在以只读模式打开智能大对象后尝试独占锁定字节范围。

Check these two cases and use a valid lock type.

检查这两种情况并使用有效的锁类型。

-12036 Smart Large Objects: Invalid sbspace name.

During a smart-large-object create operation, a nonexistent smart-large-object space name was specified in the create specification.

在智能大对象创建操作期间，创建规范中指定了不存在的智能大对象空间名称。

Create the specified smart-large-object space with the onspaces -c -S command or ensure that the create specification used the correct sbspace name.

使用 onspace -c -S 命令创建指定的智能大对象空间，或者确保创建规范使用正确的sbspace 名称。

-12037 Smart Large Objects: Invalid seek position.

During a smart-large-object read or write operation, a seek position contained an invalid value. The value was likely less than 0. Correct the smart-large-object application program so that it specifies a valid read/write start position.

在智能大对象读写操作期间，搜索位置包含无效值.该值可能小于 0。更正智能大对象应用程序，以便它指定有效的读/写开始位置。

-12038 Smart Large Objects: Invalid access time flag combination.

During a smart-large-object CREATE or ALTER operation, a create specification was provided that specified conflicting values for the access time flag. Correct the smart-large-object application program.

Ensure that the create specification is set to the default NULL values before you provide it to the smart-large-object subsystem. Use ifx_lo.

在智能大对象创建或更改操作期间，提供了为访问时间标志指定冲突值的创建规范。更正智能大对象应用程序。在将创建规范提供给智能大对象子系统之前，请确保将其设置为缺省空值。使用 ifx_lo。

-12039 Smart Large Objects: Invalid whence value for seek.

The whence parameter for a smart-large-object seek or I/O operation contains an invalid value. Set the whence parameter to the correct value.

智能大对象查找或 I/O 操作的 whence 参数包含无效值。将 whence 参数设置为正确的值。

-12040 Smart Large Objects: Invalid truncate value for size.

The new size parameter supplied to a truncate operation for a smart large object was invalid. The new size parameter was probably less than zero. Correct the smart-large-object application program.

为智能大对象的截断操作提供的新大小参数无效。新的大小参数可能小于零。更正智能大对象应用程序。

-12041 Smart Large Objects: Size of smart large object or buffer is too big.

The size after a write or truncate operation exceeds the maximum size limit for the smart large object. The system does not allow the size of the smart large object to exceed the maximum number of bytes that the application sets. This size limit was set by the CREATE or ALTER statement for the smart large object.

写入或截断操作后的大小超过智能大对象的最大大小限制。系统不允许智能大对象的大小超过应用程序设置的最大字节数。此大小限制是由智能大对象的 CREATE 或 ALTER 语句设置的。

-12042 Smart Large Objects: Size of page is too big.

The page size specified during an sbspace creation operation is too big. Specify a page size that is less than the platform-dependent maximum asynchronous I/O size or is greater than the subsystem page-size limitation for the smart large object.

在 sbspace 创建操作中指定的页大小太大。指定小于平台相关的最大异步 I/O 大小或大于智能大对象的子系统页大小限制的页大小。

-12043 Smart Large Objects: Invalid create flags.

The smart-large-object create specification contains mutually inconsistent flags. Fix the create specification flags in the smart-large-object application program so that the flags do not conflict. Before the create specification is used, ensure that the create specification has been initialized to the appropriate default values by using the function that the database server provides.

智能大对象创建规范包含相互不一致的标志.修复智能大对象应用程序中的创建规范标志，以便这些标志不会冲突。在使用创建规范之前，通过使用数据库服务器提供的函数，确保已将创建规范初始化为适当的缺省值。

-12044 Smart Large Objects: Invalid integrity type flag combination.

The smart-large-object create specification contains conflicting flags for the integrity field. Change the smart-large-object application program so that no more than one integrity flag is set in the smart-large-object create specification.

智能大对象创建规范包含完整性字段的冲突标志。更改智能大对象应用程序，以便在智能大对象创建规范中设置不超过一个完整性标志。

-12045 Smart Large Objects: Invalid logging mode combination.

The smart-large-object create specification contains conflicting flags for the log-mode field. Change the smart-large-object application program so that no more than one logging mode is specified in the smart-large-object create specification. Before you use the create specification, ensure that the create specification has been initialized to the proper default values by using the functions that the database server provides.

智能大对象创建规范包含日志模式字段的冲突标志。更改智能大对象应用程序，以便在智能大对象创建规范中指定不超过一种日志记录模式。在使用创建规范之前，确保已经使用数据库服务器提供的函数将创建规范初始化为正确的缺省值。

-12046 Smart Large Objects: Cannot enter critical section.

Call to isenter() failed.

调用 isenter()失败。

Contact GBase Technical Support.

请与 GBase 技术支持联系。

-12047 Smart Large Objects: sb_lo_map_offs failed.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12048 Smart Large Objects: unique ID does not match. Smart large object probably deleted.

The smart large object being referenced by the smart-large-object pointer has been deleted.

由智能大对象指针引用的智能大对象已被删除。

Ensure that the smart-large-object pointer is valid and that the smart large object has not been deleted. If you are keeping a smart-large-object handle,then the reference count for the smart large object must be greater than 0 or the database server deletes the smart large object at session end.

请确保智能大对象指针有效，且智能大对象未被删除。如果要保留智能大对象句柄，则智能大对象的引用计数必须大于 0，否则数据库服务器将在会话结束时删除智能大对象。

-12049 Smart Large Objects: No memory.

The system ran out of memory during a smart-large-object operation.

在智能大对象操作期间，系统内存不足。

Add more virtual memory or determine the cause of the memory leak.

请添加更多虚拟内存或确定内存泄漏的原因。

-12050 Smart Large Objects: dbm_bfget: Cannot get a memory buffer.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12051 Smart Large Objects: Smart large object was not opened for read.

You attempted to read a smart large object that was not open for reading.

您试图读取未打开的智能大对象。

Change the smart-large-object application program so that it opens the smart large object in read mode.

请更改智能大对象应用程序，使其在读取模式下打开智能大对象。

-12052 Smart Large Objects: Smart large object was not opened for write.

You attempted to write to a smart large object that was not open for writing. Change the smart-large-object application program so that it opens the smart large object for writing.

您试图写入一个未打开的智能大对象。更改智能大对象应用程序，以便打开智能大对象进行写入。

-12053 Smart Large Objects: No sbspace number specified.

No default sbspace was found, and the caller has not specified an sbspace to use.

没有找到默认的 sbspace，调用方也没有指定要使用的 sbspace。

Either specify the smart-large-object space name in the smart-large-object function call or set the SBSPACENAME onconfig file parameter to the name of a valid smart-large-object space.

要么在智能大对象函数调用中指定智能大对象空间名称，要么将 SBSPACENAME onconfig文件参数设置为有效的智能大对象空间的名称。

-12054 Smart Large Objects: Cannot open chunk adj partition.

The chunk might be down.

chunk 可能已关闭。

Ensure that the smart-large-object space chunk is up.

请确保智能大对象空间 chunk 已打开。

-12055 Smart Large Objects: Cannot open smart-large-object header partition.

The chunk might be down.

chunk 可能已关闭。

Ensure that the smart-large-object space chunk is up.

请确保智能大对象空间 chunk 已打开。

-12056 Smart Large Objects: Cannot open sbspace.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12057 Smart Large Objects: Cannot open sbspace description partition.

The smart-large-object space is probably down, or an attempt was made to open a space that should have been a smart-large-object space but was not.

智能大对象空间可能已经关闭，或者试图打开一个本应是智能大对象空间但却不是的空间。

Ensure that the first chunk of the smart-large-object space is up.

Also ensure that an application program is not attempting to perform TEXT or BYTE operations to a smart-large-object space.

确保智能大对象空间的第一个 chunk 已打开。还要确保应用程序不试图对智能大对象空间执行 TEXT 或 BYTE 操作。

-12058 Smart Large Objects: Cannot read chunk adjunct entry.

The smart-large-object space is corrupt or down.

智能大对象空间已损坏或关闭。

If the space is down, perform the actions necessary to bring it back online.

如果空间关闭，执行必要的动作使其返回在线。

-12059 Smart Large Objects: open failed at read of smart-large-object header.

Possibly you attempted to open a nonexistent or deleted smart large object.

可能您试图打开一个不存在或已删除的智能大对象。

Ensure that the system is not collecting unreadable data in the smart large object because of a zero reference count. Ensure that the smart-large-object handle is not getting corrupted.

确保系统没有收集不可读取的数据智能大对象，因为零引用计数。确保智能大对象句柄没有被损坏。

-12060 Smart Large Objects: Cannot read SB_LOMAP_SLOT.

The database server cannot read the extent map for the smart large object.

数据库服务器无法读取智能大对象的范围映射。

Check to see if the smart-large-object space is corrupt or if the chunk is down.

请检查智能大对象空间是否损坏或 chunk 是否已关闭。

-12061 Smart Large Objects: Cannot read user data.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12062 Smart Large Objects: Error in user data free list.

User data free list cannot be manipulated.

无法操作用户数据空闲列表。

-12063 Smart Large Objects: Cannot update SB_LOHD_SLOT.

Cannot read smart-large-object header page for smart large object.

Cannot update smart-large-object header page for smart large object.

无法读取智能大对象的智能大对象标题页。

无法更新智能大对象的智能大对象标题页。

-12064 Smart Large Objects: Cannot update SB_LOMAP_SLOT.

Cannot update extent map for smart large object.

无法更新智能大对象的范围映射。

-12065 Smart Large Objects: Cannot update optimization data.

Optimization data cannot be put into the sbspace description entry.

优化数据不能放入 sbspace 描述项中。

-12066 Smart Large Objects Archive: Cannot build pre-image temporary partition.

An attempt to create a temporary partition during an archive failed.

在归档期间创建临时分区的尝试失败。

Ensure that the dbspace in which temporary partitions are placed is not full and is accessible.

请确保放置临时分区的 dbspace 不是满的，并且是可访问的。

-12067 Smart Large Objects Archive: Cannot extend pre-image temporary partition.

An attempt to lengthen a temporary partition during an archive failed.

在存档期间延长临时分区的尝试失败。

Ensure that the dbspace in which temporary partitions are placed is not full and is accessible.

请确保放置临时分区的 dbspace 不是满的，并且是可访问的。

-12068 Smart Large Objects Archive: Cannot drop pre-image temporary partition during archive.

An attempt to drop the pre-image temporary partition failed. Ensure that the dbspace in which temporary partitions are placed is accessible.

删除图像前页临时分区的尝试失败。确保放置临时分区的 dbspace 是可访问的。

-12069 Smart Large Objects Archive: Cannot write pre-image page to temporary partition.

An attempt to write a pre-image page during archive failed. Ensure that the dbspace in which the temporary partitions are placed is accessible.

在存档期间编写图像前页的尝试失败。确保放置临时分区的 dbspace 是可访问的。

-12070 Smart Large Objects Archive: Cannot read pre-image page from temporary partition.

An attempt to read a pre-image page during archive failed. Ensure that the dbspace in which the temporary partitions are placed is accessible.

在存档期间读取图像前页的尝试失败。确保放置临时分区的 dbspace 是可访问的。

-12071 Smart Blobs Archive: During restore, a page write failed.

During an archive restore, a page-write operation to the chunk failed.

Ensure that the device is accessible.

在存档还原期间，对 chunk 的页写操作失败。确保设备是可访问的。

-12072 Smart Large Objects: Not implemented.

An unimplemented smart-large-object feature was accessed. Wait until the next release.

访问了未实现的智能大对象功能。等到下一个版本。

-12073 Smart Large Objects Archive: Archive already active on sbspace.

Another archive is already running on the same sbspace. Ensure that you do not have another archive running on the same sbspace. Only one archive operation on an sbspace at a time is permitted.

另一个存档文件已经在相同的 sbspace 上运行。确保在相同的 sbspace 上没有运行另一个存档。一次只允许在 sbspace 上执行一个归档操作。

-12074 Smart Large Objects: Free extension list overflow.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12075 Smart Large Objects Archive: Cannot delete arch rec table.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12076 Smart Large Objects Archive: Cannot create arch space table.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12077 Smart Large Objects Archive: Unexpected exit condition.

During an archive, the database server detected that the number of pages it expected to read from the chunk was not the number of pages that actually could be read. Try restarting the archive.

在存档期间，数据库服务器检测到它希望从 chunk 读取的页数不是实际可读取的页数。

试着重新启动档案。

-12078 Smart Large Objects Archive: Illegal level specified for archiving.

You specified an illegal archive level. You must specify an archive level of 0, 1, or 2.

您指定了非法存档级别。必须指定 0、1 或 2 的存档级别。

-12079 Smart Large Objects: Cannot decrement zero reference count.

The reference count for the smart large object is already 0. Attempts to decrement the reference count to less than 0 are ignored.

智能大对象的引用计数已经为 0。忽略将引用计数减少到小于 0 的尝试。

-12080 Smart Large Objects Archive: Page is outside user data area.

An attempt was made to archive a page outside the user data area. If this error recurs, note all circumstances and contact GBase Technical Support.

尝试将页面存档在用户数据区域之外。如果再次出现此错误，请注意所有情况，并与GBase 技术支持部门联系。

-12081 Smart Large Objects Archive: illegal control page type in arc.

The archive tape was corrupted either by a user error or a database server malfunction. Ensure that the archive file was not corrupted through user error. If the archive file is intact, the database server malfunctioned. You can either try to create another archive of the same sbspace, or you can remove the sbspace from the list of spaces to be archived and try to archive the remaining spaces.

存档磁带由于用户错误或数据库服务器故障而损坏。确保存档文件不会因用户错误而损坏。如果存档文件完整，则数据库服务器出现故障。您可以尝试为相同的 sbspace 创建另一个归档文件，也可以从要归档的空格列表中删除 sbspace，并尝试对其余的空间进行归档。

-12082 Smart Large Objects Archive: invalid state encountered.

The smart-large-object archive program encountered an archive record that was out of sequence. Ensure that the archive file has not been corrupted through user error. If the archive file is intact, the database server malfunctioned. You can either try to create another archive of the same sbspace, or you can remove the sbspace from the list of spaces to be archived and try to archive the remaining spaces.

智能大对象存档程序遇到的存档记录不符合顺序.确保存档文件未因用户错误而损坏。如果存档文件完整，则数据库服务器出现故障。您可以尝试为相同的 sbspace 创建另一个归档文件，也可以从要归档的空格列表中删除 sbspace，并尝试对其余的空间进行归档。

-12083 Smart Large Objects: Restore: END_DESC record found before SB_ARC_CHUNK_RECS record.

-12084 Smart Large Objects: Restore: NULL control info block ptr;archive records out of order.

存档磁带由于用户错误或数据库服务器故障而损坏。确保存档文件不会因用户错误而损坏。如果存档文件完整，则数据库服务器出现故障。您可以尝试为相同的sbspace 创建另一个归档文件，也可以从要归档的空格列表中删除 sbspace，并尝试对其余的空间进行归档。

-12085 Smart Large Objects: Restore: SB_ARC_END_DESC record not found for this chunk.

-12086 Smart Large Objects: open: invalid open flags detected at smart-large-object open time.

A programmer entered conflicting smart-large-object open flags. For instance, LO_LOG and LO_NOLOG cannot be set at the same time. Check open-flag settings to ensure that conflicting flags are not being set.

In addition, ensure that the smart-large-object open-flag field is initialized.

程序员输入了冲突的智能大对象打开标志。例如，LO_LOG 和 LOG_NOLOG 不能同时设置。

检查打开标志设置，以确保没有设置冲突的标志。此外，确保初始化了智能大对象打开标志字段.

-12087 Smart Large Objects: alter: attempt to change physical characteristics of a smart large object in sb_alter.

The database administrator attempted to perform an alter operation on a smart-large-object column that requires physical reorganization or relocation of the smart large objects.

数据库管理员试图对需要对智能大对象进行物理重组或重新定位的智能大对象列执行ALTER 操作。

Do not attempt to reorganize smart large objects physically.

As an alternative to physical reorganization, try using the LOCopy function to copy smart large objects to a new location with different physical attributes.

不要试图从物理上重新组织智能大对象。作为物理重组的替代方法，尝试使用 LOCopy 函数将智能大对象复制到具有不同物理属性的新位置。

-12088 Smart Large Objects: create: number of estimate bytes < -1.

The application programmer has specified an invalid value for the estimated number of bytes in a smart large object. If the number of bytes in a smart large object is unknown, set the estimated-number-of-bytes field to -1 or call ifx_lo_def_create_spec or the equivalent mi function and then leave this field alone.

应用程序员为智能大对象中的估计字节数指定了一个无效的值。如果智能大对象中的字节数未知，则将估计字节数字段设置为 -1，或调用 ifx_lo_def_create_spec 或等效的 mi函数，然后将该字段单独处理。

-12089 Smart Large Objects: create: size limit of smart large object < -1.

The application programmer specified an invalid value for the size limit of the smart large object. If the number of bytes in a smart large object is unknown, set the estimated-number-of-bytes field to -1 or call ifx_lo_def_create_spec or the equivalent mi function and then leave this field alone.

应用程序员为智能大对象的大小限制指定了无效值。如果智能大对象中的字节数未知，则将估计字节数字段设置为 -1，或调用 ifx_lo_def_create_spec 或等效的 mi 函数，然后将该字段单独处理。

-12090 Smart Large Objects: create: invalid column parameters.

The database server received a smart-large-object create specification that has invalid values in the column portion. Either the application programmer forgot to call the ifx_lo_def_create_spec function or the mi equivalent with create specification, or the create specification data structure has been corrupted.

数据库服务器收到了一个智能大对象创建规范，其中列部分中的值无效。应用程序员要么忘记调用 ifx_lo_def_create_spec 函数，要么调用与创建规范等价的 mi，要么创建规范数据结构已损坏。

-12091 Smart Large Objects: the in-memory sbspace table doesn't exist.

Database server initialization error.

数据库服务器初始化错误。

-12092 Smart Large Objects: sbspace exists but is currently down.

Either the database server or the database administrator brought the smart-large-object space down. Look at the database server log to determine why the sbspace is down. You might need to bring up the sbspace.

无论是数据库服务器还是数据库管理员，都会导致智能大对象空间下降。查看数据库服务器日志以确定 sbspace 关闭的原因。你可能需要提升空间。

-12093 Smart Large Objects: archive failed to create a mutex and aborted.

The system could be out of memory.

系统可能内存不足。

-12094 Smart Large Objects: bad temporary partition page number.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-12095 Smart Large Objects: create: Invalid Ext. size() Ext. size < -1 or > MAXINT.

The application programmer specified an invalid value for the estimated number of bytes in a smart large object. If the extent size is out of range for a smart large object, set the estimated extent size to -1 or call ifx_lo_def_create_spec or the equivalent mi function and then leave this field alone.

应用程序员为智能大对象中的估计字节数指定了一个无效的值。如果范围大小超出智能大对象的范围，则将估计的范围大小设置为 -1，或调用 ifx_lo_def_create_spec 或等效的 mi 函数，然后将该字段单独处理。

-12096 Smart Large Objects: alter: New size limit < number of bytes in the smart large object.

The application programmer specified an invalid value for the size limit. The value must be greater than or equal to the current number of bytes in the smart large object. If the new size limit is less than the current number of bytes in the smart large object, do not alter the value in the header.

应用程序员为大小限制指定了无效值。该值必须大于或等于智能大对象中当前字节数。如果新的大小限制小于智能大对象中当前字节数，则不要更改标头中的值。

-12097 Smart Large Objects: Invalid smart large object address or ID.

The most likely reason for this error message is that the smart large object reference being used contains outdated information. The client application might have passed an invalid smart large object reference to the server: for example, a reference to a smart large object the application deleted prior to the current reference attempt. If a smart large object is deleted and then a new one created in its place, any references to the old object are no longer valid, because the new object will have a different ID even if it is stored in the same physical location.

此错误消息最可能的原因是正在使用的智能大对象引用包含过时的信息。客户端应用程序可能已将无效的智能大对象引用传递给服务器：例如，在当前引用尝试之前，应用程序删除了对智能大对象的引用。如果删除了一个智能大对象，然后在其位置创建了一个新对象，则对旧对象的任何引用都不再有效，因为新对象即使存储在相同的物理位置，也将具有不同的 ID。

-12098 Smart Large Objects: Sbspace corrupted.

If this internal error code for access sequence recurs, note all circumstances and contact GBase Technical Support.

如果访问序列的内部错误代码再次出现，请注意所有情况，并与 GBase 技术支持部门联系。

-12099 Smart Large Objects: Archiver found a smart large object with a corrupted header.

The archiver detected a smart large object missing an extent map slot or a header slot. The archive process is corrupted.

归档器检测到缺少 extent map 槽或标头槽的智能大对象。归档过程已损坏。

-12100 Smart Large Objects: A bad value was entered for the sbpage unit.

The page unit must be between 1 and the maximum asynchronous I/O size.

Re-execute the creation command with a correct page unit.

页面单元必须介于 1 和最大异步 I/O 大小之间。使用正确的页面单元重新执行创建命令。

-12101 Smart Large Objects: A bad value was entered for the average smart-large-object size.

You entered a bad value for avg_lo_size, in kilobytes, during the creation of an sbspace. Re-execute the creation command with a correct average smart-large-object size, in kilobytes.

在创建 sbspace 期间，输入了 avg_lo_size 的坏值（以 KB 为单位）。使用正确的平均智能大对象大小（以千字节为单位）重新执行创建命令.

0 <= Smart Large Object < 2 Terabytes-12102 Smart Large Objects: A bad Meta Data Area was entered for the smart large object.

The metadata area received a bad value during the creation of a smartblob sbspace. Re-execute the creation command with a correct metadata size:在创建 smartblob sbspace 期间，元数据区域收到了一个坏值。使用正确的元数据大小重新执行创建命令：0 <= metadata area size < chunk size-12103 Smart Large Objects: Attempt to open a non-sbspace as an sbspace.

The smartblob subsystem detected an attempt to open a smart-large-object space when the space specified was really a dbspace or a blobspace. The application might be attempting to use the smart-large-object application programming interface on a space that is not a smart-large-object space. Ensure that you are only using the smart-large-object commands and interface on a smart-large-object space and on smart large objects. The smart-large-object API cannot be used on TEXT and BYTE data types.

当指定的空间实际上是 dbspace 或 bobspace 时，smartblob 子系统检测到有人试图打开智能大对象空间。应用程序可能试图在不是智能大对象空间的空间上使用智能大对象应用程序编程接口。确保只在智能大对象空间和智能大对象上使用智能大对象命令和接口。

智能大对象 API 不能用于 TEXT 和 BYTE 数据类型.

-12104 Smart Large Objects: Inconsistent LO map was encountered.

Contact GBase Technical Support.

与 GBase 技术支持部门联系。

-12105 Smart Large Objects: An attempt to change the sbspace name was made.

In an alter operation, an attempt was made to change the name of the sbspace for the smart large object. You cannot change an sbspace name with the alter operation.

在 ALTER 操作中，尝试更改智能大对象的 sbspace 名称。不能用 ALTER 操作更改sbspace 名称。

Re-execute the alter operation with a NULL sbspace name in the LO-specification structure or the name of the sbspace in which the smart large object currently resides.

请在 LO 规范结构中使用空 sbspace 名称或当前智能大型对象所在的 sbspace 重新执行ALTER 操作。

-12106 Smart Large Objects: Could not find delete Q for transaction.

This error is internal.

此错误是内部错误。

If the error recurs, refer to your Administrator's Guide to acquire additional diagnostics. Contact GBase Technical Support with the diagnostic information.

如果该错误再次发生，请参考管理员指南获取其他诊断信息。请与 GBase 技术支持部门联系，了解诊断信息。

-12108 Smart Large Objects: Unknown version.

Server encountered an unknown version during conversion of smart-large-object metadata. Make sure that you are converting/reverting to a supported version of the server.

服务器在转换智能大对象元数据时遇到了未知版本.确保您正在转换/恢复到受支持的服务器版本。

-12109 Smart Large Objects: Conversion failed.

During conversion/reversion of server, conversion/reversion of sbspace failed.

在服务器的转换/还原过程中，sbspace的转换/还原失败。

Your smart blob space might have been corrupted before conversion.

您的智能 BLOB 空间在转换之前可能已经损坏。

Run oncheck -cS and oncheck -ce on all sbspaces before conversion.

If an sbspace is corrupt, you might need to restore the sbspace from a backup before conversion.

在转换之前在所有 sbspace 上运行 oncheck -cS 和 oncheck -ce。如果 sbspace 已损坏，则可能需要在转换前从备份还原 sbspace。

-12110 Smart Large Objects: Could not find suitable size extent.

Server could not find a suitable size extent for a smart large object.

A write request might not be complete.

服务器无法为智能大对象找到大小合适的 extent。写入请求可能不完整。

Delete some smart large objects or add a chunk to the sbspace.

请删除一些智能大对象或向 sbspace 添加 chunk。

-12111 Smart Large Objects: Attempt to write to a smart large object without closing light IO scan.

The user tried to write to a smart large object that is currently opened for a lightweight I/O scan.

用户试图写入当前为轻量级 I/O 扫描打开的智能大对象。

Close the open smart large object and open it again (without lightweight I/O) before you write to the smart large object.

在写入智能大对象之前，请关闭打开的智能大对象并再次打开它(没有轻量级 I/O)。

-12112 Smart Large Objects: Conversion from using buffers to light IO not allowed.

The user tried to change the buffering mode of a smart large object from buffered I/O to lightweight I/O.

用户试图将智能大对象的缓冲模式从缓冲 I/O 更改为轻量级 I/O。

This type of conversion is currently not allowed.

目前不允许这种类型的转换。

-12113 Smart Large Objects: Attempt to convert from using light IO to buffers while LO is open.

The user tried to alter a smart large object with either ifx_lo_alter()(ESQL/C) or mi_lo_alter() (DAPI) while some instances of the smart large object are currently open.

用户试图使用 ifx_lo_alter()(ESQL/C) 或 mi_lo_alter() (DAPI) 更改智能大对象，而智能大对象的某些实例目前正在打开。

Close all open instances of the smart large object before altering the buffering mode with ifx_lo_alter() or mi_lo_alter().

在使用 ifx_lo_alter() 或 mi_lo_alter() 更改缓冲模式之前，请关闭智能大对象的所有打开实例。

-12114 Smart Large Objects: Archive not started.

This error is internal. The smart-large-object subsystem was asked to build a user-data extent list before the archiving started.

这个错误是内部的。在开始归档之前，智能大对象子系统被要求构建一个用户数据 extent 列表。

-12115 The LO header page is a wrong length - probably corrupted.

An internal error probably occurred and corrupted the LO header.

可能发生内部错误并损坏 LO 报头。

Delete and recreate the smart large object or restore the sbspace from an archive.

请删除并重新创建智能大对象或从存档中恢复 sbspace。

-12116 Smart Large Objects: Bad LO header.

LO header read from disk is bad. Refer to log file for LO id. Most likely sbspace is corrupt. Restore the sbspace from backup.

从磁盘读取的 LO 标头是不好的。查阅 LO id 的日志文件。很可能 sbspace 是损坏的。

从备份恢复 sbspace。

-12117 Smart Large Objects: Bad LO header (encountered during deletion).

LO header read from disk is bad. Most likely sbspace is corrupt. Run oncheck -ce on the sbspace. You might need to restore the sbspace from an archive.

从磁盘读取的 LO 标头是不好的。很可能 sbspace 是损坏的。在 sbspace 上运行。您可能需要从存档中恢复 sbspace。

-12118 Smart Large Objects: Bad LO extent map.

The extent map record for the smart large object is corrupt. Most likely the sbspace is corrupt. Run oncheck -ce on the sbspace. You might need to restore the sbspace from an archive.

智能大对象的区段映射记录已损坏。最有可能的是 sbspace 是损坏的。在 sbspace 上运行。您可能需要从存档中恢复 sbspace。

-12119 Smart Large Objects: reversion of sbspace failed.

The database server reversion you attempted encountered an error during the reversion of the sbspace.

您尝试的数据库服务器还原在 sbspace 的还原过程中遇到错误。

You can find the reason for this failure in the log file. If the error is recoverable, retry the reversion. If the error persists, contact GBase Technical Support.

您可以在日志文件中找到此失败的原因。如果错误是可恢复的，请重试还原。如果错误仍然存在，请与 GBase 技术支持部门联系。

-12120 Smart Large Objects: Duplicate key encountered in sbspace create.

During the creation of an sbspace, it was noticed that the sbspace number was the same as some other sbspace number. The most common cause of the problem is failure to create an sbspace in an earlier attempt.

在创建 sbspace 时，注意到 sbspace 号与其他 sbspace 数相同。问题最常见的原因是在早期的尝试中未能创建 sbspace。

Rebooting the database server will remove the entry from the internal table.

重新启动数据库服务器将从内部表中删除该条目。

-12121 Smart Large Objects: The sbspace is flagged as dropped.

You are attempting an operation on an sbspace that someone else is trying to drop. Perhaps they are using a forced drop command. Do not use sbspaces that are being dropped. The force drop allows you to drop an sbspace that contains data.

您正在尝试对其他人试图删除的 sbspace 进行操作。也许他们是在使用强制降落命令。

不要使用正在删除的 sbspace。强制删除允许您删除包含数据的 sbspace。

-12122 Smart Large Objects: drop of the sbspace chunk is already occurring.

You are probably attempting an operation that might be in conflict with a chunk drop operation that is already occurring (for example, trying to drop a chunk when sbspace is being dropped). Retry the operation later.

您可能尝试的操作可能与已经发生的块丢弃操作发生冲突（例如，在删除 sbspace 时尝试删除 chunk）。稍后重试操作。

-12123 Smart Large Object: Metadata is full.

The metadata area in the smart-large-object space has insufficient storage for a create or write request.

智能大对象空间中的元数据区域对于创建或写入请求没有足够的存储空间。

Delete some of the smart large objects or add a chunk with metadata space to the sbspace. Use the -Ms option of onspaces to add additional metadata space.

请删除一些智能大对象，或者向 sbspace 添加带有元数据空间的 chunk。使用 onspace的 -Ms 选项添加其他元数据空间。

-12124 Smart Large Objects: The archive preimage partition doesn't exist.

An internal error occurred in the archiver. The preimage partition should exist at this point but it does not.

归档程序中发生内部错误。在这一点上，预图像分区应该存在，但它不存在。

If the error recurs, refer to your Administrator's Guide to acquire additional diagnostics. Contact GBase Technical Support with the diagnostic information.

如果出现错误，请参考管理员指南获取其他诊断信息。请与 GBase 技术支持部门联系，了解诊断信息。

-12125 Smart Large Objects: No more slots in LO header partition.

This is an internal code.

这是一个内部代码。

If the error recurs, refer to your Administrator's Guide to acquire additional diagnostics. Contact GBase Technical Support with the diagnostic information.

如果出现错误，请参考管理员指南获取其他诊断信息。请与 GBase 技术支持部门联系，了解诊断信息。

-12126 Smart Large Objects: LO is not opened for byte range locking.

A call to one of the byte-range locking functions has attempted to specify a byte-range lock:对一个字节范围锁定函数的调用试图指定一个字节范围锁：* ESQL/C: ifx_lo_lock() or ifx_lo_unlock()* ESQL/C: ifx_lo_lock() 或 ifx_lo_unlock()* DAPI: mi_lo_lock() or mi_lo_unlock()* DAPI: mi_lo_lock() 或 mi_lo_unlock()The smart large object is currently opened for locking at the whole-object level.

智能大对象当前打开以便在整个对象级别锁定。

Close the smart large object, then reopen the smart large object with the LO_LOCKRANGE (ESQL/C) or MI_LO_LOCKRANGE (DAPI) lock-mode flag set.

关闭智能大对象，然后使用 LO_LOCKRANGE (ESQL/C) 或 MI_LO_LOCKRANGE (DAPI) 锁定模式标志设置重新打开智能大对象。

-12127 Smart Large Objects: Invalid range size in byte range lock / unlock call.

A call to one of the byte-range locking functions specifies a range size that is invalid:对一个字节范围锁定函数的调用指定无效的范围大小：* ESQL/C: ifx_lo_lock() or ifx_lo_unlock()* ESQL/C: ifx_lo_lock() 或 ifx_lo_unlock()* DAPI: mi_lo_lock() or mi_lo_unlock()* DAPI: mi_lo_lock() 或 mi_lo_unlock()An invalid range size is either a negative value or has the following sum that results in an INT8 overflow:无效的范围大小不是负值，就是导致 INT8 溢出的以下和：offset + range size Use a valid range size in the byte-range locking function.

在字节范围锁定函数中使用有效的范围大小。

-12128 Smart Large Objects: Invalid offset in byte range lock / unlock call.

A call to one of the byte-range locking functions specifies an offset that is invalid:对一个字节范围锁定函数的调用指定无效的偏移量：* ESQL/C: ifx_lo_lock() or ifx_lo_unlock()* ESQL/C: ifx_lo_lock() 或 ifx_lo_unlock()* DAPI: mi_lo_lock() or mi_lo_unlock()* DAPI: mi_lo_lock() 或 mi_lo_unlock()An invalid offset means that the provided combination of (offset, whence)results in a negative value.

无效偏移量意味着所提供的（offset, whence）的组合会产生负值。

Use a valid (offset, whence) combination in the byte-range locking function.

在字节范围锁定函数中使用有效的（offset, whence）组合。

-12129 Smart Large Objects: Failed to create condition variable in smart-large-object open call.

The error might be generated when an out-of-memory condition occurs.

当内存不足情况发生时，可能会产生错误。

Check that you have closed all instances of smart large objects that are no longer in use. Also check the memory available to ensure that you have enough.

请检查是否已关闭不再使用的智能大型对象的所有实例。还要检查可用的内存，以确保您有足够的内存。

-12130 Smart Large Objects: Failed to create chunk because someone else is also creating one.

You tried to create chunks concurrently and had a conflict.

您尝试同时创建块并发生冲突。

Try to create the chunk again.

请再次创建该 chunk。

-12131 Smart Large Objects: Metadata area in the chunk contains data.

During a chunk drop, the metadata area in the chunk was not empty. The metadata area must be empty for the chunk to be dropped without dropping the sbspace.

在 chunk 删除期间，chunk 中的元数据区域不是空的。元数据区域必须为空，才能在不删除 sbspace 的情况下删除块。

Try to empty the metadata area by deleting all the smart large objects in the chunk. If you do not want the smart large objects, you can also "force" drop the sbspace.

请尝试通过删除 chunk 中的所有智能大对象来清空元数据区域。如果您不想要智能大对象，也可以“强制”删除 sbspace。

-12132 Smart Large Objects: Invalid lock type for lock merge.

This message is an internal error code.

此消息是内部错误代码。

Contact GBase Technical Support to report the error. Try creating the sbspace again.

请与 GBase 技术支持部门联系以报告错误。再次尝试创建 sbspace。

-12133 Smart Large Objects: During the creation of the sbspace, the desc partition was not the first in the sbspace.

An internal database server error occurred. The sbspace is likely corrupt or is not an sbspace.

发生内部数据库服务器错误。sbspace 可能已损坏或不是 sbspace。

Contact GBase Technical Support to report the error. Try creating the sbspace again.

请与 GBase 技术支持部门联系以报告错误。再次尝试创建 sbspace。

-12134 Smart Large Objects: During creation of the sbspace, the sbspace desc record was not the first in the partition.

An internal error occurred.

发生了内部错误。

Contact GBase Technical Support to report the error. Try creating the sbspace again.

请与 GBase 技术支持部门联系以报告错误。再次尝试创建 sbspace。

-12135 Smart Large Objects: Cannot initialize the smart-large-object subsystem.

The most likely cause of this error is that you are out of memory.

这个错误最可能的原因是你内存不足。

Increase the amount of available memory.

增加可用内存量。

-12136 Smart Large Objects: smart-large-object space is valid.

This is an internal code.

这是一个内部代码。

If the error recurs, refer to your Administrator's Guide to acquire additional diagnostics. Contact GBase Technical Support with the diagnostic information.

如果出现错误，请参考管理员指南获取其他诊断信息。请与 GBase 技术支持部门联系，了解诊断信息。

-12137 Smart Large Objects: sbspace does not exist.

The sbspace entry has been removed while it was in use. Someone probably did a force drop of the sbspace.

sbspace 条目在使用时已被移除。可能有人强制删除了 sbspace。

-12138 Smart Large Objects: Attempt to open an LO with light I/O and byte range locking.

At open time, you specified an unsupported combination of options.

Byte-range locking is not supported with light I/O. Check your program and remove one of the blob open flags (MI_LO_NOBUFFER flag or MI_LO_LOCKRANGE flag).

在打开时，您指定了不支持的选项组合。轻 I/O 不支持字节范围锁定。检查程序并删除BLOB 打开标志之一（MI_LO_NOBUFFER flag 或 MI_LO_LOCKRANGE flag）。

-12139 Smart Large Objects: Invalid option.

An invalid option was specified for changing sbspace characteristics.

Certain characteristics of an sbspace cannot be changed, such as the chunk offsets.

为更改 sbspace 特性指定了无效选项。sbspace 的某些特征不能更改，例如 chunk 偏移。

-12140 Smart Large Objects: Aborted by user.

No changes have been made to the sbspace. Utility aborted by user.

对 sbspace 没有做任何更改。由用户中止的实用程序。

-12141 Smart Large Objects: sbspace is not fully recovered.

You are trying to access a smart large object created in an sbspace that is not recovered yet. When the system opens an sbspace, it must be physically and logically restored before the open attempt.

您正在尝试访问尚未恢复的 sbspace 中创建的智能大型对象。当系统打开sbspace时，必须在打开尝试之前从物理上和逻辑上恢复它。

Wait until the recovery is complete before accessing the smart large object.

在访问智能大对象之前，等待恢复完成。

-12142 Smart Large Objects: Invalid sbspace number.

The sbspace ID number you specified is incorrect. It is either out of range or does not refer to a valid smartblob space.

您指定的 sbspace ID 编号不正确。它不是超出范围，就是不引用有效的 smartblob 空间。

Correct the sbspace ID number and retry the operation.

请更正 sbspace ID号，然后重试操作。

-12143 Smart Large Objects: Invalid chunk number.

The chunk number in an LO handle is not valid. Either it is out of range,or it does not exist. Most likely the LO handle is corrupt.

LO 句柄中的 chunk 号无效。要么它超出了范围，要么它不存在。LO 句柄很可能已损坏。

If you are getting this error in an ESQL program, make sure that the LO handle is valid. In addition, ensure that you did not force drop the chunk.

如果在 ESQL 程序中获得此错误，请确保 LO 句柄是有效的。此外，确保没有强制删除 chunk。

-12144 Smart Large Objects: Some space is allocated.

A chunk allocated to an sbspace is not empty. Some of its space is allocated to either metadata or user data. This error is internal.

分配给 sbspace 的 chunk 不是空的。它的一些空间被分配给元数据或用户数据。此错误是内部错误。

If the error recurs, refer to your Administrator's Guide to acquire additional diagnostics. Contact GBase Technical Support with the diagnostic information.

如果出现错误，请参考管理员指南获取其他诊断信息。请与 GBase 技术支持部门联系，了解诊断信息。

-12145 Smart Large Objects: sbspace is not fully recovered.

An attempt was made to archive an sbspace that is not recovered or consistent. An sbspace must be online and consistent before a backup is attempted.

尝试将未恢复或一致的 sbspace 存档。在尝试备份之前，sbspace 必须处于联机状态并保持一致。

Wait until the recovery is complete before backup. If the sbspace is online,check the sbspace using oncheck -cS and oncheck -ce. If it is inconsistent,you need to restore it from a backup first.

在备份之前等待恢复完成。如果 sbspace 处于联机状态，则使用 oncheck -cS 和oncheck -ce 检查 sbspace。如果不一致，则需要首先从备份中还原它。

-12146 General Table Manager: No mvkey function provided.

The table manager did not find an mvkey function.

表管理器没有找到 mvkey 函数。

-12148 General Table Manager: No table allocated.

The table has not been created or was deleted.

表尚未创建或删除。

-12149 General Table Manager: No memory.

Not enough memory was available.

内存不足。

-12150 General Table Manager: Mutex cannot be created.

No mutex (latch) is associated with the buffer, so it cannot be shared.

没有与缓冲区相关联的互斥（锁），因此不能共享它。

-12151 General Table Manager: Duplicate keys not allowed.

Table entries with the same key are not allowed.

不允许使用相同键的表条目。

-12152 General Table Manager: Table is full.

Table is full and cannot be extended.

表已满，无法扩展。

-12153 General Table Manager: Entry is locked.

Entry of a table is already locked.

表的条目已经锁定。

-12154 General Table Manager: Table is locked.

Table is already locked.

表已被锁定。

-12155 General Table Manager: No entry.

The required entry does not exist.

不存在所需的条目。

-12156 General Table Manager: Invalid entry specification.

Something in the table entry is incorrect.

表条目中的某些内容不正确。

-12157 General Table Manager: Invalid data specification.

One or more column values is incorrect.

一个或多个列值不正确。

-12201 Smart Large Objects: Non zero reference count.

You are trying to delete a smart large object whose reference count is not zero.

您正在尝试删除引用计数不是零的智能大对象。

-12202 Smart Large Objects: Non zero open count.

You are trying to delete a smart large object whose open count is not zero.

您正在尝试删除打开计数不是零的智能大对象。

-12203 Smart Large Objects: Cannot add LO to delete undo queue.

This error is internal.

此错误为内部错误。

If the error recurs, refer to your Administrator's Guide to acquire additional diagnostics. Contact GBase Technical Support with the diagnostic information.

如果出现错误，请参考管理员指南获取其他诊断信息。请与 GBase 技术支持部门联系，了解诊断信息。

-12204 RSAM error: Long transaction detected.

The database server ran out of log space in which to record this transaction. A transaction that is not fully recorded cannot be rolled back. To preserve database integrity, the database server ended the current operation that caused the long transaction.

数据库服务器没有记录此事务的日志空间。未完全记录的事务不能回滚。为了保持数据库完整性，数据库服务器结束导致长事务的当前操作。

Terminate the application and replan it so that it requires less log space in a transaction. Alternatively, contact the database server administrator to discuss increasing the number or the size of the logical logs. Be prepared to talk about the number of rows being updated or inserted and the size of each row.

终止应用程序并重新规划它，以便它在事务中需要更少的日志空间。另外，请与数据库服务器管理员联系，讨论如何增加逻辑日志的数量或大小。准备好谈论正在更新或插入的行数和每行的大小。

-12205 Smart Large Objects: No free disk space for archive preimage partition.

The database server ran out of space from rootdbs while extending the temp archive preimage partition.

数据库服务器在扩展临时存档预映像分区时，从 rootdb 中耗尽空间。

Add more space to rootdbs and restart the archive.

向 rootdb 添加更多空间并重新启动归档。

-12222 Cannot rename dbspace when checkpoint is in progress.

You cannot rename a dbspace during a checkpoint.

在检查点期间不能重命名 dbspace。

Retry renaming the dbspace after the checkpoint completes.

请在检查点完成后重命名dbspace。

-12223 Rename dbspace on HDR secondary.

You cannot rename a dbspace on HDR secondary.

不能在 HDR 辅助服务器上重命名 dbspace。

-12224 The partition needs to be archived.

If the table type is altered from non logging to logging, perform a backup before you use the table in a transaction or modify data within the table.

Otherwise the table may not be fully recovered if the server crashes.

如果表类型从非日志记录更改为日志记录，则在事务中使用表或在表中修改数据之前执行备份。否则，如果服务器崩溃，表可能无法完全恢复。

-12226 Cannot add dbspace.

When expanded chunk capacity mode is disabled, a dbspace with page size greater than the default page size cannot be added.

当禁用扩展块容量模式时，不能添加页大小大于默认页大小的 dbspace。

-12227 Page size mismatch.

Page size of the partition on tape is different from the page size of the target dbspace. Tape might contain a corrupt page (or) if you are executing onload command specify the correct DBspace name using the -d argument.

磁带上分区的页大小与目标 dbspace 的页大小不同。如果执行 onload 命令，磁带可能包含损坏的页(或)，使用 -d 参数指定正确的 dbspace 名称。

-12230 Cannot create blobspace blob.

You cannot create a blobspace blob on a secondary server.

不能在辅助服务器上创建 blobspace blob。

-12233 Alter in progress on partition.

The partition is being altered. The session could not obtain access to the requested table or index because it has been opened exclusively by another user. This condition is normally transient, retry operation after some delay.

分区正在被更改。会话无法访问请求的表或索引，因为它是由其他用户独占打开的。这种情况通常是暂时性的，延迟后再试运行。

-12234 Partition has been altered.

The partition has been altered and the table's data dictionary has been marked dirty. DML operations are susceptible to this error when they are referencing an older copy of the table's data dictionary information.

Most likely, the database server just completed a CREATE/DROP INDEX or ALTER FRAGMENT operation on the table referred to by the DML operation.

分区已被更改，表的数据字典被标记为脏。DML操作在引用表的数据字典信息的旧副本时容易发生此错误。最有可能的是，数据库服务器刚刚完成了 DML 操作所引用的表上的CREATE/DROP INDEX 或 ALTER FRAGMENT 操作。

This error is accompanied by SQL Error -710.

此错误伴随 SQL 错误 -710。

-12235 An online fragment operation is in progress on this table.

Only one online operations can be performed on a table at a time.

Wait until the online fragment operation is complete before reissuing another online command.

一次只能在一个表上执行一个联机操作。在重新发出另一个联机命令之前，等待联机片段操作完成。

-12240 Changed Data Capture: Generic Read Error.

The smart large object file descriptor you are using refers to a Changed Data Capture (CDC) session. An error has occurred while attempting to read data.

您使用的智能大对象文件描述符引用了更改的数据捕获(CDC)会话。在试图读取数据时发生了错误。

Monitor the CDC subsystem to determine the cause of the error.

请监视 CDC 子系统以确定错误的原因。

-12241 Changed Data Capture: The attempted operation is not supported.

The smart large object file descriptor you are using refers to a Changed Data Capture (CDC) session. Among the operations provided by the smart large object interface, CDC sessions only support read operations, without seeking.

您使用的智能大对象文件描述符引用的是已更改的数据捕获(CDC)会话。在智能大对象接口提供的操作中，CDC 会话只支持读取操作，不进行搜索。

Do not issue smart large object interface operations other than read on CDC sessions.

除了在 CDC 会话上读取之外，不要发出智能大对象接口操作。

-12242 Changed Data Capture: The CDC session must be closed.

The smart large object file descriptor you are using refers to a Changed Data Capture (CDC) session. The CDC session can no longer be read and must be closed. The likely cause is an error in the CDC subsystem.

您使用的智能大对象文件描述符引用的是更改的数据捕获(CDC)会话。CDC 会话不能再读取，必须关闭。可能的原因是 CDC 子系统中的一个错误。

Issue the close operation provided by the Changed Data Capture interface on the CDC session. Monitor the CDC subsystem to determine the nature of the error.

在 CDC 会话上发出由更改的数据捕获接口提供的关闭操作。监视 CDC 子系统以确定错误的性质。

-12243 Changed Data Capture: Read size smaller than minimum allowed.

The smart large object file descriptor you are using refers to a Changed Data Capture (CDC) session. The amount of data you have requested to be read from the CDC session is less than the minimum allowed.

您使用的智能大对象文件描述符引用的是已更改的数据捕获(CDC)会话。您请求从 CDC 会话读取的数据量小于允许的最小数据量。

Retry the read operation with a larger read size. The minimum allowed read size is 128 bytes.

请使用较大的读取大小重试读取操作。允许的最小读取大小为 128 字节。

-12244 Changed Data Capture: Object in incorrect state for attempted operation.

The smart large object file descriptor you are using refers to a Changed Data Capture (CDC) session. The operation on the CDC session encountered internal structures in an incorrect state.

您使用的智能大对象文件描述符引用的是更改的数据捕获(CDC)会话。CDC 会话上的操作遇到了内部结构不正确的状态。

Report to GBase Technical Support.

向 GBase 技术支持报告。

-12245 Changed Data Capture: Memory corruption detected.

The smart large object file descriptor you are using refers to a Changed Data Capture (CDC) session. The CDC subsystem has detected evidence of memory corruption. This is an internal error.

您使用的智能大对象文件描述符引用了更改的数据捕获(CDC)会话。CDC 子系统检测到内存损坏的证据。这是一个内部错误。

Report to GBase Technical Support.

向 GBase 技术支持报告。

-12246 Smart large objects: You cannot put a temporary large object into a permanent table You attempted to take a temporary smart large object and put it into a permanent table. This large object can disappear leaving the permanent table with an invalid pointer.

Checking for this behavior is controlled by onconfig parameter SB_CHECK_FOR_TEMP.

您尝试将一个临时的智能大对象放到一个永久的表中。这个大对象可能会消失，留下一个无效指针的永久表。对此行为的检查由 onconfig 参数 SB_CHECK_FOR_TEMP 控制。

-12247 Smart Large Objects: Processing failed because of an invalid buffer size from the client The server uses the buffer size provided by the client to process smart large object data. The buffer size that the client provided is not valid.

服务器使用客户端提供的缓冲区大小来处理智能大对象数据。客户端提供的缓冲区大小无效。

ACTION If this internal error recurs, note all circumstances and contact GBase Software Support.

措施：如果此内部错误再次发生，请注意所有情况并与 GBase 技术支持联系。

-12800 Unsuspected internal error.

An inconsistency has been found in the data used to invoke access method routines.

在用于调用 access_method 例程的数据中发现了不一致性。

-12801 An attempt was made to invoke an access_method routine that does not exist.

An SQL statement has been used that would normally cause a particular access_method routine to be invoked, but the routine is not defined for that access_method. Unless the routine is defined for the corresponding access_method purpose, the SQL statement cannot be used for that access method.

所使用的 SQL 语句通常会导致调用特定的 access_method 例程，但该例程未为该access_method 定义。除非为相应的 access_method 目的定义了例程，否则 SQL 语句不能用于该 access method。

-12802 Error in initializing an access_method routine execution sequence.

An access_method routine cannot be made ready to execute. For example,the external name used in the CREATE FUNCTION statement that defined the access_method routine might not exist. Check that the routines used for the access_method are properly defined.

access_method 例程无法准备执行。例如，定义 access_method 例程的 CREATE FUNCTION 语句中使用的外部名称可能不存在。检查用于 access_method 的例程是否已正确定义。

-12803 Error in executing an access_method routine execution sequence.

An error occurred when an attempt was made to execute an access_method routine. Try the statement again.

尝试执行 access_method 例程时出错。请重试该语句。

-12804 Error indicated by an access_method routine.

An access_method routine returned MI_ERROR.

access_method 例程返回 MI_ERROR。

-12805 Improper return value from access_method routine.

An access_method routine returned a value that is not valid. Possibly a bug exists in the access_method routine.

access_method 例程返回一个无效的值。可能 access_method 例程中存在错误。

-12806 Unable to build row descriptor.

An error occurred in building a row descriptor to be used by an access_method routine.

生成 access_method 例程使用的行描述符时出错。

-14500 CSS: error Communication Support Services internal error.

通信支持服务内部错误。

Contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件(concsm.cfg）和用于客户端和数据库服务器的 sqlhost 信息。

-14501 CSS: out of memory Not enough memory to run in this configuration.

内存不足，无法在此配置中运行。

Check the system parameters.

请检查系统参数。

-14502 CSS: CSM not found.

Communication Support Services could not locate a Communications Support Module with the given name.

通信支持服务无法找到具有给定名称的通信支持模块。

Check the Communications Support Module definition in the concsm.cfg file, and the CSM option field in the sqlhosts file.

请检查 consm.cfg 文件中的通信支持模块定义，以及 sqlhost 文件中的 CSM 选项字段。

-14503 CSS error loading Communication Support Services failed to load the library that contains a Communications Support Module.

通信支持服务无法加载包含通信支持模块的库。

Check the path name of the CSM library in CSS configuration file, and Make sure it is a valid shared library.

请在 CSS 配置文件中检查 CSM 库的路径名，并确保它是有效的共享库。

If the problem persists, contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

如果问题仍然存在，请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：数据库服务器版本或客户端 SDK。

-14504 CSS: unsupported CSM version in Communication Support Services does not support the version of the Communications Support Module interface that a given Communications Support Module uses.

通信支持服务不支持给定通信支持模块使用的通信支持模块接口的版本。

Make sure the database server or client application support the CSM interface version in question.

请确保数据库服务器或客户端应用程序支持所讨论的 CSM 接口版本。

If the problem persists, contact GBase Technical Support or the CSM vendor and have the following information available: the version of the database server or the client SDK.

如果问题仍然存在，请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：数据库服务器版本或客户端 SDK。

-14506 CSS: CSM : unexpected return code A Communications Support Module returned an unusual completion status.

通信支持模块返回了不寻常的完成状态。

Contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件和用于客户端和数据库服务器的 sqlhost 信息。

-14507 CSS: cascade disconnected.

For Communications Support Module: the peer disconnected.

对于通信支持模块：对等机断开连接。

如果断开连接似乎出乎意料，且问题仍然存在，请与 GBase 技术支持公司或 CSM 供应商联系，并提供以下信息：CSS 配置文件和用于客户端和数据库服务器的 sqlhost 信息。

-14508 CSS: error getting flags from CSM .

Communication Support Services internal error.

通信支持服务内部错误。

Contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件和用于客户端和数据库服务器的 sqlhost 信息。

-14509 CSS: CSM disconnected inside cascade.

For Communications Support Module: a Communications Support Module inside the cascade disconnected.

通信支持模块：级联内部的通信支持模块断开。

如果断开连接看起来出乎意料，而且问题仍然存在，请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件和用于客户端和数据库服务器的 sqlhost 信息。

-14510 CSS: null buffer owner Communication Support Services internal error.

通信支持服务内部错误。

Contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件和用于客户端和数据库服务器的 sqlhost 信息。

-14511 CSS: init function is not found in library .

A shared library that contains a Communications Support Module does not export a Communications Support Module initialization function.

包含通信支持模块的共享库不导出通信支持模块初始化功能。

Contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件和用于客户端和数据库服务器的 sqlhost 信息。

-14512 CSS: shared library name is not specified.

The CSM library path name in the CSS configuration file is missing, or there is an error.

CSS 配置文件中的 CSM 库路径名丢失，或者出现错误。请检查 CSS 配置文件。

Check the CSS configuration file.

请检查 CSS 配置文件。

如果问题仍然存在，请与 GBase Technology Support 或 CSM 供应商联系，并提供以下信息：CSS 配置文件和用于客户端和数据库服务器的 sqlhost 信息。

-14513 CSS: CSM cannot finish a service operation.

A Communications Support Module is deadlocked. It requires more data without having an adequate data source. This is an internal error.

通信支持模块陷入死锁。它需要更多的数据，而没有足够的数据源。这是内部错误。

Contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件和用于客户端和数据库服务器的 sqlhost 信息。

-14551 CSS: CSM: no CSM name specified.

The user did not specify the name of a Communications Support Module to be used.

用户没有指定要使用的通信支持模块的名称。

Check the CSM option field in the sqlhosts file, and the CSS configuration file.

请检查 sqlhost 文件中的 CSM 选项字段和 CSS 配置文件。

-14562 CSS: no buffer management function provided.

Communication Support Services caller did not provide a buffer management function in I/O reference context to Communication Support Services.

通信支持服务调用方在 I/O 引用上下文中没有提供对通信支持服务的缓冲区管理功能。

Contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件和用于客户端和数据库服务器的 sqlhost 信息。

-14563 CSS: error writing data.

Communication Support Services internal error.

通信支持服务内部错误。

Failure performing data output.

Contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件和用于客户端和数据库服务器的 sqlhost 信息。

-14564 CSS: no output function provided.

Communication Support Services internal error.

通信支持服务内部错误。

Communication Support Services caller did not provide a data output function in I/O reference context to Communication Support Services.

通信支持服务调用方没有在 I/O 引用上下文中向通信支持服务提供数据输出功能。

Contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件和用于客户端和数据库服务器的 sqlhost 信息。

-14565 CSS: error reading data.

The database server or client's attempt to receive data to establish Communication Support Services (CSS) context failed.

数据库服务器或客户端试图接收数据以建立通信支持服务(CSS)上下文失败。

Probable causes of the error and corrective actions follow:错误的可能原因和纠正措施如下：* This error usually occurs when the CSM option is turned on and the database server or the network is very busy, or when too many clients are trying to connect to the database server at once. The database server might be taking so long to respond to a client that the client's connection request times out before the connection is complete. Or possibly a client terminates its connection attempt before the connection is completely established.

* 此错误通常发生在打开 CSM 选项且数据库服务器或网络非常繁忙时，或者当太多客户端试图同时连接到数据库服务器时。数据库服务器可能需要很长时间才能响应客户端，以至于客户端的连接请求在连接完成之前超时。也可能是客户端在连接完全建立之前终止其连接尝试。

* Use the environment variable GBASEDBTCONTIME or GBASEDBTCONRETRY, or both, on the client side to increase the connection time and the number of retry attempts.

* 在客户端使用环境变量 GBASEDBTCONTIME 或 GBASEDBTCONRETRY，或者两者都使用，以增加连接时间和重试尝试的次数。

* Either the database server or the client application exits abnormally due to an error condition. The other side which is waiting for data from the failed side would report this error. Check the error on the failed side for the root cause of the problem.

* 数据库服务器或客户端应用程序由于错误情况而异常退出。正在等待失败端数据的另一方将报告此错误。检查故障侧的错误，找出问题的根本原因。

If the problem persists, contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files (concsm.cfg) and sqlhosts information for both the client and the database server.

如果问题仍然存在，请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS配置文件(consm.cfg)和 sqlhost 客户端和数据库服务器的信息。

-14566 CSS: no input function provided.

Communication Support Services internal error.

通信支持服务内部错误。

Communication Support Service caller did not provide a buffer management function in reference context to Communication Support Services.

通信支持服务调用方没有在通信支持服务的引用上下文中提供缓冲区管理功能。

Contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件和用于客户端和数据库服务器的 sqlhost 信息。

-14567 CSS: buffer management function return code .

Communication Support Services internal error.

通信支持服务内部错误。

Error while disposing of a data buffer provided by a Communication Support Services caller.

在处理通信支持服务调用方提供的数据缓冲区时出错。

Contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件和用于客户端和数据库服务器的 sqlhost 信息。

-14571 CSS: null CSS library context.

Communication Support Services internal error.

通信支持服务内部错误。

Communication Support Services caller passed a null library context to Communication Support Services.

通信支持服务调用方将空库上下文传递给通信支持服务。

Contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件和用于客户端和数据库服务器的 sqlhost 信息。

-14572 CSS: null I/O reference context.

Communication Support Services internal error.

通信支持服务内部错误。

Communication Support Services caller passed a null I/O reference context to Communication Support Services.

通信支持服务调用方将空 I/O 引用上下文传递给通信支持服务。

Contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件和用于客户端和数据库服务器的 sqlhost 信息。

-14573 SS: bogus iterator direction.

Communication Support Services internal error.

通信支持服务内部错误。

Contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件和用于客户端和数据库服务器的 sqlhost 信息。

-14574 CSS: error processing initialization string: .

Communication Support Services could not get access to a Communications Support Module configuration provided by a Communication Support Services caller.

通信支持服务无法访问通信支持服务调用方提供的通信支持模块配置。

Check whether concsm.cfg exists. Check the configuration file, and the CSM option field in the sqlhosts file. If the problem persists,contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration file (concsm.cfg)and sqlhosts information for both the client and the database server.

检查是否存在 consm.cfg。检查配置文件和 sqlhost 文件中的 CSM 选项字段。如果问题仍然存在，请与 GBase 技术支持部门或 CSM 供应商联系，并提供以下可用信息：CSS 配置文件(consm.cfg)和用于客户端和数据库服务器的 sqlhost 信息。

-14575 CSS: invalid run-time parameters.

There is an error in the CSS configuration file (concsm.cfg).

CSS 配置文件(consm.cfg)中有一个错误。

Check CSS configuration file, and the CSM option field in the sqlhosts file. If the problem persists, contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files (concsm.cfg) and sqlhosts information for both the client and the database server.

检查 CSS 配置文件和 sqlhost 文件中的 CSM 选项字段。如果问题仍然存在，请与GBase Technology Support 或 CSM 供应商联系，并提供以下信息：CSS 配置文件(consm.cfg)和用于客户端和数据库服务器的 sqlhost 信息。

-14576 CSS: null CSS context.

Communication Support Services internal error.

通信支持服务内部错误。

Communication Support Services caller passed a null context to Communication Support Services.

通信支持服务调用方将空上下文传递给通信支持服务。

Contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files (concsm.cfg)and sqlhosts information for both the client and the database server.

请联系 GBase 技术支持或 CSM 供应商，并提供以下信息：CSS 配置文件(consm.cfg)和用于客户机和数据库服务器的 sqlhost 信息。

-14577 CSS: no registered output buffer owner.

Communication Support Services internal error.

通信支持服务内部错误。

请联系 GBase 技术支持或 CSM 供应商，并提供以下信息：CSS 配置文件(consm.cfg)和用于客户机和数据库服务器的 sqlhost 信息。

-14578 CSS: null output buffer owner.

Communication Support Services internal error.

通信支持服务内部错误。

请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件(consm.cfg)和用于客户端和数据库服务器的 sqlhost 信息。

-14579 CSS: unspecified buffer type.

Communication Support Services internal error.

通信支持服务内部错误。

请联系 GBase 技术支持或 CSM 供应商，并提供以下信息：CSS 配置文件(consm.cfg)和用于客户机和数据库服务器的 sqlhost 信息。

-14581 CSS: CSM descriptor: syntax error.

The Communications Support Module descriptor contains a syntax error.

通信支持模块描述符包含语法错误。

Check the Communications Support Module descriptor in the concsm.cfg file. If the problem persists, contact GBase Technical Support or the CSM vendor and have the following information available: CSS configuration files (concsm.cfg) and sqlhosts information for both the client and the database server.

请检查 consm.cfg 文件中的通信支持模块描述符。如果问题仍然存在，请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件(consm.cfg)和用于客户端和数据库服务器的 sqlhost 信息。

-14582 CSS: CSM descriptor: CSM redefinition.

A Communications Support Module with this name has already been defined.

已经定义了具有此名称的通信支持模块。

Check CSS configuration file, and the CSM option field in the sqlhosts file.

检查 CSS 配置文件和 sqlhost 文件中的 CSM 选项字段。

-14583 CSS: CSM descriptor: CSM not defined.

The cascade descriptor refers to a Communications Support Module that is not defined.

级联描述符指未定义的通信支持模块。

Check CSS configuration file, and the CSM option field in the sqlhosts file.

检查 CSS 配置文件和 sqlhost 文件中的 CSM 选项字段。

-14584 CSS: CSM descriptor: link method undefined.

Communication Support Services internal error.

通信支持服务内部错误。

请联系 GBase 技术支持或 CSM 供应商，并提供以下信息：CSS 配置文（concsm.cfg）和用于客户机和数据库服务器的 sqlhost 信息。

-14585 CSS: CSM descriptor: unknown error Communication Support Services internal error.

通信支持服务内部错误。

请联系 GBase 技术支持或 CSM 供应商，并提供以下信息：CSS 配置文（concsm.cfg）和用于客户机和数据库服务器的 sqlhost 信息。

-14586 CSS: CSM descriptor: nameless CSM!A Communications Support Module descriptor does not specify the Communications Support Module name.

通信支持模块描述符没有指定通信支持模块名称。

Check CSS configuration file, and the CSM option field in the sqlhosts file.

请检查 CSS 配置文件，以及 sqlhost 文件中的 CSM 选项字段。

-14587 CSS: CSM descriptor : .

Cascade descriptor recursively refers to itself.

级联描述符递归地引用自身。

Check CSS configuration file, and the CSM option field in the sqlhosts file.

请检查 CSS 配置文件，以及 sqlhost 文件中的 CSM 选项字段。

-14588 CSS: CSM descriptor : CSM link type undefined.

Communications Support Module library name is not specified.

未指定通信支持模块库名。

Check CSS configuration file, and the CSM option field in the sqlhosts file.

请检查 CSS 配置文件，以及 sqlhost 文件中的 CSM 选项字段。

-14589 Cannot open configuration file.

Check whether the CSS configuration file exists.

检查 CSS 配置文件是否存在。

-14590 CSS: failed to acquire sync object.

Communication Support Services internal error.

通信支持服务内部错误。

请与 GBase 技术支持或 CSM 供应商联系，并提供以下信息：CSS 配置文件(concsm.cfg）和用于客户端和数据库服务器的 sqlhost 信息。

-14591 CSS: failed to release sync object.

Communication Support Services internal error.

通信支持服务内部错误。

请联系 GBase 技术支持或 CSM 供应商，并提供以下信息：客户端和数据库服务器的CSS 配置文件（concsm.cfg）和 sqlhosts 信息。

-16300 Identifier is too long.

An identifier in this statement is too long for its context. Check if you have omitted a separator between two identifiers, or select a shorter identifier.

此语句中的标识符对于其上下文来说太长。检查是否省略了两个标识符之间的分隔符，或者选择较短的标识符。

-16301 A syntax error has occurred.

A syntax error has been detected in a Debugger command. Check that you have not misspelled or omitted a keyword or identifier, included an extra command argument, or placed keywords out of sequence. Check if you have omitted parentheses after a function name in a CALL command or included them in a VIEW command. To display a two-page synopsis of all the commands, enter help all.

在调试器命令中检测到语法错误。检查是否有拼错或省略关键字或标识符，是否包含额外的命令参数，或者是否按顺序排列了关键字。检查 CALL 命令中的函数名称后面是否省略了括号，或将它们包含在 VIEW 命令中。要显示所有命令的两页大纲，请输入 help 。

-16302 An illegal character has been found in the command.

Characters in Debugger commands are restricted to letters, numbers,blanks, underscores, and the special characters that are listed in the section "Conventions for Command Syntax Notation" in the Debugger manual. You might have pressed a key inadvertently, or you might have introduced illegal characters when you edited a file that provided input to a READ command. If you create or modify a .4db file with a word-processing program, be sure to save it in nondocument or text-only mode.

调试器命令中的字符只能包含字母、数字、空格、下划线和 Debugger 手册中“命令语法表示法约定”一节中列出的特殊字符。您可能无意中按下了一个键，或者您在编辑一个文件时可能引入了非法字符，该文件为 Read 命令提供了输入。如果使用文字处理程序创建或修改 .4db 文件，请确保将其保存为非文档或纯文本模式。

-16303 An illegal integer has been found in the command.

Your expression or search pattern includes a numeric string of more than 50 characters. Repeat the command, specifying a shorter expression or search pattern.

您的表达式或搜索模式包括一个浮点数字字符串，该字符串超过50个字符。

重复该命令，指定较短的表达式或搜索模式。

-16304 An illegal floating point number has been found in the command.

Your expression or search pattern includes a floating-point numeric string of more than 50 characters or includes more than one decimal point. Repeat the command, specifying a shorter expression or search pattern, or fewer decimal points.

您的表达式或搜索模式包括一个浮点数字字符串，该字符串超过50个字符，或包含多个小数点。

重复命令，指定较短的表达式或搜索模式，或更少的小数点。

-16305 Memory allocation failed.

Not enough system memory is available to execute your command. Repeat the command at another time, when other users are making smaller demands on system memory. On DOS systems, you will need to free some disk space.

没有足够的系统内存可用于执行命令。当其他用户对系统内存提出较小的要求时，请在另一个时间重复该命令。在 DOS 系统上，您需要释放一些磁盘空间。

-16306 Found a quote for which there is no matching quote.

You might have omitted a quotation mark from a name or string, or included an extraneous quotation mark. Repeat the command, using an even number of single (') or double (") quotes.

可能在名称或字符串中省略了引号，或者包含无关引号。

重复该命令，使用偶数个单引号（'）或双引号（''）。

-16307 Quoted string is too long.

The maximum length of a quoted string is 256 characters. Repeat the command with a shorter string.

带引号的字符串的最大长度是 256 个字符。用较短的字符串重复该命令。

-16308 Missing function name.

You must specify the name of a function in a CALL command. Repeat the command, specifying the name of a function followed by left and right parentheses. If the function requires arguments, include the list of arguments within the parentheses, separating multiple arguments by commas.

您必须在 CALL 命令中指定一个函数的名称。重复该命令，指定一个函数的名称，后跟左括号和右括号。如果函数需要参数，请在括号内包含参数列表，用逗号分隔多个参数。

-16309 Internal buffer limit exceeded.

Your command has too many characters. A Debugger command can include no more than 256 characters. If you are specifying an ALIAS, BREAK, or TRACE command that includes many command lines within braces, you might consider using nested aliases. You can cause a function key or a short string to stand for hundreds of keystrokes by specifying it as the alias of a list of aliases, each of which represents fewer than 256 characters. Another alternative is to use READ commands, rather than aliases, to enter multiple commands.

您的命令有太多字符。调试器命令只能包含不超过 256 个字符。如果您指定包含大括号内的许多命令行的 ALIAS、BREAK 或 TRACE 命令，则可以考虑使用嵌套别名。您可以通过将功能键或短字符串指定为别名列表的别名来代表数百个按键，每个别名的代表少于 256个字符。另一种选择是使用 READ 命令而不是别名来输入多个命令。

-16310 Keyword expected.

You have omitted a required command option. Enter help all to display the names of all the Debugger commands or refer to the manual.

您省略了必需的命令选项。输入 help all 以显示所有调试器命令的名称或参考手册。

-16311 Command name is not recognized.

You have misspelled the name of the command or improperly abbreviated it. Enter help to see a display of the names of all the Debugger commands. If the string name appears to be a valid command name, you might have also pressed a nonprinting key when you entered it.

命令的名称拼写错误或者错误缩写了它。输入 help 来查看所有调试器命令的名称显示。

如果字符串名称看起来是一个有效的命令名称，那么您在输入字符串时可能也按下了非打印键。

-16312 Missing or misplaced = sign.

The LET command always requires an equal sign (=) as does ALIAS without the asterisk option. Repeat the command and be sure to use the equal sign in the appropriate place.

LET 命令需要一个等号（=），没有星号选项的 ALIAS 也是如此。

重复该命令，并确保在适当的地方使用等号。

-16313 Missing module line number.

In a BREAK or TRACE command, you specified the name of a module,followed by a dot, followed by a noninteger. The module name must be followed by a dot and a line number that is an integer.

在 BREAK 或 TRACE 命令中，指定了模块的名称，后面跟着一个点，之后跟着一个非整数。

模块名称后面必须跟一个点号和一个整数的行号。

-16314 Missing filename.

If the Debugger is already loaded, you have not specified a filename after a READ command or after a command to redirect output to a file.

Repeat the command, specifying the name of an input or output file.

如果已经加载了调试器，则在 READ 命令之后或在将输出重定向到文件的命令之后，没有指定文件名。重复该命令，指定输入或输出文件的名称。

If you were at the system prompt, you used the -F command-line option to invoke the Debugger, but you did not specify the name of an initialization file. Repeat the command, but this time either omit the-F option or specify the name of a .4db initialization file following the -F option.

如果在系统提示符处，则使用 -F 命令行选项来调用 Debugger，但是没有指定初始化文件的名称。

重复该命令，但是这次要么省略 -F 选项，要么在 -F 选项后面指定一个 .4db 初始化文件的名称。

-16315 Missing ).

Either you omitted a right parenthesis from a command argument, or you included a superfluous left parenthesis.

命令参数中省略了右括号，或者包含了多余的左括号。

-16316 A small integer is expected.

You must supply a positive or negative integer as an argument of a GROW command. Repeat the command, specifying the number of lines to be added to the size of the window. The sum of this integer and the current size must be in the range from 1 to L-6, where L is the number of lines that your terminal can display (often 24).

您必须提供一个正整数或负整数作为 GROW 命令的参数。重复该命令，指定要添加到窗口大小的行数。

此整数和当前大小之和必须在 1 到 L-6 的范围内，其中 L 是终端可显示的行数（通常为 24）。

-16317 Program variable name expected.

A Debugger LET command requires three arguments:Debugger LET 命令需要三个参数：* The identifier of a program variable程序变量的标识符* An equal sign (=)一个等号（=）* An expression whose value is assigned to the variable给该变量的赋值的表达式The identifier could not be recognized in the command that you entered.

无法在您输入的命令中识别标识符。

-16318 Positive number or name expected.

The ENABLE, DISABLE, NOBREAK, and NOTRACE commands all require an argument. This argument can be a breakpoint or tracepoint name,reference number, function name, or the ALL option. If the argument that you entered in the Command window looks valid, you might have also pressed a nonprinting key.

ENABLE、DISABLE、NOBREAK 和 NOTRACE 命令都需要参数。该参数可以是断点或跟踪点名称、引用数、函数名称或 ALL 选项。如果您在“命令”窗口中输入的参数看起来有效，那么可能按了非打印键。

-16319 Internal error - illegal command.

This message reflects an unexpected condition in the command-parsing module of the Debugger. If the error recurs, note all circumstances and contact GBase Technical Support.

该消息反映了调试器的命令解析模块中的意外情况。如果错误再次出现，请注意所有情况并联系 GBase 技术支持。

-16320 Missing left brace.

You must use left and right brace characters ({ and }) in balanced pairs.

必须使用一对左大括号和右大括号({和})。

-16321 Alias alias-name is an existing command keyword.

The name of an alias cannot be the complete form of a Debugger command. (However, you can assign an abbreviated form of a command keyword as an alias.) Repeat the command using another alias identifier.

别名的名称不能是 Debugger 命令的完整形式。但是，可以将命令关键字的缩写形式指定为别名。

使用另一个别名标识符重复该命令。

-16322 Missing directory list.

You used the -I command-line option when you invoked the Debugger, but you did not specify a source-file search path. Repeat the command, and either omit the -I option or specify a search path with it.

您在调用 Debugger 时使用了 -I 命令行选项，但未指定源文件搜索路径。

重复该命令，省略 -I 选项或指定一个搜索路径。

-16323 User cannot specify more than one directory list.

You can use the -I option only once on the command line. However, you can specify more than one search path in the list following -I. Repeat the command, listing all the desired source-file search paths,separated by commas, following a single -I option.

您只能在命令行上使用 -I 选项一次。但是，您可以在 -I 之后的列表中指定多个搜索路径。

重复这个命令，列出所有所需的源文件搜索路径，用逗号分隔，后面跟着一个 -I 选项。

-16324 User cannot specify more than one file name.

You can use the -F option only once on the command line. Repeat the command specifying only one initialization file. After the Debugger starts, you can enter READ commands to execute additional .4db files.

您只能在命令行上使用 -F 选项一次。重复命令，只指定一个初始化文件。

Debugger 启动后，可以输入 READ 命令来执行额外的 .4db 文件。

-16325 Missing or extra parameter.

You omitted or repeated a command-line option. Repeat the command after you check the description of the fgldb command in the Debugger manual.

您省略或重复了一个命令行选项。在检查调试器手册中 fgldb 命令的描述后，重复该命令。

This message also appears if you attempt to pass parameters to the program that is being debugged. The correct way to give command-line parameters to the subject program is to include them with the run command when you start the program.

如果您尝试将参数传递给正在调试的程序，也会出现此消息。将命令行参数提供给主程序的正确方法是：在启动程序时将它们包含在运行命令中。

-16326 Missing program name.

If you invoke the Debugger at the system prompt, you must include as an argument the name of a compiled 4GL program (or else, in UNIX, use the option -V to indicate that you want a display of only the software version number). Repeat the command, specifying the name of a compiled program this time.

如果您在系统提示符下调用 Debugger ，则必须包含一个已编译的 4GL 程序的名称作为参数（或者，在 UNIX 中，使用选项 -V 指示您只需显示软件版本号）。重复该命令，指定一个编译完成的程序的名称。

-16327 Cannot locate file filename.

Possibly you omitted or misspelled the filename of a .4db input file(either in a READ command or following the -F command-line option), or you misspelled the filename or pathname of a .4gl source file in a VIEW command or on the command line.

可能您省略或拼错了 .4db 输入文件的文件名（无论是在 READ 命令中还是在 -F 命令行选项后面），或者在 VIEW 命令中或命令行中错误拼写了 .4gl 源文件的文件名或路径名。

If filename is spelled correctly and names a file that exists, then you might need to specify a complete pathname. You must specify the full pathname of a file when you refer to a .4db file that is not in the current directory, or to a .4gl source file that is not in the current directory or any directory that you specify with the-I command-line option.

如果 filename 拼写正确，并命名的文件存在，那么可能需要指定完整的路径名。

当引用不在当前目录中的 .4db 文件或不位于当前目录或使用 -I 命令行选项指定的任何目录中的 .4gl 源文件时，必须指定文件的完整路径名。

-16328 Cannot read initialization file filename.

Although the Debugger found the file that you specified with the -F parameter, it encountered an error when it tried to read from the file. Check for operating-system error messages that might provide more details. If the problem is not a hardware error, make sure that your account has read access to the file (for instance, by displaying its contents).

虽然 Debugger 找到了使用 -F 参数指定的文件，但它在尝试从文件读取时遇到错误。

检查可能提供更多详细信息的操作系统错误消息。如果问题不是硬件错误，请确保您的账户具有对文件的读取权限（例如，可以显示内容）。

-16329 Pathname too long.

The Debugger will accept pathnames of up to 70 characters.

Debugger 接受多达 70 个字符的路径名。

-16330 Cannot open file filename for reading.

Make sure that you specified the correct filename in your READ or VIEW command, or after the -F option when you invoked the Debugger from the command line. If the name was correct, the file might be damaged or read protected. If you do not have permission to read it, refer to the discussion of access privileges in your operating-system documentation,or contact your system administrator.

确保在 READ 或 VIEW 命令中指定了正确的文件名，或者在从命令行调用 Debugger 时，指定了 -F 选项。如果名称正确，则文件可能已损坏或读取保护。如果您无权读取它，请参阅操作系统文档中有关访问权限的讨论，或与系统管理员联系。

-16331 Too many recursive aliases.

In some debugging tasks, aliases that reference other aliases can save time or circumvent limits on the number of characters in a Debugger command line. For example, you can specify alias1 to be a substring of alias2, which can be a substring of alias3, and so forth up to alias5.

However, you cannot specify more than five levels of aliases between your keystrokes and the fully expanded commands for which they stand.

在一些调试任务中，引用其他别名的别名可以节省时间或规避调试器命令行中字符数量的限制。

例如，您可以将 alias1 指定为 alias2 的子字符串，该字符串可以是 alias3 的子字符串等等直到 alias5 。但是，但是，您不能在击键和它们所代表的完全展开的命令之间指定超过五个别名级别。

-16332 Duplicate function name function-name.

The function name shown was found in a module that was being loaded.

However, a function of that name had already been seen in a module that was loaded earlier. This situation is not allowed. Change the application so that all functions in it have unique names.

所显示的函数名称位于正在加载的模块中。但是，在早期加载的模块中已经看到了该名称函数。

这种情况是不允许的。更改应用程序，使其中的所有函数都有唯一的名称。

-16333 Duplicate module name module-name.

The module whose name is shown is being loaded, but a module of that name had already been loaded. Use the Program menu of the Programmer's Environment to make sure that the program that is being debugged is composed of only one copy of each module.

显示其名称的模块正在加载，但该名称的模块已经加载。使用程序员环境的“程序”菜单，确保正在调试的程序仅由每个模块的一个副本组成。

-16334 Internal error - null keyword encountered.

This message reflects a condition that was expected never to occur. If the error recurs, note all circumstances and contact GBase Technical Support.

此消息反映了一种预期永远不会发生的情况。如果错误再次发生，请注意所有情况，并与 GBase 技术支持部门联系。

-16335 Window can't be adjusted by number of lines specified.

The minimum number of lines in the Source window or in the Command window one, not counting the Source window line that displays the current module name. On a standard 24-line terminal, the maximum number of lines in either window is 18, or L-6 where L is the number of lines that the terminal supports.

源窗口或命令窗口中的最小行数，不包括显示当前模块名称的源窗口行。在标准 24 行终端上，任一窗口中的最大线路数为 18 或 L-6，其中 L 是终端所支持的行数。

The argument of a GROW command is not the new window size but the increment to the current window size. To change the size of a window in the Debugger screen, enter a GROW command to produce window sizes within this range.

GROW 命令的参数不是新窗口大小，而是当前窗口大小的增量。若要更改调试器屏幕中窗口大小，请输入 GROW 命令以此范围内生成窗口大小。

-16336 User must specify source file to view.

The VIEW command requires the name of a 4GL source file.

VIEW 需要一个 4GL 源文件名称。

-16337 No previous search pattern.

You cannot enter a Search command without specifying a search pattern,unless earlier in the same debugging session you specified a search pattern. Repeat the command, specifying a valid search pattern.

如果不指定搜索模式，则无法输入搜索命令，除非在同一调试会话的前面指定了搜索模式。

重复命令，指定有效的搜索模式。

-16338 Cannot continue execution.

You cannot invoke CONTINUE or STEP commands unless a 4GL program has begun (but not terminated) execution. If the program is terminated normally or by a fatal error, use CALL or RUN. After execution begins,you must then suspend execution by a breakpoint (or, in UNIX environments, by an Interrupt command) before you can invoke CONTINUE or STEP. See also the section on "Active Functions and Variables" in the Debugger manual.

除非 4GL 程序开始（但未终止）执行，否则不能调用 CONTINUE 或 STEP 命令。

如果程序正常终止或由于致命错误终止，请使用 CALL 或 RUN。开始执行后，必须通过断点暂停执行（或者在 UNIX 环境中，通过中断命令暂停），然后才能调用CONTINUE 或 STEP 。另请参见“调试器”手册中的“主函数和变量”部分。

-16339 Break or trace name name is not unique.

A name that you assign to a breakpoint or tracepoint in a BREAK or TRACE command cannot duplicate the name of any existing reference point(including disabled breakpoints or tracepoints). This message will also appear after a READ command that sets a named breakpoint or tracepoint if you read the same input file twice.

您在 BREAK 或 TRACE 命令中分配给断点或跟踪点的名称不能与现有的参考点重复（包括禁用的断点或跟踪点）。如果您两次读取相同的输入文件，该消息还将出现在一个 READ 命令之后，该命令设置一个指定的断点或跟踪点。

-16340 Invalid backslash encountered.

Your command includes a backslash symbol that cannot be interpreted as a command-line continuation symbol. Repeat the command without invalid backslashes.

您的命令包含一个不能被解释为命令行继续的反斜杠符号。重复该命令，不要使用无效的反斜杠。

-16341 Line number line-number not in specified module.

Your BREAK or TRACE command cannot specify a line number that is greater than the line number of the last executable statement in the specified module. If you specified no module name, the line number cannot be greater than the last executable statement in your current module. Check that you specified the correct module and line number.

BREAK 或 TRACE 命令不能指定大于指定模块中最后一个可执行语句的行号的行号。

如果未指定模块名称，则行号不能大于当前模块中的最后一个可执行语句。检查是否指定了正确的模块和行号。

-16342 Internal error - cannot set breakpoint.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次出现，请注意所有情况并联系 GBase 技术支持。

-16343 Invalid module name module-name specified.

You specified a module that is not part of the current 4GL program.Possibly you misspelled the name, or you are confusing the names of modules or functions from different programs. Repeat the command, specifying a valid name.

您指定了不属于当前 4GL 程序的模块。可能是拼错了名称，或者混淆了不同程序中模块或函数的名称。重复该命令，指定一个有效的名称。

-16344 Invalid function name function-name specified.

You specified a function that is not part of the current 4GL program.

Possibly you misspelled the name, you are confusing the names of modules or functions from different programs, or you neglected to compile a program module that contains this function. Repeat the command, specifying a valid name.

您指定了不属于当前 4GL 程序的函数。可能是拼错了名称，或者混淆了不同程序中模块或函数的名称。或者忽略编译包含此函数的程序模块。重复该命令，指定一个有效的名称。

-16345 Cannot set breakpoint in 4GL library function or user C function.

You can set a breakpoint only at a function written in 4GL, not at a function that is written in another language such as C or ESQL/C, and not at the name of a built-in function.

您只能在使用 4GL 语言编写的函数中设置断点，而不是在用 C 或 ESQL/C 等其他语言编写的函数中设置断点，也不能以内置函数的名称设置断点。

To suspend program execution when a C function is called, set a breakpoint by specifying the line number of the 4GL statement that calls the C function, rather than specifying the name of the function.

若要在调用 C 函数时暂停程序执行，请通过指定调用 C 函数的 4GL 语句的行号来设置断点，而不是指定函数的名称。

-16346 Cannot open output file filename.

Check if the output file already exists but is damaged or write protected. In UNIX, check that you have permission to write in the specified directory (or in the current directory if you specified no pathname).

检查输出文件是否已经存在但已损坏或写保护。在 UNIX 中，请检查是否有权写入指定的目录（如果未指定任何路径名，则是在当前目录中）。

-16347 Invalid breakpoint or tracepoint number or reference name specified.

You cannot specify a reference number in an ENABLE, DISABLE, NOBREAK,or NOTRACE command with a zero or negative value, or a value for which no corresponding breakpoint or tracepoint currently exists. You can enter list break trace to display your current reference numbers.

您不能在 ENABLE、DISABLE、NOBREAK 或 NOTRACE 命令中指定具有零值或负值的参考号，或者当前不存在的断点或跟踪点的值。您可以输入列出断点跟踪来显示当前的参考号码。

-16348 Breakpoint or tracepoint name is not active.

You asked the DISABLE command to deactivate a breakpoint that is already disabled. Check that you named the breakpoint that you intended. You can enter list break trace to display your current breakpoints and tracepoints.

您要求 DISABLE 命令停用已禁用的断点。检查是否命名了想要的断点。您可以列出断点跟踪来显示当前的断点和跟踪点。

-16349 Use nobreak for breakpoints and notrace for tracepoints.

You specified a breakpoint to the NOTRACE command or a tracepoint to the NOBREAK command. Each command can deal only with its own objects.

您为 NOTRACE 命令或 NOBREAK 命令的跟踪点指定了断点。每个命令只能处理它自己的对象。

-16350 Breakpoint/tracepoint already disabled/enabled or can't be determined.

The Debugger cannot find a corresponding breakpoint or tracepoint on which to carry out your ENABLE or DISABLE command. You can enter list break trace to display all your current reference points.

Debugger 无法找到执行 ENABLE 或 DISABLE 命令的相应断点或跟踪点。

您可以列出断点跟踪来显示当前的所有参考点。

-16351 Variable variable-name could not be located.

The Debugger cannot reference a variable unless it is defined in a 4GL module. For 4GL variables, check that you entered the variable name correctly. If the variable is not in the current function or module,you must qualify its name. See the section on "Scope of Reference" in the Debugger manual. (This message can appear if you enter what you intend to be a module name in a BREAK or TRACE command, but you omit the dot at the end of the name.)除非在4GL模块中定义 Debugger，否则不能引用变量。对于 4GL 变量，请检查您是否正确输入了变量名称。如果该变量不在当前函数或模块中，则必须具有限定名。请参阅“调试器”手册中“参考范围”一节。（如果在 BREAK 或 TRACE 命令中输入您想要作为模块名称的内容，但省略了名称末尾的点，则会出现此消息。）-16352 File filename has been modified. (.4gl is newer than .4go).

The Debugger executes the .4go module, but it displays lines from the.4gl source file. Because the source file has been changed since the module was compiled, the lines that the Source window displays might not correspond to the statements in the compiled program.

Debugger 执行 .4go 模块，但它显示 .4gl 源文件中的行。由于源文件自编译模块以来已更改，“源”窗口显示的行可能与编译的程序中的语句不符。

If you change the source code in a .4gl file, you must recompile it. If your program includes several modules, you must also concatenate the compiled modules before you start debugging. Also check if files exist with both the .4go and .4gi suffixes for this program. Even if your.4go file is the appropriate recompiled version, the Debugger first attempts to interpret the .4gi version.

如果更改 .4gl 文件中的源代码，则必须重新编译它。如果程序包含多个模块，则在开始调试之前，还必须连接已编译的模块。同时检查文件是否存在该程序的 .4go 和 .4gi 后缀。即使.4go 文件是合适的重新编译版本，调试器也会首先尝试解释 .4gi 版本。

-16353 Executable command is invalid when executing tracepoint commands.

The list of command lines in your TRACE command includes a CALL,CONTINUE, RUN, or STEP command. These commands are not supported within a TRACE command.

TRACE 命令中的命令行列表包括 CALL、CONTINUE、RUN 或 STEP 命令。这些命令在 TRACE命令中不受支持。

-16354 Function function-name not found.

You specified a function that is not part of the current 4GL program.

Check if you have misspelled the name or if you are confusing the names of functions from different programs. Make sure that your 4GL source code defines and calls the function that you want to execute.

您指定了一个不属于当前 4GL 程序的函数。检查您是否拼写错了名称，或者是否混淆了不同程序中函数的名称。确保 4GL 源代码定义并调用了想要执行的函数。

-16355 Function function-name requires parameters.

The function that the CALL command names is defined as taking one or more parameters. You must enter a matching number of parameters in the parentheses following the name of the function. If you are not sure what parameters should be passed to the function, use a VIEW command to display its source code.

CALL 命令名称的函数被定义为采用一个或多个参数。您必须在函数名称后面的括号中输入匹配的参数。如果您不确定应将哪些参数传递给函数，请使用 VIEW 命令显示其源代码。

-16356 Too many parameters passed to function function-name.

Your argument list in a CALL command includes more parameters than the function is defined as receiving. If you are not sure how many parameters should be passed to the function, you can use a VIEW command to display the source code of the function.

CALL 命令中的参数列表包含的参数多于该函数定义中要接收的参数。如果不确定应传递多少个参数给函数，则可以使用 VIEW 命令来显示该函数的源代码。

-16357 Function function-name is not active.

You can display only variables that are defined in the active function.

This variable is defined in function name, which is not active.

您只能显示活动函数中定义的变量。该变量在函数名称中定义，它没有激活。

-16358 Variable name expected.

A LET command requires as its first argument a variable name. Do not put quotes around the name.

LET 命令需要一个变量名作为其第一个参数。不要在名称周围加引号。

-16359 Cannot assign values to records; Assignments must be to record members.

A LET command can assign a value to a simple variable or to a specific member of a record, but not to a whole record.

LET 命令可以赋值给简单变量或记录的特定成员，但不能给整个记录赋值。

-16360 Cannot assign values to arrays; Assignments must be to array elements.

A LET command can assign a value to a simple variable or to a single element of an array that a subscript in brackets designates. Enter help let to see an example.

LET 命令可以将值分配给简单变量或数组的单个元素，括号中的下标表示该元素。输入 help 可以查看示例。

-16361 Invalid variable name variable-name.

The identifier variable-name is not the name of a variable. The VARIABLE command requires the name of a variable. Check the spelling of the name.

标识符变量名称不是变量的名称。VARIABLE 命令需要变量名称。检查名称的拼写。

-16362 No current function.

No current 4GL function exists if you have not yet invoked a RUN or CALL command. Even after RUN or CALL, no current function exists if execution terminated normally, rather than being stopped by a breakpoint, by an Interrupt or STEP command, or by a fatal error. Use RUN or CALL to begin or restart program execution.

如果尚未调用 RUN 或 CALL 命令，则不存在当前的 4GL 函数。即使在 RUN 或 CALL 之后，如果执行正常终止，而不是由断点、中断或 STEP 命令或致命错误所停止，则不存在当前函数。

使用 RUN 或 CALL 开始或重新启动程序执行。

-16363 Variable in function function-name is not active.

You named a variable whose value is assigned by a function that has not yet been called or by a function that has already returned. A LET or PRINT command can refer to only an active variable; that is, one global or assigned in a function that is currently executing (a function that a WHERE command lists). When you enter a CALL command, you must substitute a literal value for an expression that needs an inactive variable.

您指定了一个变量，其值由尚未调用的函数或已返回的函数赋值。LET 或 PRINT 命令只能引用一个活动变量；即一个全局或在当前正在执行的函数中分配的一个变量（WHERE 命令列出的函数）。输入 CALL 命令时，必须用文字值替换需要非活动变量的表达式。

-16364 Unknown option option.

The Debugger cannot identify an argument option in your command. Repeat the command, specifying option differently. Enter help turn to display the many options of TURN.

Debugger 无法在您的命令中识别参数选项。重复该命令，使用不同方式指定选项。

输入 help 转到显示 TURN 的许多选项。

-16365 Breakpoint or tracepoint name is already active.

The ENABLE command has no effect on breakpoints or tracepoints that are already enabled. Check that you entered the name or reference number that you intended. If you did, and you still feel that name should have been inactive, use list break trace or search the command buffer to see if a previous DISABLE command deactivated the wrong breakpoint or tracepoint.

ENABLE 命令对已经启用的断点或跟踪点没有影响。检查是否输入了您想要的名称或参考号码。

如果您这样做了，并且您仍然认为名称应该是不活动的，请使用列表中断跟踪或搜索命令缓冲区来查看以前的 DISABLE 命令是否禁用了错误的断点或跟踪点。

-16366 Error occurred while trying to write to a file.

Either your file system is full, or a hardware error occurred. Use the Escape feature to display the space that remains on your current drive.

文件系统已满，或发生硬件错误。使用 Escape 功能显示当前驱动器上剩余的空间。

-16367 Need to specify a specific record member or array element.

You cannot use the name of an array as an argument of a CALL command.

You cannot use the unqualified name of an array or record in an expression or as the object of a breakpoint or tracepoint. In all these cases, you must use a subscript in brackets to specify a particular array element, or the full name of a member of a record.

不能将数组的名称作为 CALL 命令的参数。不能在表达式中使用数组或记录的非限定名称，也不能将其用作断点或跟踪点的对象。在所有这些情况下，必须在括号中使用下标来指定特定的数组元素或记录成员的全名。

-16368 Expression contains variables from different functions.

You cannot combine variables from different functions in the same expression. If you need to know the value of such an expression, you must use PRINT to evaluate the variables from each function separately.

Then enter these values as constants in the BREAK, LET, or PRINT command in place of the names of the variables.

不能在同一个表达式中组合来自不同函数的变量。如果需要知道此类表达式的值，则必须使用PRINT 计算每个函数中的变量。然后以常量的形式输入这些值，以代替变量的名称，在 BREAK、LET 或 PRINT 命令中输入这些值。

-16369 Cannot initialize application device device-name.

You must specify the name of another terminal that has the same termcap or terminfo entries as the terminal from which you invoked the Debugger. The second terminal must be logged in under your account name.

您必须指定另一个终端的名称，该终端具有与调用 Debugger 的终端相同的termcap 或 terminfo。第二个终端必须以您的账户名登录。

-16370 No application device specified.

You must specify the name of another terminal that has the same termcap or terminfo entries as the terminal from which you invoked the Debugger. (However, it cannot be the name of the device from which you invoked the Debugger.) Enter tty from the terminal that you want to use as your application device. Its screen will display its terminal pathname. Repeat the APPLICATION DEVICE command, specifying an appropriate terminal device name.

您必须指定另一个终端的名称，该终端具有与调用 Debugger 的终端相同的 termcap或 terminfo。（但是，它不能是您调用 Debugger 的设备的名称）从要用作应用程序设备的终端输入 tty。它的屏幕将显示其终端路径名。重复 APPLICATION DEVICE 命令，指定一个适当的终端设备名称。

-16371 Read file not specified.

You must specify the name of a .4db file in a READ command.

必须在 READ 命令中指定一个 .4db 文件的名称。

-16372 Variable or expression expected.

You must identify what you want the Debugger to display in a PRINT command. Repeat the command, specifying the name of a variable, record or array, or an expression.

必须标识希望调试器在 PRINT 命令中显示的内容。重复命令，指定变量、记录或数组或表达式的名称。

-16373 Cannot print or make assignments before execution has started.

You cannot use a LET command to assign a value to a variable, or a DUMP or PRINT command to display information about a variable or function until after execution starts. The same restriction applies after execution has terminated normally or after a CLEANUP command. Invoke the RUN or CALL command to begin execution and then repeat the command. (You might have to set a breakpoint or, in UNIX, press the Interrupt key to prevent normal termination.)在开始执行之前，不能使用 LET 命令将值分配给变量，也不能使用 DUMP 或 PRINT 命令显示有关变量或函数的信息。同样的限制适用于执行正常终止或 CLEANUP 命令后。调用RUN 或 CALL 命令开始执行，然后重复该命令。（可能必须设置断点，或者在 UNIX 中按下中断键以防止正常终止。）-16374 Break command contains 'if' without having a condition specified.

An expression must follow the IF keyword in a BREAK command. The breakpoint has no effect while the condition is false (zero). Repeat the command without IF, or with IF and a condition.

在 BREAK 命令中表达式必须跟在 IF 关键字后面。当条件为假（零）时，断点不起作用。

重复命令，不使用 IF，或使用 IF 和条件。

-16375 Cannot view C-library function function-name.

The VIEW command cannot display the source code of C functions or ESQL/C functions. To examine C source code, you must use the Escape feature and use an operating-system command that displays the C source file.

VIEW 命令不能显示 C 函数或 ESQL/C 函数的源代码。要检查 C 源代码，必须使用 Escape功能和使用显示 C 源文件的操作系统命令。

-16376 Break or trace name name does not begin with an alpha character.

The first character in the name of a breakpoint or of a tracepoint must be a letter. The subsequent characters can be letters, numbers, or underscores ( _ ). Single apostrophes ( ' ) or double-quote characters( " ) must enclose the name. Repeat the command, specifying a valid name enclosed in quotes.

断点名称或跟踪点名称中的第一个字符必须是字母。后续字符可以是字母、数字或下划线（_），使用单引号（'）或双引号字符（"）括起名称。重复该命令，指定用引号括起来的有效名称。

-16377 Cannot retrieve values of global variables before execution begins.

A PRINT command cannot display the value of a global program variable until after execution begins. Invoke the RUN or CALL command to begin execution and then repeat the PRINT command. In this situation, you can specify constants or the names of global variables as arguments of CALL. (You might have to set a breakpoint or press the Interrupt key to suspend the program before normal termination.)PRINT 命令在执行开始之后才能显示全局程序变量的值。调用 RUN 或 CALL 命令开始执行，然后重复 PRINT 命令。在这种情况下，可以指定常量或全局变量的名称作为 CALL 的参数。

（在正常结束之前，您可能必须设置断点或按中断键暂停程序。）-16378 A small positive integer is expected.

You cannot enter a TIMEDELAY command without an argument, or with a negative number as the argument. Repeat the command, specifying zero or a positive integer as the number of seconds delay in the Source window or Command window.

不能输入没有参数的 TIMEDELAY 命令，或者输入负数作为参数。

重复该命令，指定零或正整数作为源窗口或命令窗口中的秒数延迟。

-16381 Cannot set breakpoint or tracepoint - no current module.

You cannot set a breakpoint or tracepoint without referencing a module or function unless a program module is in the Source window. You probably ignored an error message that appeared when you were unable to load a 4GL source file.

除非程序模块在源窗口中，否则不能在不引用模块或函数的情况下设置断点或跟踪点。

您可能忽略了无法加载 4GL 源文件时出现的错误消息。

-16382 Command file filename is currently being processed.

You used a READ command, either nested in an initialization file or in the input file of another READ command, that refers to one of the following:您使用了 READ 命令，它嵌套在初始化文件中或另一个READ命令的输入文件中，它指向以下之一：* To itself它本身* To a previous READ command input file到先前的 READ 命令输入文件* To a .4db initialization file that has not yet completed execution到尚未完成执行的 .4db 初始化文件You cannot execute a READ command that might create an infinite loop.

您不能执行可能会创建无限循环的 READ 命令。

-16383 Number of nested read commands limit exceeded.

You started a READ command that invoked another, which invoked another,and so on for more than ten nested READ commands. You must simplify your arrangement of .4db command files.

您启动了另一个 READ 命令，该命令调用另一个命令，以此类推，对超过十个嵌套的 READ 命令，必须简化 .4db 命令文件的排列。

-16384 Line in .4db file exceeds maximum length.

You cannot have more than 256 characters in a single Debugger command line. If you are using semicolon (;) command separators, break the line into separate commands.

单个调试器命令行中的字符数不能超过 256 个。如果使用分号（;）命令分隔符，请将该行分割为单独的命令。

Avoid Debugger commands that have more characters in a single line than your screen or list device can display. Use the backslash continuation symbol to divide long command lines into shorter segments, or use aliases.

避免 Debugger 命令在一行中显示的字符数超过屏幕或列表设备所显示的字符数。

使用反斜杠连续符号将长命令行划分为较短的段，或使用别名。

-16385 Call to function function-name failed.

The logic in your 4GL or C language function might be defective or might not support the argument list that you specified in a CALL command. Use the VIEW command to examine the source code of a 4GL function. Use the Escape feature to examine the source file of a C function.

4GL 或 C 语言函数中的逻辑可能有缺陷，或者可能不支持您在 CALL 命令中指定的参数列表。

使用 VIEW 命令检查 4GL 函数的源代码。使用 Escape 功能检查 C 函数的源文件。

-16386 Search string exceeds maximum length.

The maximum length of a search pattern specification whose first character is a quote (") is 80 characters. The maximum length is 50 after any other first character. Check if you unintentionally pressed a Search command key (? or /). Repeat the Search command, but specify a shorter pattern.

第一个字符为引号（“）的搜索模式规范的最大长度为 80 个字符，在任何其他第一个字符后的最大长度为 50。检查是否无意中按下了搜索命令键（?或/）。重复搜索命令，但指定较短的模式。

-16387 Program is not currently being executed.

A WHERE command cannot display your active functions until after execution begins. Invoke the RUN or CALL command to begin execution,and then repeat the command. (You might first have to set a breakpoint to suspend execution before normal termination.) See the topic "Active Functions and Variables" in the Debugger manual.

直到执行开始之后，WHERE 命令才能显示活动函数。调用 RUN 或 CALL 命令开始执行，然后重复该命令。（您可能首先必须设置断点才能在正常终止之前暂停执行。）请参阅“调试器”手册中的“主动函数和变量”。

-16388 Cannot create Debugger window.

You are probably out of memory. Take whatever steps your operating system permits to increase the amount of available memory.

可能内存不足。采取您的操作系统允许的任何步骤来增加可用的内存量。

-16389 File name exceeds maximum length.

A filename cannot exceed 80 characters. If the name exceeds this length(if the message is not the result of some mistake in punctuation), you must rename it before you use it with the Debugger.

文件名不能超过 80 个字符。如果名称超出此长度（如果消息不是因为标点符号中的错误），则必须在使用 Debugger 之前对其进行重命名。

-16390 Error occurred while reading file filename.

The Debugger encountered an error while it was trying to read a 4GL source file. Look for other messages (from the operating system, for example) that provide more details about the failure. Check that the file exists and that you have read permission.

Debugger 在尝试读取 4GL 源文件时遇到错误。查找其他消息（例如来自操作系统的消息），以提供有关故障的更多详细信息。检查文件是否存在，是否具有读取权限。

-16391 Internal error - attempt to highlight invalid line number.

Repeat the command. If the error recurs, note all circumstances,and contact GBase Technical Support.

重复该命令。如果错误再次出现，请注意所有情况，并联系 GBase 技术支持。

-16392 No database name specified.

The database command requires the name of a database as its argument.

数据库命令需要数据库的名称作为其参数。

-16393 Expression or variable contains invalid substring.

The Debugger cannot interpret a reference to a substring of a character value. Two numbers in square brackets specify a substring, as in the following expression:Debugger 不能解释对字符值的子字符串的引用。方括号中的两个数字指定一个子字符串，如下面的表达式所示：charvalue[n1,n2]The name charvalue must be the CHAR(n) data type; n1 specifies the first character of the substring, and n2 specifies the last. This error message appears when n1 is larger than n, the length of the character value, or when n1 is greater than n2.

名称 charvalue 必须是CHAR(n) 数据类型;;n1 指定子字符串的第一个字符，而 n2指定最后一个字符。当 n1 大于 n、字符值的长度或当 n1 大于 n2 时，会出现此错误消息。

-16394 Cannot access the help messages.

The Debugger help messages are in the file fgldb.iem. The INSTALL program copies this file into the msg directory to which the GBS_HOME environment variable points. Probably the file was damaged,deleted, or read protected. Ask the system administrator to restore your access to it.

Debugger 帮助信息位于 fgldb.iem 文件中。INSTALL 程序将该文件复制到 GBS_HOME环境变量指向的 msg 目录中。可能文件被损坏、删除或读取保护。请系统管理员恢复您的访问权限。

-16395 Cannot compare BLOBs to any other value.

You asked the Debugger to compare a TEXT or BYTE variable in an expression. You cannot use variables of these types for comparisons.

(However, you can refer to a substring of a TEXT variable.)您要求 Debugger 在表达式中比较 TEXT 或 BYTE 变量。但是不能使用这些类型的变量进行比较。（但是，可以引用 TEXT 变量的子字符串。）-16396 Cannot use BLOBs in this expression.

You asked the Debugger to use a TEXT or BYTE variable in an expression. Variables of these types can only be displayed with PRINT or DUMP statements, or assigned null values using the LET statement.

您要求 Debugger 在表达式中使用 TEXT 或 BYTE 变量。这些类型的变量只能使用PRINT 或 DUMP 语句显示，或者使用 LET 语句分配空值。

-16397 Can print only BLOB variables with program =.

The PROGRAM = clause of the PRINT statement is used to specify an external program (for instance, a text editor) that can display the contents of a BYTE or TEXT value. The clause is not relevant with any other type of data.

PROGRAM = PRINT 语句的子句，用于指定可显示 BYTE 或 TEXT 值内容的外部程序（例如文本编辑器）。该子句与任何其他类型的数据无关。

-16398 Illegal BLOB file name. Null name not permitted.

The 4GL LOCATE statement has located the BYTE or TEXT variable in a file. However, the filename for the variable is a null string. Because the file does not exist, the Debugger cannot do anything with it.

4GL LOCATE 语句在文件中定位了BYTE 或 TEXT 变量。但是，变量的文件名是空字符串。

由于该文件不存在，调试器无法对其执行任何操作。

-16399 No program name specified.

The PROGRAM = clause of the PRINT statement is used to specify an external program (for instance, a text editor) that can display the contents of a BYTE or TEXT value. In this command, the keyword was specified, but no program name followed it.

PROGRAM = PRINT 语句的子句，用于指定可显示 BYTE 或 TEXT 值内容的外部程序。

在此命令中，指定了关键字，但没有在其后面加上程序名称。

-16400 Bad file name name.

The filename that is shown is not appropriate for its intended use. It is too long, contains improper special characters, or is null. Enter an appropriate filename.

所显示的文件名不符合预期的用途。filename 太长、或包含不正确的特殊字符、或为空。

请输入一个适当的文件名。

-16401 No program loaded.

A program was unloaded with the command UNLOAD PROGRAM, but no program was subsequently loaded with the command LOAD PROGRAM.

使用 UNLOAD PROGRAM 命令卸载程序，但是没有程序随后用 LOAD PROGRAM 命令加载。

-19800 Role name already exists as a user or role.

You cannot create a role name identical to any user that is known to the system or a user or role that is known to the database. Change the name of the role.

您无法创建与系统已知的任何用户或数据库已知的用户或角色相同的角色名称。更改角色的名称。

-19801 Role name cannot be.

You cannot create a role name that is a reserved word. The reserved words are connect, resource, dba, dbsecadm, select, update, delete, insert,index, references, alter, execute, default, none, null, and public.

Change the name of the role.

角色名称不能是一个保留字。保留字有 connect、resource、dba、dbsecadm、select、update、delete、insert、index、references、alter、execute、default、none、null和 public。请更改角色的名称。

-19802 Name cannot appear as both the role grantor and the role grantee.

A role cannot be granted to itself, either directly or indirectly.

Verify if the role grantor and grantee are the correct roles.

Check for roles already granted to the role that is being granted.

角色不能直接或间接地授予自己。验证角色授予者和被授权人是否是正确的角色。

检查已授予正在授予的角色。

-19803 Only the DBA, or a user granted the role with the WITH GRANT OPTION can grant, revoke, or drop a role.

Check your privileges and permissions. Only a DBA can grant, revoke, or drop a default role to a user.

检查您的特权和权限。只有 DBA 可以授予、撤销或删除给用户的缺省角色。

For example, a DBA can grant the default role to a user by running the following statement:例如，DBA 可以通过以下语句将缺省角色授予给用户：GRANT DEFAULT ROLE privilege TO user1;A user who is granted a role with the WITH GRANT OPTION can grant, revoke, or drop a role, optionally with the WITH GRANT OPTION to another user.

使用 WITH GRANT OPTION 授予角色的用户可以授予、撤销或删除角色，也可以使用WITH GRANT OPTION 赋予其他用户。

For example, a DBA can grant a privilege with the WITH GRANT OPTION to a user by running the following statement:例如，DBA 可以通过运行以下语句向用户授予 WITH GRANT OPTION 权限：GRANT privilege TO user1 WITH GRANT OPTION;Then that user can grant privileges to other users,for example, by running the following statements:然后，该用户可以将权限授予其他用户，例如，通过运行以下语句：GRANT privilege TO user2 WITH GRANT OPTION;GRANT privilege TO user3;However, a non DBA user cannot grant the default role to a user.

For example,the following statement fails:但是，非 DBA 用户无法将缺省角色授予用户。例如，以下语句失败：GRANT DEFAULT ROLE privilege TO usr2;-19804 The role does not exist.

For a role to exist, the DBA must first use the CREATE ROLE statement to create the role. For a list of roles, see the gbasedbt.sysusers table.

要使角色存在，DBA 必须首先使用 CREATE ROLE 语句创建角色。

有关角色列表，请参阅 gbasedbt.sysusers 表。

-19805 No privilege to set to the role.

Check your privileges and permissions. A user or role must be granted a role using the GRANT statement before the role can be set.

检查您的特权和权限。在可以设置角色之前，必须使用 GRANT 语句授予用户或角色角色。

-19806 Cannot grant database privileges or default role to a role.

A role cannot be granted database-level privileges. Use the GRANT statement to grant database-level privileges to the user or to PUBLIC.

不能授予角色数据库级别的权限。使用 GRANT 语句将数据库级别的权限授予用户或 PUBLIC 。

A default role cannot be granted to a role. Use the GRANT DEFAULT ROLE statement to grant default role to the user or to PUBLIC.

不能将缺省角色授予角色。使用 GRANT DEFAULT ROLE 语句将缺省角色授予用户或 PUBLIC。

-19807 Cannot grant privileges to a role WITH GRANT option.

A user that is granted a role with the WITH GRANT option cannot in turn grant the role to a user and include the WITH GRANT option. Use the GRANT statement without the WITH GRANT option.

被授予具有 WITH GRANT 选项的角色的用户不能反过来将该角色授予用户并包含 WITH GRANT 选项。

使用 GRANT 语句，不要使用 WITH GRANT 选项。

-19808 User name already exists as a rolename in the database.

A user cannot open a database as a role name that is the same as the user name. Role names and user names must be unique in the database. If you want to access the database, contact the DBA of the database. The DBA can drop the role if necessary.

用户无法打开数据库作为与用户名相同的角色名称。角色名称和用户名在数据库中必须是唯一的。

如果要访问数据库，请联系数据库的 DBA。如有必要，DBA 可以放弃角色。

-19809 Invalid password to access the database.

Use the correct password.

请使用正确的密码。

-19810 Cannot set database password for a role.

You can set a database password only for a user.

您只能为用户设置数据库密码。

-19811 DBpassword should not exceed 8 characters.

Choose a database password with a length that does not exceed eight characters.

选择长度不超过 8 个字符的数据库密码。

-19812 Illegal usage of replication shadow columns.

The specified operation cannot be performed on the replication shadow columns.

指定的操作无法在复制影子列上执行。

-19813 Cannot add CRCOLS when table already has replication shadow columns.

The specified table was created with the WITH CRCOLS syntax and therefore already has the replication shadow columns defined. You cannot alter this table to add CRCOLS to it.

指定的表是使用 WITH CRCOLS 语法创建的，因此已经定义了复制影子列。

不能更改此表以向其添加 CRCOLS。

-19814 Cannot drop CRCOLS when table does not have replication shadow columns.

The specified table was not created with the WITH CRCOLS syntax, or it has not been altered to include the CRCOLS. You cannot alter this table and drop the CRCOLS because these columns do not exist on this table.

指定的表不是用 WITH CRCOLS 语法创建的，也没有更改为包含 CRCOLS。

您不能更改此表并删除 CRCOLS，因为此表中不存在这些列。

-19815 Cannot create a temp table with CRCOLS.

You cannot create a temporary table to include the replication shadow columns.

不能创建包含复制阴影列的临时表。

-19816 Cannot perform this operation on a table defined for replication.

The specified operation cannot be performed on a table if Enterprise Replication is defined on the table. If you want to perform the specified operation, you must delete all replicates defined on this table.then you must use CDC API functions to stop data capture and disable full row loggiIf the table is being captured using the Change Data Capture interface,ng on the table.

如果在表上定义了 Enterprise Replication，则无法在表上执行指定的操作。如果要执行指定的操作，则必须删除此表上定义的所有复制。然后，必须使用 CDC API 函数来停止数据捕获并禁用整行 loggi 。如果表上的更改数据捕获接口 ng 正在捕获表。

-19819 An ON-clause has an invalid table reference.

One of the ON clauses that you specified refers to a table that is not within the scope of the join to which the ON clause belongs.

您指定的 ON 子句之一是指不在 ON 子句所属的连接范围内的表。

Check that the tables that you specify in the join criteria and join filters of each ON clause are applicable to the join of which they are a part.

检查您在连接条件中指定的表以及每个 ON 子句的连接过滤器是否适用于它们所属的连接。

-19820 GBase 8s OUTER JOIN and ANSI JOIN in the same query block.

You cannot have GBase 8s OUTER JOIN and ANSI JOIN in the same query block. GBase 8s OUTER JOIN and ANSI JOIN are two different mechanisms and should not be combined in a single query. You can use only one of these.

在同一查询块中不能有 GBase 8s OUTER JOIN 和 ANSI GBase 8s OUTER JOIN和 ANSI JOIN 是两种不同的机制，不应将其组合在一个查询中。您只能使用其中的一种。

-19821 Cannot rename a table using a synonym.

You cannot rename a table using a synonym. Specify the instead.

您不能使用同义词重命名表。指定代替。

If you intend to rename the synonym, then drop the existing synonym and create a new one.

如果您打算重新命名同义词，则删除现有同义词并创建一个新同义词。

-19822 Cannot alter or truncate a table or drop a table or view using a synonym.

You cannot perform an alter or drop on a table or view using a synonym. Specify the or instead.

您不能使用同义词对表格或视图执行更改或删除操作。

指定或代替。

Or, to drop or alter the table or view using the synonym, first unset the environment variable USETABLENAME.

或者，要使用同义词删除或更改表或视图，请首先取消环境变量 USETABLENAME 的设置。

If you intend to drop the synonym, specify DROP SYNONYM instead.

如果打算删除同义词，请指定 DROP SYNONYM 代替。

-19823 Cannot use EXECUTE PROCEDURE INTO with the INSTEAD OF trigger.

You cannot use EXECUTE PROCEDURE INTO with the INSTEAD OF trigger.

INSTEAD OF 触发器不能使用 EXECUTE PROCEDURE INTO。

-19824 Cannot use BEFORE or AFTER action with INSTEAD OF trigger.

You cannot use BEFORE or AFTER with the INSTEAD OF trigger. You must use FOR EACH ROW with an INSTEAD OF trigger.

INSTEAD OF 触发器不能与 BEFORE 或 AFTER 一起使用。必须与 FOR EACH ROW一起使用 INSTEAD OF 触发器。

-19825 Cannot use WHEN clause if INSTEAD OF trigger is defined.

You cannot use the WHEN clause with INSTEAD OF triggers since you cannot specify trigger restrictions for INSTEAD OF trigger statements. The trigger will always replace the specified action.

由于您无法为 INSTEAD O F触发器语句指定触发器限制，因此不能将 INSTEAD OF触发器用于 WHEN 子句。触发器将始终替换指定的操作。

-19826 Cannot create INSTEAD OF trigger for a select event.

You can create an INSTEAD OF trigger for an insert, update,or delete event, but not for a select event.

您可以为 insert、update 或 delete 事件创建 INSTEAD OF 触发器，但不能为 select 事件创建。

-19827 Cannot create an INSTEAD OF trigger on a table.

You can create an INSTEAD OF trigger on a view only and not on a base table or synonym.

您只能在视图上创建 INSTEAD OF 触发器，而不在基表或同义词上创建。

-19828 ORDER BY column or expression must be in SELECT list in this context.

You cannot omit the ORDER BY column or expression from the SELECT list in the following situations:在以下情况下，您不能忽略 SELECT 列表中的 ORDER BY 列或表达式：* The UNIQUE or DISTINCT operator is used.

使用 UNIQUE 或 DISTINCT 操作符。

* The UNION, INTERSECT, or MINUS operator is used.

使用了 UNION、INTERSECT 或 MINUS 运算符。

* The query selects into a temporary table (SELECT ... INTO TEMP).

选择到临时表的的查询（SELECT ... INTO TEMP）。

* A distributed query references a server and requires ORDER BY columns to be in the SELECT list is used.

使用分布式查询引用服务器，并要求选择列表中的 ORDERBY 列。

* The query uses the GROUP BY clause with aggregate expressions.

查询使用 GROUPBY 子句和聚集表达式。

* The expression uses an alias to a column substring.

使用列子字符串别名的表达式。

Revise the SQL statement to follow these rules.

修改 SQL 语句以遵循这些规则。

-19829 LVARCHAR column size is too big.

This statement specifies a width for a LVARCHAR column that exceeds 32,739.

Use the TEXT, BYTE or CLOB data type, which allow character strings of 2 gigabytes (TEXT or BYTE)or 4 terabytes (CLOB)for a column.

Otherwise, check the statement for typographical errors.

此语句指定超过 32,739 的 LVARCHAR 列的宽度。使用 TEXT、BYTE 或 CLOB 数据类型，它们允许字节为 2 GB（TEXT 或 BYTE）或 4 TB（CLOB）。

否则，请检查语句是否有印刷错误。

-19830 This operation is not allowed on a table where the type is raw.

An unsupported operation (for example, trying to create a constraint) was attempted on a RAW table.

试图在 RAW 表上尝试不支持的操作（例如尝试创建约束）。

You must alter the RAW table to a STANDARD table if you want to perform an operation that RAW tables do not support.

如果要执行 RAW 表不支持的操作，则必须将 RAW 表更改为 STANDARD 表。

-19831 Referential constraints are not allowed on tables of type raw.

The CREATE TABLE statement contains constraints that are not allowed for RAW tables. Check your statement to make sure you do not define these kinds of constraints on RAW tables.

This error could also occur if you try to alter a STANDARD table to RAW but the table has referential constraints.

CREATE TABLE 语句包含 RAW 表不允许的约束。检查语句，确保没有在 RAW 表上定义这些类型的约束。

如果尝试将 STANDARD 表更改为 RAW，但该表具有参照约束，也会发生此错误。

You must alter the RAW table to a STANDARD table if you want to use referential constraints.

如果要使用参照约束，则必须将 RAW 表更改为 STANDARD 表。

-19832 Cannot alter table type in combination with other alter table options.

You cannot alter the table type in combination with other ALTER TABLE options.

不能与其他 ALTER TABLE 选项组合更改表类型。

You must use separate statements to alter the table type with an ALTER TABLE statement. It cannot be done in combination with other ALTER TABLE options.

您必须使用单独的语句通过 ALTER TABLE 语句来更改表类型。它不能与其他 ALTER TABLE选项结合使用。

-19833 Table type raw not allowed together with access method.

You cannot associate a user-defined primary access method with a raw(nonlogging) table.

不能将用户定义的主访问方法与原始(非日志)表关联起来。

If you want to associate a user-defined primary access method with your table, omit the keyword RAW from the CREATE TABLE statement. If you want a raw table, omit the USING <access_method> clause from the CREATE TABLE statement.

如果要将用户定义的主访问方法与表关联，请从 CREATE TABLE 语句中省略关键字 RAW。

如果想要原始表，请从 CREATE TABL E语句中省略 USING <access_method>子句。

-19834 Error in unload due to invalid data : row number.

The column in a row that is being unloaded through an UNLOAD statement has invalid characters for the current locale settings. The output file that is specified in this UNLOAD statement has invalid data on the specified line.

对于当前语言环境设置而言，正在通过 UNLOAD 语句卸载的行中的列具有无效字符。

在此 UNLOAD 语句中指定的输出文件在指定的行上具有无效数据。

Take corrective action before you can use the unload file for loading the data back into the database. Delete or repair the row under consideration.

在使用卸载文件将数据加载回数据库之前，请采取更正措施。删除或修复所考虑的行。

-19835 Cannot create an attached index with a collation different from that of DB_LOCALE.

You cannot create an attached index when the collation set differs from that of DB_LOCALE.

当排序规则集与 DB_LOCALE 的排序规则集不同时，不能创建附加索引。

Use set collation to change the collation value to the DB_LOCALE value before attempting to create an attached index.

尝试创建附加索引之前，请设置集合以将集合值更改为 DB_LOCALE 值。

-19836 Extent size is too large. Maximum size of an extent is %sk.

The maximum size specified for a disk extent (either the EXTENT SIZE or the NEXT SIZE clause) is 16 MB pages on 9.40 and the maximum size of a chunk on 9.3x and lower.

为磁盘扩展区指定的最大大小（EXTENT SIZE 或 NEXT SIZE 子句）为 9.40 上的 16 MB页面和 9.3x 及更低版本的 chunk 的最大大小。

-19837 Invalid PDQ priority value specified.

The value of PDQPRIORITY must range from -1 to 100.

PDQPRIORITY 值的范围必须是 -1 到 100。

-19838 Invalid partition was accessed by dirty reader.

The application had a dirty reader that tried to access an invalid partition. The partition does not exist or was dropped when trying to lock it.

应用程序具有一个尝试访问无效分区的脏读。尝试锁定它时，分区不存在或被删除。

-19839 Invalid OPTCOMPIND value specified.

The value of OPTCOMPIND must range from 0 to 2.

OPTCOMPIND 值的范围必须是 0 到 2。

-19840 Invalid session environment variable.

The identifier cannot be set in a session using the SET ENVIRONMENT command.

使用 SET ENVIRONMENT 命令无法在会话中设置标识符。

-19841 Error In Specifying Automatically (Server) Generated Keys.

Possible causes are: column does not exist in table, or column is not a SERIAL or SERIAL8 or BIGSERIAL. Other causes are null String, null array, empty array or unknown constant. (Valid constants are NO_GENERATED_KEYS or RETURN_GENERATED_KEYS).

可能的原因是：列不存在于表中，或者列不是 SERIAL 或 SERIAL8 或 BIGSERIAL。

其他原因是空字符串、空数组、或未知常量。（有效常量是 NO_GENERATED_KEYS或 RETURN_GENERATED_KEYS）。

-19842 Invalid value specified for the USELASTCOMMITTED parameter.

You can set the USELASTCOMMITTED configuration parameter to one of the following values : 'Dirty Read', 'Committed Read', 'All' or 'None'.

您可以将 USELASTCOMMITTED 配置参数设置为以下值之一：'Dirty Read'、'Committed Read'、'All' 或 'None'。

-19843 Invalid IFX_AUTO_REPREPARE value specified.

The value of IFX_AUTO_REPREPARE must be either 0, 'off', or 'OFF' (to disable the Auto Re-prepare feature) or else 1, 'on', or 'ON' (to enable this feature,so that the database server automatically re-prepares a prepared object or re-optimizes an SPL routine, after a table that the prepared object or SPL routine references has been renamed or after its schema has been modified.

IFX_AUTO_REPREPARE 的值必须是 0、'off'或 'OFF'（禁用 Auto Re-prepare 功能）或 1、'on' 或 'ON'（启用此功能，以便数据库服务器将在已准备对象或 SPL 例程引用已重命名的表或其模式被修改后，自动重新准备已准备的对象或重新优化 SPL 例程）。

-19844 Tables of type RAW are not allowed in a logged database on an HDR primary server.

DML statements on RAW tables are not logged, and therefore not replicated to the HDR secondary server. If you need RAW tables on an HDR primary server,you must temporarily disable HDR. To use RAW tables on an HDR primary server:RAW 表上的 DML 语句不记录，因此不会复制到 HDR 辅助服务器。如果需要 HDR 主服务器上的 RAW 表，则必须暂时禁用 HDR。要在 HDR 主服务器上使用 RAW 表：1. Stop replication by shutting down the HDR secondary server.

通过关闭 HDR 辅助服务器停止复制。

Convert the HDR primary server into standard mode with the onmode -d standard command.

使用 onmod -d 标准命令将 HDR 主服务器转换为标准模式。

Create or alter the appropriate tables to type RAW.

创建 RAW 类型表或将表类型更改为 RAW。

Perform the required DML statements on the RAW tables.

在 RAW 表上执行所需的 DML 语句。

Convert the RAW tables back to STANDARD tables.

将 RAW 表转换回 STANDARD 表。

Perform a level-0 archive.

执行 0 级归档。

Convert the server to an HDR primary server with the onmode -d primary command.

使用 onmod -d 主命令将服务器转换为 HDR 主服务器。

Physically restore the secondary server from the level-0 archive.

从 0 级存档中物理恢复辅助服务器。

Restart replication by running the onmode -d secondary command on the secondary server.

通过在辅助服务器上运行 onmode -d secondary 命令重新启动复制。

-19845 You cannot alter the logging mode of a table in a logged database on a primary server.

You cannot change a logged table in a logged database on a primary server into a RAW, nonlogging table because changes to that table would no longer be replicated to secondary servers. You cannot change a RAW, nonlogging table to a logged table in a logged database on a primary server because the secondary servers would not be able to process replicated transactions for that table.

您无法将主服务器上记录的数据库中的日志记录表更改为 RAW 非日志记录表，因为对该表的更改将不再复制到辅助服务器。无法将 RAW 非日志记录表更改为主服务器上日志记录数据库中日志记录的表，因为辅助服务器无法处理该表的复制事务。

-19846 You cannot access a nonlogging table (%s) in a logged database on a secondary server.

Nonlogging tables are not replicated to secondary servers and are therefore not available on secondary servers.

非日志记录表不会复制到辅助服务器，因此它们在辅助服务器上不可用。

-19847 Incorrect session optimization environment variable.

The specified identifier cannot be set in a session using the SET OPTIMIZATION ENVIRONMENT statement.

不能使用 SET ENVIRONMENT 语句在会话中设置指定的标识符。

-19848 Incorrect STAR_JOIN value specified.

The value for the STAR_JOIN optimization environment must be 'DISABLED','ENABLED', or 'FORCED'. Use the value 'DISABLED' to prevent star joins in this session. Use the value 'ENABLED' to allow star joins in this session. Use the value 'FORCED' to favor star joins for all queries whenever possible in this session.

STAR_JOIN 优化环境的值必须是“DISABLED”、“ENABLED”或“FORCED”。使用值'DISABLED'来防止会话星型连接。使用“ENABLED”值允许此在会话中使用星型连接。尽可能在本次会话中使用 'FORCED' 值来支持所有查询的星型连接。

-19850 Invalid OPT_SEEK_FACTOR value specified.

The value for OPT_SEEK_FACTOR must range from 0 to 25.

OPT_SEEK_FACTOR 的值必须介于 0 到 25 之间。

-19851 Invalid OPT_CPUCOST_FACTOR value specified.

The value for OPT_CPUCOST_FACTOR must range from 0 to 20.

OPT_CPUCOST_FACTOR 的值必须介于 0 到 20 之间。

-19990 Use of CRCOLS must be consistent across the table hierarchy.

If the parent table in a table hierarchy has been created with the WITH CRCOLS option for replication shadow columns, then all subtables must also be created with the WITH CRCOLS option.

Similarily, if the parent table in the table hierarchy has not been created with the WITH CRCOLS option, then all subtables cannot be created with the WITH CRCOLS option.

如果使用复制影子列的 WITH CRCOLS 选项创建表层次结构中的父表，则还必须使用WITH CRCOLS 选项创建所有子表。类似的，如果表层次结构中的父表没有使用 WITH CRCOLS 选项创建，则所有子表都不能使用 WITH CRCOLS 选项创建。

-19989 Enterprise Replication is not in active state The specified operation cannot be performed on a table defined for replication if Enterprise replication is not in active state.

If you want to perform the specified operation, you must start Enterprise Replication.

如果 Enterprise Replication 不在活动状态，则无法在为复制定义的表上执行指定的操作。

如果要执行指定的操作，必须启动 Enterprise Replication 。

-19991 Table is not in Enterprise Replication alter mode The specified operation cannot be performed on a table defined for replication if the table is not in Enterprise Replication alter mode.

If you want to perform the specified operation, you must put the table in Enterprise Replication alter mode.

如果表未处于 Enterprise Replication 更改模式，则无法在为复制定义的表上执行指定的操作。

如果要执行指定的操作，则必须将该表置于 Enterprise Replication 更改模式。

This error can also be returned when user attempts to modify primary key constraint of a replicated table without setting alter mode manually using 'cdr alter --on DB1:OWNER1.TABLE1' command. Make sure to close the current transaction before attempting manual alter mode.

如果用户尝试修改复制表的主键约束而不使用 'cdr alter --on DB1：OWNER1.TABLE1'命令手动设置更改模式，则也会返回此错误。确保在尝试手动更改模式之前关闭当前事务。

-19992 Cannot perform insert/delete/update operations on a replicated table while the table is in alter mode The specified operation cannot be performed on a table defined for replication if the table is in Enterprise Replication alter mode.

If you want to perform the specified operation, you must unset the Enterprise Replication alter mode.

如果表处于 Enterprise Replication 更改模式，则无法在为复制定义的表上执行指定的操作。如果要执行指定的操作，则必须取消 Enterprise Replication 更改模式的设置。

-19993 Cannot modify a replicated column The specified operation cannot be performed on a table defined for replication. If you want to perform the specified operation,you must remove the column from the replicate definition, alter the column then add the column again to the replicate definition through Enterprise Replication remastering process.

指定的操作不能在为复制定义的表上执行。如果要执行指定的操作，则必须从复制定义中删除列，然后更改该列，然后通过 Enterprise Replication remastering 过程再次将该列添加到复制定义。

-19994 Cannot drop a replicated column while the column is part of replicate definition The specified operation cannot be performed on a table defined for replication. If you want to perform the specified operation,you must remove the column from the replicate definition through Enterprise Replication remastering process.

指定的操作不能在为复制定义的表上执行。如果要执行指定的操作，则必须通过Enterprise Replication remastering 过程从复制定义中删除该列。

-19995 Enterprise Replication error encountered while setting alter mode.

See the message log file to get the Enterprise Replication error code.

Enterprise Replication error encountered while performing the specified operation. See the message log file to get the Enterprise replication error code. If you want to perform the specified operation, correct the Enterprise Replication problem and reattempt the operation.

执行指定操作时遇到 Enterprise Replication 错误。请参阅消息日志文件以获取企业复制错误代码。如果要执行指定的操作，请纠正 Enterprise Replication 问题并重新尝试该操作。

-19996 Enterprise Replication error encountered while unsetting alter mode.

See message log file to get the Enterprise Replication error code Enterprise Replication error encountered while performing the specified operation. See the message log file to get the Enterprise replication error code. Correct the problem and clear the alter mode manually through cdr command line utility.

执行指定操作时遇到 Enterprise Replication 错误。

请参阅消息日志文件以获取 Enterprise Replication 错误代码。

通过 cdr 命令行实用程序手动更正问题并手动清除 alter 模式。

-19997 Cannot alter table type to STANDARD, failed to write a log record.

The table type could not be altered to STANDARD because the system failed to write a log record for this operation.

Check the accompanying ISAM error code for more information.

由于系统无法为此操作写入日志记录，因此无法将表的类型更改为 STANDARD。

请查看随附的 ISAM 错误代码以获取更多信息。

-21000 Invalid byte in codeset conversion input.

Code-set conversion cannot recognize data that is being passed between the server and the client. Check DB_LOCALE and CLIENT_LOCALE settings in your initialization file or your environment.

代码集转换无法识别在服务器和客户端之间传递的数据。检查初始化文件或环境中的 DB_LOCALE 和 CLIENT_LOCALE 设置。

-21001 Incomplete character at end of codeset conversion input.

Code-set conversion cannot recognize data that is being passed between the server and the client. Check DB_LOCALE and CLIENT_LOCALE settings in your initialization file or your environment.

代码集转换无法识别在服务器和客户端之间传递的数据。检查初始化文件或环境中的 DB_LOCALE 和 CLIENT_LOCALE 设置。

-21002 Codeset conversion output buffer too small.

An internal error occurred during code-set conversion. Note allobserved behavior and any other error message. Check with the system administrator to ensure that the system is functioning properly.

代码集转换期间发生内部错误。注意所有观察到的行为和任何其他错误消息。

请咨询系统管理员以确保系统运行正常。

-21003 Cannot open codeset conversion file.

The system could not open a code-set-conversion file. Check that GBS_HOME points to a valid directory that contains the proper code-set- conversion subdirectory.

系统无法打开代码集转换文件。检查 GBS_HOME 是否指向包含正确的代码集转换子目录的有效目录。

-21004 Internal error in codeset conversion.

An internal error occurred during code-set conversion. Note all observed behavior and any other error message. Check with the system administrator to ensure that the system is functioning properly.

代码集转换期间发生内部错误。注意所有观察到的行为和任何其他错误消息。请咨询系统管理员以确保系统运行正常。

-21005 Inexact character conversion during translation.

One or more characters were translated using a substitution character.

Translation in the reverse direction would not produce the original string.

Make sure that the values of the CLIENT_LOCALE and DB_LOCALE environment variables are compatible.

使用替换字符翻译了一个或多个字符。反向翻译不会产生原始字符串。确保 CLIENT_LOCALE和 DB_LOCALE 环境变量的值是兼容的。

-21400 brand: Invalid serial number and/or key.

Check that the serial number and key you entered during installation correspond with those on the keycard. Restart installation, or contact GBase Technical Support for verification of your serial number and key.

检查您在安装过程中输入的序列号和密钥是否与钥匙卡上的密码一致。重新启动安装，或者联系 GBase 技术支持以验证您的序列号和密钥。

-21401 brand: Cannot open file -- file probably not in current directory.

The file might not have been transferred correctly from media.

Reloadthe product from the media and reinstall. If the error recurs,note all circumstances and contact GBase Technical Support.

该文件可能未从媒体正确传输。从介质中重新加载产品并重新安装。

如果错误再次出现，请注意所有情况并联系 GBase 技术支持。

-21402 brand: Location is incorrect for file.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次出现，请注意所有情况并联系 GBase 技术支持。

-21403 brand: file already branded.

For some products, installation cannot be restarted unless you reload files from the media. Reload files from the media before you run the installation script.

对于某些产品，除非您从介质重新加载文件，否则无法重新安装。

在运行安装脚本之前，请从介质中重新加载文件。

-21404 brand: Identifier string multiply found in file.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次出现，请注意所有情况并联系 GBase 技术支持。

-21405 brand: Serial number is wrong length in file.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次出现，请注意所有情况并联系 GBase 技术支持。

-21406 program: Cannot open file.

The file might not have been transferred correctly from media.

Reload the product from the media and reinstall. If the error recurs,note all circumstances and contact GBase Technical Support.

文件可能无法从媒体正确传输。从媒体重新加载产品并重新安装。

如果错误再次发生，请注意所有情况，并与 GBase 技术支持部门联系。

-21407 Error reading from file.

The file might not have been transferred correctly from media.

Reload the product from the media and reinstall. If the error recurs,note all circumstances and contact GBase Technical Support.

文件可能无法从媒体正确传输。从媒体重新加载产品并重新安装。

如果出现错误，请记录所有情况并与 GBase 技术支持部门联系。

-21408 Error writing to file.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次出现，请注意所有情况并联系 GBase 技术支持。

-21410 verstamp: Cannot create stream for file.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次出现，请注意所有情况并联系 GBase 技术支持。

-21411 verstamp: Identify string not found in file.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次出现，请注意所有情况并联系 GBase 技术支持。

-21412 verstamp: Warning: string found number times in file.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次出现，请注意所有情况并联系 GBase 技术支持。

-21413 Cannot open file; system error number.

The file might not have been transferred correctly from media.

Reload the product from the media and reinstall. If the error recurs,note all circumstances and contact GBase Technical Support.

该文件可能未从媒体正确传输。从介质中重新加载产品并重新安装。

如果错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-21414 Unexpected EOF on file.

The file might not have been transferred correctly from media.

Reload the product from the media and reinstall. If the error recurs,note all circumstances and contact GBase Technical Support.

该文件可能未从媒体正确传输。从介质中重新加载产品并重新安装。

如果错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-21501 ISAM error: SE/C-ISAM was unable to insert a row because the file already contains 2^31 -1 (2147483647) rows.

You have reached the maximum number of rows for this file.

您已达到此文件的最大行数。

Delete some rows before you add more rows.

在添加更多行之前删除一些行。

-21502 ISAM error: The transaction log-file format is incompatible with the SE/C-ISAM version being used.

This could be because the transaction log file was created using an older version of SE/C-ISAM.

这可能是因为事务日志文件是使用较旧版本的 SE/C-ISAM 创建的。

Ensure that the transaction log file is used by the same version of SE/C-ISAM that created it, so that log-file format is compatible.

确保事务日志文件由创建它的 SE/C-ISAM 的相同版本使用，这样日志文件格式是兼容的。

-21524 ISAM error: Cannot create a temporary operating system file to use in a sort.

The database server could not create a temporary operating system file for this sort.

数据库服务器无法为这类创建临时操作系统文件。

Consider setting the PSORT_DBTEMP environment variable to a secure directory with a minimum of 200 MB of free space.

请考虑将 PSORT_DBTEMP 环境变量设置为至少 200 MB 可用空间的安全目录。

-21525 ISAM error: Cannot write to a temporary operating system file during a sort.

The database server could not write to the temporary operating system file,most likely because the file directory is out of space.

数据库服务器无法写入临时操作系统文件，很可能是因为文件目录空间不足。

-21600 Usage: mkmessage [-v] [-dMACRO] input_file output_file.

This message indicates an internal error. You probably used incorrect syntax in the command line. Check the usage that the message indicates,and try again. If the error recurs, note all circumstances and contact GBase Technical Support.

此消息表示内部错误。您可能在命令行中使用了不正确的语法。检查消息指示的用法，然后重试。

如果错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-21601 Source and object files the same, would overwrite 'filename'.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-21602 Input file could not be opened.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-21603 Output file could not be created.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-21604 Error writing to result file filename.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-21605 Error writing to output file filename.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-21606 Error reading from temporary text file.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-21607 Number of errors counted: number.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-21608 You have exceeded the limits of 8 defines. Extra defines will be ignored.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-21609 Unmatched ^ELSE at line line-number.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-21610 Unmatched ^ENDIF at line line-number.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-21611 Syntax error at line line-number. Expect ifdef, ifndef, else or endif after '^'.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-21612 Unexpected EOF. Expected an ^endif.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-21613 Syntax error at line line-number. Expect ifdef, ifndef, else or endif.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-21614 Expected identifier not found following ^ifdef or ^ifndef at line line-number.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-21615 Output file could not be opened for read/write.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-21616 Temporary text file could not be created.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-21617 Temporary text file could not be opened for read/write.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22201 variable-name is not a unique record component.

The name in the record has already been used, so it is not unique.

Change the name of the record variable and try again.

记录中的名称已经被使用，所以它不是唯一的。更改记录变量的名称，然后重试。

-22202 This feature is not supported in this preprocessor.

The GBase 8s ESQL/COBOL preprocessor does not support the feature that this statement requests. Check the GBase 8s ESQL/COBOL Programmer's Manual for information on preprocessor functionality in this version.

GBase 8s ESQL/COBOL 预处理器不支持此语句请求的功能。有关此版本中预处理器功能的信息，请查看 GBase 8s ESQL/COBOL 程序员手册。

-22203 Invalid keyword name on the PICTURE clause.

The PICTURE clause contains an illegal keyword, as the error message specifies. Check the syntax of the variable declaration for the PICTURE clause and try again.

PICTURE 子句包含非法关键字，如错误消息所指定。检查 PICTURE 子句的变量声明的语法，然后重试。

-22204 COBOL group USAGE clause contradiction (variable OF record).

The USAGE clause for a record component does not match the USAGE clause of the record group to which it belongs. Usage clauses for the elements of a record are inherited from the group record declaration. A mismatch causes an error.

记录组件的 USAGE 子句与其所属的记录组的 USAGE 子句不匹配。记录元素的 USAGE 子句从组记录声明中继承。不匹配导致错误。

-22205 COBOL group SIGN clause contradiction (variable OF record).

The SIGN clause of the record component does not match the SIGN clause of the record group to which it belongs. Sign clauses for the elements of a record are inherited from the group record declaration. A mismatch causes an error.

记录组件的 SIGN 子句与其所属的记录组的 SIGN 子句不匹配。记录元素的 SIGN 子句是从组记录声明继承的。不匹配会导致错误。

-22206 INTERNAL ERROR: Bad COBOL function call.

Check that the CALL syntax is correct and verify whether data is corrupted before you call GBase Technical Support for assistance.

在致电 GBase 技术支持寻求帮助之前，检查 CALL 语法是否正确并验证数据是否损坏。

-22207 Host variables may only be 01-49 or 77 level.

ESQL/COBOL supports only level 01 through level 49 COBOL variables and record types, plus COBOL variable level 77 if your COBOL compiler supports it. Check the level number of the host variable to see if it is valid.

ESQL/COBOL只支持级别 01 到 49 级 COBOL 变量和记录类型，加上 COBOL 变量级别 77(如果 COBOL 编译器支持它)。检查主机变量的级别数，以确定其是否有效。

-22208 Host variables may not be USAGE INDEX.

Change the USAGE clause for the host variable so that it is not USAGE IS INDEX and try again. GBase 8s ESQL/COBOL does not support USAGE INDEX.

更改主机变量的 USAGE 子句，以便它不是 USAGE IS INDEX，然后重试。

GBase 8s ESQL/COBOL 不支持 USAGE INDEX。

-22209 No hyphen allowed in SQL object identifier, cursor name, or statement id.

You must change the name of the object identifier, cursor, or statement ID so that it does not contain a hyphen.

必须更改对象标识符、游标或语句 ID 的名称，以使其不包含连字符。

-22210 Repeated data item variable-name is not expanded.

The ESQL/COBOL preprocessor does not expand the record that contains repeated data items. Change the record and try again.

ESQL/COBO L预处理器不扩展包含重复数据项的记录。更改记录并重试。

-22227 Invalid COBOL compiler compiler-name.

The compiler that is specified is not supported. Check the GBase 8s ESQL/COBOL Programmer's Manual for information on compilers that this version supports.

指定指定的编译器不受支持。查看 GBase 8s ESQL/COBOL 程序员手册，了解此版本支持的编译器的信息。

-22229 Host object variable-name not declared.

The specified host variable was accessed but was not declared. You must declare the host variable in the declaration section and try again.

指定的主机变量已被访问但未被声明。必须在声明部分声明主机变量，然后重试。

-22230 Identification error on host symbol variable-name.

The host variable has been declared more than once. Check for the duplicate variable declaration and redeclare one of the variables.

已多次声明主机变量。检查重复变量声明并重新声明其中一个变量。

-22231 Record nesting limit exceeded.

The maximum number of levels for valid record nesting is 100. Reduce the number of nested records and try again.

有效记录嵌套的最大级别数为 100。减少嵌套记录的数量，然后重试。

-22232 variable-name is not a component of record-name.

The variable name is not part of the components of the record. Check the record declaration and its components to verify that you have correctly declared the variable with this name.

变量名称不是记录组件的一部分。检查记录声明及其组件，以验证是否已使用此名称正确声明了变量。

-22233 compiler-name does not allow array elements to be passed as parameters.

Unless you are using either the Ryan McFarland RM/COBOL 85 compiler or the Micro Focus COBOL/2 compiler, you cannot pass array elements as parameters. Use one of the specified compilers, or rewrite this section of code that involves arrays.

除非您使用 Ryan McFarland RM/COBOL 85 编译器或 Micro Focus COBOL/2 编译器，否则无法将数组元素作为参数传递。使用其中一个指定的编译器，或重写涉及数组的这部分代码。

-22234 Buffer provided by user is too small. Result will be truncated to fit buffer.

The buffer that is used to store the result of the operation of the function is too small to hold the entire result. As much of the result as possible was copied, and extra characters were truncated. Increase the buffer declaration so that it can hold larger strings.

用于存储函数操作结果的缓冲区太小，无法保存整个结果。尽可能多地复制结果，并截断额外的字符。增加缓冲区声明，以便它可以容纳更大的字符串。

-22245 Invalid BCD type (rvalhlvar).

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22246 INTERNAL ERROR: BCD buffer too small (rhlvarval).

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22247 Invalid BCD type (rhlvarval).

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22248 Date conversion error: rfmtdate in toadate.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22249 Internal error: Invalid integer size (toaint).

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22250 BCD buffer length is too small.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22251 Error in decimal conversion (frombcd: deccvasc).

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22252 Error in decimal conversion (frompbcd: deccvasc).

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22253 Error in C var to val conversion (frombcd).

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22254 DATE type variable size is too large.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22255 Date conversion error: rdefmtdate.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22256 Error in C var to val conversion (fromadate).

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22257 Error in C var (short) to val conversion.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22258 Error in C var (int) to val conversion.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22259 Error in C var (long) to val conversion.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22260 Internal Error: Invalid integer size.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22261 Error in decimal conversion (valtoasc: deccvasc).

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22262 Error in decimal conversion (valtoasc: dectoasc).

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22263 Internal error: Invalid C type (valtoasc).

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-22264 Host data items must not be alphanumeric or numeric edited items.

Change the declaration of the PICTURE clause to one of the following valid categories for host variables: alphabetic, numeric, or alphanumeric. GBase 8s ESQL/COBOL does not support alphanumeric edited or numeric edited items.

将 PICTURE 子句的声明更改为主机变量的下列有效类别之一：字母、数字或字母数字。

GBase 8s ESQL/COBOL 不支持经编辑或数字编辑的字母数字项。

-22265 A sign clause was specified for an unsigned numeric type.

If you have a SIGN clause but did not specify "S," the compiler cannot process the data type. Check whether the variable is signed or unsigned and declare it accordingly.

如果有 SIGN 子句但未指定“S”，则编译器无法处理数据类型。检查变量是有符号还是无符号，并相应地声明它。

-22266 Type not supported by ESQL/language-name for compiler-name.

The type that is specified for the variable is not supported for the compiler name that is used. Check your compiler documentation for valid type declarations.

所使用的编译器名称不支持为变量指定的类型。检查编译器文档以获取有效的类型声明。

-22268 P in the PICTURE clause not implemented.

Currently, GBase 8s ESQL/COBOL does not support the declaration P(decimal scaling position) in a PICTURE clause.

目前，GBase 8s ESQL/COBOL 不支持 PICTURE 子句中的声明 P（十进制缩放比例）。

-22274 Host variables may not be USAGE POINTER.

Change the USAGE clause for the host variable so that the host variable is not a pointer and try again.

更改主机变量的 USAGE 子句，使主机变量不是指针，然后再试一次。

-22275 INTERNAL ERROR: Temporary buffer length has been exceeded.

The string or buffer parameter to the function is longer than the internal buffer. Change the string or buffer declaration so that the string or buffer has a smaller maximum size.

函数的字符串或缓冲区参数比内部缓冲区长。更改字符串或缓冲区声明，以便字符串或缓冲区具有较小的最大大小。

-22276 Floating point variables are not allowed.

This compiler does not support floating-point numbers.

此编译程序不支持浮点数。

-22277 Invalid storage mode. Assuming byte-storage mode.

Micro-Focus COBOL/2 has either byte or word storage mode for USAGE COMP/BINARY variables. Check the current storage mode. To specify byte or word storage, set the GBASEDBTCOBSTORE environment variable, as the GBase 8s Guide to SQL: Reference discusses.

Micro-Focus COBOL/2 具有 USAGE COMP/BINARY 变量的字节或字存储模式。

检查当前的存储模式。要指定字节或字存储，请按照“GBase 8s SQL指南：参考”中讨论的内容设置 GBASEDBTCOBSTORE 环境变量。

-22278 Cannot open COBOL 'whenever' file file-name.

The directory in which the COBOL temporary files are being created(usually /tmp or whatever is specified when the DBTEMP environment variable is set) is full. No room is available to open new files. Check this directory and free some space.

创建 COBOL 临时文件的目录（通常为 /tmp 或在设置 DBTEMP 环境变量时指定的文件）已满。没有空间可用于打开新文件。检查这个目录并释放一些空间。

-22279 Cannot open COBOL temp file file-name.

创建 COBOL 临时文件的目录（通常为 /tmp 或在设置 DBTEMP 环境变量时指定的文件）已满。没有空间可用于打开新文件。检查这个目录并释放一些空间。

-22280 Line is too long.

The SQL string in the EXEC SQL statement is too long to fit in the internal buffer. The maximum SQL string length should be less than 32,767.

EXEC SQL 语句中的 SQL 字符串太长，无法适应内部缓冲区。

最大的 SQL 字符串长度应小于 32,767。

-22281 FILLER variables can only be used as fields in a record.

In GBase 8s ESQL/COBOL, the FILLER keyword must identify all filler items. Filler variables can only be used as fields in a record and must also have a PIC clause associated with them. Check the declaration of the variable and change its name.

在 GBase 8s ESQL/COBOL 中，FILLER 关键字必须标识所有填充项目。

填充变量只能用作记录中的字段，并且还必须具有与之关联的 PIC 子句。

检查变量的声明并更改其名称。

-22282 Invalid numeric data length.

The length and precision of the data is too large or otherwise incorrect. The length cannot be greater than 18, and the precision cannot be greater than the length.

数据的长度和精度太大或者不正确。长度不能大于 18，精度不能大于长度。

-22283 Numeric value from database cannot be stored in COBOL data item.

In GBase 8s ESQL/COBOL, a number of conditions can cause this error message to appear. The value is too large, data cannot contain a negative value, a signed value cannot be stored in an unsigned data item, or a float overflow has occurred.

在 GBase 8s ESQL/COBOL 中，许多情况都可能会导致出现此错误消息。值太大、数据不能包含负值、有符号值不能存储在无符号数据项中、或发生浮点溢出。

-22284 Incorrect levels of indirection on variable variable-name.

A pointer variable is used with the wrong number of level indirection.

Check the indirection levels in the ESQL statement.

指针变量与错误的级别间接数一起使用。检查 ESQL 语句中的间接级别。

-22285 Incorrect dimension on table variable variable-name.

An entry in a multidimensional array is illegally accessed.

Indexes for multidimensional arrays must be specified when used.

For example, suppose a host variable is declared in ESQL/COBOL as follows:非法访问多维数组中的项。必须在使用时指定多维数组的索引。

例如，假设主变量在 ESQL/COBOL 中声明如下：01 VARA X(10) OCCURS 3 TIMES.

It will return an error if it is used in an SQL statement as follows because you must specify the index into which you want to insert (that is, VARA(1)):如果在 SQL 语句中使用它，则会返回一个错误，因为必须指定要插入的索引（即 VARA(1)）：INSERT INTO TAB VALUES ($VARA)-22554 Field type field-type-name has been used out of context.

This error is generated when, for example, the field type TYPE is used where COUNT is expected. Check the syntax and usage for system-descriptor field names in the discussion of the ALLOCATE DESCRIPTOR and GET DESCRIPTOR statements in the GBase 8s Guide to SQL: Syntax. For a discussion of the system-descriptor area,see the manual for your embedded-language product.

例如，当使用字段类型 TYPE 时，会生成此错误，其中 COUNT 是预期的。在 GBase 8s SQL指南：语法的讨论中讨论 ALLOCATE DESCRIPTOR 和 GET DESCRIPTOR 语句，检查系统描述符字段名称的语法和用法。有关系统描述符区域的讨论，请参阅嵌入式语言产品的手册。

-22555 The type of host-variable does not match the expected type for this field.

This error is generated when a variable is expected to have a certain type but does not. For example, an TYPE field accepts only integer types when a value is assigned to it or retrieved from it. If the variable type is not integer, an error is generated. Check the syntax and usage for system descriptor field names in the discussion of the ALLOCATE DESCRIPTOR and GET DESCRIPTOR statements in the GBase 8s Guide to SQL: Syntax. For a discussion of the system descriptor area, see the manual for your embedded-language product.

在需要计数的地方使用字段类型时会产生此错误。在讨论分配描述符时检查系统描述符字段名的语法和用法，并在《GBase 8s SQL指南：语法》中获取描述符语句。有关系统描述符区域的讨论，请参阅嵌入式语言产品手册。

-22558 This feature is not supported in the GBase 8s Dynamic Server.

The GBase 8s Dynamic Server does not support this feature.

Check the GBase 8s ESQL/C Programmer's Manual or GBase 8s Guide to SQL Syntax for information on the DESCRIBE statement functionality of this server version.

GBase 8s Dynamic Server 不支持此功能。有关此服务器版本的描述语句功能的信息，请参阅《GBase 8s ESQL/C 程序员手册》或《GBase 8s SQL指南：语法》。

-22559 SQLUNKNOWN is invalid data type, need to be set valid data type.

If the database server cannot infer the type of parameter in an expression, the DESCRIBE INPUT statement returns SQLUNKNOWN as the data type. Before statement execution, you must set a valid SQL data type to replace SQLUNKNOWN.

如果数据库服务器无法推断表达式中参数的类型，则 DESCRIBE INPUT 语句将返回SQLUNKNOWN 作为数据类型。在执行语句之前，必须设置有效的 SQL 数据类型来替换SQLUNKNOWN。

-22600 Invalid SQL type type-name. Internal error.

For this GBase 8s ESQL/FORTRAN preprocessor error, check the data type of the symbol. Type-name must be a valid SQL data type.

对于此 GBase 8s ESQL/FORTRAN 预处理错误，请检查符号的数据类型。

类型名称必须是有效的 SQL 数据类型。

-22601 Whenever raise not supported by ESQL/FORTRAN.

You cannot specify RAISE in a WHENEVER statement. Delete the statement,or substitute a valid option.

无法在 WHENEVER 语句中指定 RAISE。删除该语句，或替换一个有效的选项。

-22602 Whenever perform not supported by ESQL/FORTRAN.

You cannot specify PERFORM in a WHENEVER statement. Delete the statement, or substitute a valid option.

无法在 WHENEVER 语句中指定 PERFORM。删除该语句，或替换一个有效的选项。

-22617 STRUCTURE declaration not supported.

This message indicates an GBase 8s ESQL/FORTRAN preprocessor error.

The STRUCTURE statement is supported only with the Green Hills and Sun versions of FORTRAN that include the VMS FORTRAN extensions.

此消息表明 GBase 8s ESQL/FORTRAN 预处理错误。只有包含 VMS FORTRAN 扩展的Green Hills 和 Sun 版本的 FORTRAN 才支持 STRUCTURE 语句。

-22618 RECORD statement not supported.

This message indicates an GBase 8s ESQL/FORTRAN preprocessor error.

The RECORD statement is supported only with the Green Hills and Sun versions of FORTRAN that include the VMS FORTRAN extensions.

此消息表明 GBase 8s ESQL/FORTRAN 预处理器错误。只有包含 VMS FORTRAN 扩展的Green Hills 和 Sun 版本的 FORTRAN 支持 RECORD 语句。

-22619 UNION declaration not supported.

This message indicates an GBase 8s ESQL/FORTRAN preprocessor error.

The UNION statement is supported only with Green Hills and Sun versions of FORTRAN that include the VMS FORTRAN extensions.

此消息表明 GBase 8s ESQL/FORTRAN 预处理器错误。只有包含 VMS FORTRAN 扩展的Green Hills 和 Sun 版本的 FORTRAN 才支持 UNION 语句。

-22620 Host object host variable not declared.

This message indicates an GBase 8s ESQL/FORTRAN preprocessor error. An SQL statement contains a host variable that has not been declared. Host variables are declared in the same way as other FORTRAN variables except that the declaration must be contained in a declaration block between a pair of EXEC SQL BEGIN DECLARE SECTION and EXEC SQL END DECLARE SECTION statements. You cannot use the SQL data types to declare host variables. You must specify a FORTRAN data type or one of the GBase 8s ESQL/FORTRAN data types when you declare a host variable.

The data type of the host variable should reflect the data type of the database column to which it corresponds.

此消息表明 GBase 8s ESQL/FORTRAN 预处理器错误。SQL 语句包含尚未声明的主机变量。

主变量的声明方式与其他 FORTRAN 变量相同，只是声明必须包含在一对 EXEC SQL BEGIN DECLARE SECTION 和 EXEC SQL END DECLARE SECTION 语句之间的声明块中。不能使用 SQL 数据类型来声明主机变量。声明主机变量时，必须指定 FORTRAN 数据类型或GBase 8s ESQL/FORTRAN 数据类型之一。主机变量的数据类型应该反映它所对应的数据库列的数据类型。

-22621 Out of Memory for symbol table.

This message indicates an GBase 8s ESQL/FORTRAN preprocessor error.

The preprocessor is unable to allocate more memory for the symbol table. If possible, reduce the number of processes that are running at the same time as the preprocessor or reduce the number of symbols that your FORTRAN program defines.

此消息表明 GBase 8s ESQL/FORTRAN 预处理器错误。预处理器无法为符号表分配更多内存。

如果可能，请减少与预处理器同时运行的进程数，或减少 FORTRAN 程序定义的符号数。

-22622 Type type-name is unknown.

This message indicates an GBase 8s ESQL/FORTRAN preprocessor error.

The symbol is not a declared type. Declare type-name and try again.

此消息表明 GBase 8s ESQL/FORTRAN 预处理器错误。该符号不是已声明的类型。

声明类型名称并重试。

-22623 Data type length must be greater than zero.

This message indicates an GBase 8s ESQL/FORTRAN preprocessor error.

The length that is specified for the data type is less than zero.

Assign a length to the data type and try again.

此消息表明 GBase 8s ESQL/FORTRAN 预处理器错误。为数据类型指定的长度小于零。

为数据类型指定一个长度，然后再试一次。

-22624 INTEGER type length must be 2 or 4.

This message indicates an GBase 8s ESQL/FORTRAN preprocessor error. A FORTRAN host variable of type INTEGER must be declared as INTEGER*2 or INTEGER*4. Correct the length of the INTEGER declaration and try again.

此消息表明 GBase 8s ESQL/FORTRAN 预处理器错误。INTEGER 类型的 FORTRAN 主机变量必须声明为 INTEGER * 2 或 INTEGER * 4。更正 INTEGER 声明的长度并重试。

-22625 REAL type length must be 4 or 8.

This message indicates an GBase 8s ESQL/FORTRAN preprocessor error. A FORTRAN host variable of type REAL must be declared as REAL*4 or REAL*8. Correct the length of the REAL declaration and try again.

此消息表明 GBase 8s ESQL/FORTRAN 预处理器错误。REAL 类型的 FORTRAN 主机变量必须声明为REAL * 4 或 REAL * 8。更正 REAL声明的长度并重试。

-22626 Empty SQL statement.

This message indicates an GBase 8s ESQL/FORTRAN preprocessor error.

SQL statements and precompile instructions that are embedded in a FORTRAN program must be preceded by the keywords EXEC SQL. No statement terminator is required, except when you specify a multiple-statement object in a PREPARE statement.

此消息表明 GBase 8s ESQL/FORTRAN 预处理器错误。SQL 语句和预编译指令必须以关键字 EXEC SQL 开头。除了在 PREPARE 语句中指定多语句对象外，不需要语句终止符。

-22628 Record component component-name not declared.

This message indicates an GBase 8s ESQL/FORTRAN preprocessor error.

Examine the related structure declaration for this record. The component-name element does not exist as it is typed within the structure declaration.

此消息表明 GBase 8s ESQL/FORTRAN 预处理器错误。检查此记录的相关结构声明。

组件名称元素不存在，因为它在结构声明中键入。

-22635 INTERNAL ERROR. Temporary buffer length has been exceeded.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次出现，请注意所有情况，并联系 GBase 技术支持。

-22645 Incorrect dimension on array variable.

This message indicates an GBase 8s ESQL/FORTRAN preprocessor error.

The symbol is not an array variable or the dimension is incorrect.

此消息表示GBase 8s ESQL/FORTRAN 预处理器错误。该符号不是数组变量或维度不正确。

-22646 Incorrect levels of indirection.

This message indicates an GBase 8s ESQL/FORTRAN error message. An incorrect index has been accessed in your array. Check the usage of your array. See error message -33203 for a similar message in GBase 8s ESQL/C.

此消息表示 GBase 8s ESQL/FORTRAN 错误消息。在数组中访问了不正确的索引。

检查数组的用法。有关 GBase 8s ESQL/C 中的类似消息，请参阅错误消息 -33203。

-22647 Use of non-SQL descriptors not supported by ESQL/FORTRAN.

This message indicates an GBase 8s ESQL/FORTRAN preprocessor error. In ESQL/FORTRAN, only system descriptor areas that have been allocated with the ALLOCATE DESCRIPTOR statement can be used in a DESCRIBE statement.

此消息表示 GBase 8s ESQL/FORTRAN 预处理器错误。在 ESQL/FORTRAN 中，只有使用ALLOCATE DESCRIPTOR 语句分配的系统描述符区域才能用于 DESCRIBE 语句。

-22648 Line is too long.

This message indicates anGBase 8s ESQL/FORTRAN preprocessor error.

The SQL statement is too long (greater than 32 kilobytes). In standard FORTRAN format, any nonblank character, except for zero, in column 6 is a continuation symbol. In UNIX-style FORTRAN format, an ampersand in column 1 is the continuation symbol. Shorten the SQL statement and try again.

此消息指示 GBase 8s ESQL/FORTRAN 预处理器错误。SQL 语句太长（大于 32 千字节）。

在标准 FORTRAN 格式中，除第6列中的零以外，任何非空白字符都是一个延续符号。

在 UNIX 样式的 FORTRAN 格式中，第 1列中的 & 符号是延续符号。

缩短 SQL 语句并重试。

-22649 Unmatched END statement-name statement.

This message indicates an GBase 8s ESQL/FORTRAN preprocessor error. An END STRUCTURE/UNION/MAP statement does not have a corresponding STRUCTURE/UNION/MAP statement. Check that each END STRUCTURE/UNION/MAP statement is paired with a corresponding STRUCTURE/UNION/MAP statement and try again.

此消息表示 GBase 8s ESQL/FORTRAN 预处理器错误。 END STRUCTURE/UNION/MAP 语句没有相应的 STRUCTURE/UNION/MAP 语句。检查每个 END TRUCTURE/UNION/MAP 语句是否与相应的 STRUCTURE/UNION/MAP 语句配对，然后重试。

-22650 Missing END statement-name statement.

This message indicates an GBase 8s ESQL/FORTRAN preprocessor error. A STRUCTURE/UNION/MAP statement does not have a corresponding END statement. Check that each STRUCTURE/UNION/MAP statement is paired with a subsequent END statement and try again.

此消息表示 GBase 8s ESQL/FORTRAN 预处理器错误。STRUCTURE/UNION/MAP 语句没有相应的 END 语句。检查每个 STRUCTURE/UNION/MAP 语句是否与随后的 END 语句配对，然后重试。

-23075 Unable to open the log file.

The ESQL processor cannot open the log file that is specified on the command line. The log files are specified after the -log option. Check that you have specified the log file correctly.

ESQL 处理器无法打开在命令行上指定的日志文件。日志文件是在 -log 选项之后指定的。

检查您是否正确指定了日志文件。

-23076 Incompatible file extension for '-e' option.

The filename that is specified after the -e option on the command line for the ESQL processor has an incompatible file extension. Verify the file extension and try again.

在 ESQL 处理器的命令行上的 -e 选项之后指定的文件名具有不兼容的文件扩展名。

验证文件扩展名，然后重试。

-23077 Missing target file name.

No output filename has been specified after the -o option on the command line for the ESQL processor. Re-enter the command and specify an output file.

ESQL 处理器的命令行上的 -o 选项后没有指定输出文件名。重新输入命令并指定一个输出文件。

-23078 Incompatible file extension for '-c' option.

The filename that is specified after the -c option on the command line for the ESQL processor has an incompatible file extension. Verify the file extension and try again.

在 ESQL 处理器的命令行上使用 -c 选项指定的文件名具有不兼容的文件扩展名。

验证文件扩展名并重试。

-23079 Missing log filename.

No log filename has been specified after the -c option on the command line for the ESQL processor. Enter the command again and specify a log file.

ESQL 处理器的命令行上的 -c 选项后没有指定日志文件名。再次输入命令并指定日志文件。

-23080 Memory model conflict.

More than one memory model option has been specified on the command line for the ESQL processor. Try again and specify only one memory model option.

在 ESQL 处理器的命令行上指定了多个内存模型选项。再试一次，只指定一个内存模型选项。

-23081 Compiler option conflict.

More than one compiler option has been specified on the command line for the ESQL processor. Try again and specify only one compiler option.

在 ESQL 处理器的命令行上指定了多个编译器选项。再试一次，只指定一个编译器选项。

-23082 Missing list filename.

No list filename has been specified for the -f option on the command line for the ESQL processor. Enter the command again and specify a list file.

没有为 ESQL 处理器的命令行上的 -f 选项指定列表文件名。再次输入命令并指定一个列表文件。

-23083 Application option conflict.

More than one application option has been specified on the command line for the ESQL processor. Try again and specify only one application option.

在 ESQL 处理器的命令行上指定了多个应用程序选项。再试一次，只指定一个应用程序选项。

-23084 Cannot open ESQL response file 'file-name'.

The ESQL processor cannot open the ESQL response file that is specified on the command line.

ESQL 处理器无法打开在命令行中指定的 ESQL 响应文件。

-23085 Unable to allocate memory.

The ESQL processor cannot allocate memory dynamically.

ESQL 处理器不能动态分配内存。

-23086 Unable to spawn the preprocessor.

The ESQL processor cannot spawn the ESQL preprocessor.

ESQL 处理器无法产生 ESQL 预处理器。

-23087 No source or object file.

You have not specified either a source file or an object file on the command line for the ESQL processor. Re-enter the command and specify either a source file or an object file.

您尚未在命令行上为 ESQL 处理器指定源文件或目标文件。重新输入命令并指定源文件或目标文件。

-23088 Windows application or DLL needs a module definition file.

No module definition file has been specified on the command line for the ESQL processor. Re-enter the command and specify a module definition file.

在 ESQL 处理器的命令行上没有指定模块定义文件。重新输入命令并指定一个模块定义文件。

-23091 Cannot open file 'file-name'.

The ESQL processor cannot open the specified file. Check that you have specified the file correctly.

ESQL 处理器无法打开指定的文件。检查您是否正确指定了文件。

-23092 Unable to spawn the compiler.

The ESQL processor cannot spawn the compiler.

ESQL 处理器不能派生编译器。

-23093 Unable to spawn the linker.

The ESQL processor cannot spawn the linker.

ESQL 处理器不能产生链接器。

-23094 Unable to spawn the resource compiler.

The ESQL processor cannot spawn the resource compiler.

ESQL 处理器无法生成资源编译器。

-23095 Unable to create the temporary file.

The ESQL processor cannot create the temporary file. Delete the temporary files that start with "eq" in the specified directory.

ESQL 处理器不能创建临时文件。删除指定目录中以“eq”开头的临时文件。

-23096 Missing command line parameter file.

No command-line parameter file has been specified for the ESQL processor. Try again and specify a command-line parameter file.

没有为 ESQL 处理器指定命令行参数文件。重试并指定命令行参数文件。

-23097 Too many parameters.

Too many parameters were specified on the command line for the ESQL processor. Re-enter the command and specify fewer parameters.

在 ESQL 处理器的命令行上指定的参数太多。重新输入命令并指定更少的参数。

-23098 No source file.

No source file has been specified on the command line for the ESQL processor. Re-enter the command and specify a source file.

在 ESQL 处理器的命令行中未指定源文件。重新输入命令并指定源文件。

-23099 'file-name' has incompatible file format.

The specified list file or response file has an incompatible file format for the ESQL processor.

指定的列表文件或响应文件对于 ESQL 处理器具有不兼容的文件格式。

-23100 Compilation errors.

The ESQL processor has terminated processing due to one or more compilation errors.

由于一个或多个编译错误，ESQL 处理器已终止处理。

-23101 Unable to load locale categories.

An invalid locale name was supplied for the locale initialization.

The environment variable specifying the locale category has a wrong value.

为语言环境初始化提供了无效的语言环境名称。指定语言环境类别的环境变量具有错误的值。

Check the value of the corresponding environment variable,CLIENT_LOCALE or DB_LOCALE. If this error was encountered when using the "SET COLLATION" statement, check that the value passed to the statement is a valid locale. If this error was encountered when using the "SET NO COLLATION" statement, check that the session's default locale file is still available. Also check if GBS_HOME points to a valid directory where GBase 8s products are installed.

检查相应的环境变量 CLIENT_LOCALE 或 DB_LOCALE 的值。如果在使用“SET COLLATION”语句时遇到此错误，请检查传递给语句的值是否为有效的语言环境。如果在使用“SET NO COLLATION”语句时遇到此错误，请检查会话的默认语言环境文件是否仍然可用。

还要检查 GBS_HOME 是否指向安装 GBase 8s 产品的有效目录。

If a client application receives this error when it requests a database server connection, check that the client and database locales are compatible. They are compatible if a valid locale exists on the server computer with the name lg_tr.codeset@mod, where lg_tr (language and territory) and mod (locale modifier) are from the CLIENT_LOCALE and codeset is from the database locale (from the DB_LOCALE, if it is set,or as stored in the database).

如果客户端应用程序在请求数据库服务器连接时收到此错误，请检查客户端和数据库的语言环境是否一致。如果服务器计算机上存在名称为 lg_tr.codeset@mod 的有效语言环境，则它们是一致的，其中 lg_tr（language 和 territory）和 mod（语言环境修饰符）来自 CLIENT_LOCALE，而代码集来自数据库语言环境（来自 DB_LOCALE，如果设置，或存储在数据库中）。

-23102 Memory allocation failed during locale processing.

The program cannot allocate enough memory for the internal code-set conversion buffer or control table. Only a client process returns this error. Rerun the program after you free some memory.

程序不能为内部代码集转换缓冲区或控制表分配足够的内存。只有客户端进程才会返回此错误。释放内存后重新运行该程序。

-23103 Code-set conversion function failed due to an illegal sequence or invalid value.

Illegal or invalid characters occur in the character string. The program could not execute the code-set conversion on the characters that this string contains. Reexamine the input string for illegal or invalid characters and reexecute the program.

字符串中出现非法或无效字符。程序无法对该字符串包含的字符执行代码集转换。

重新检查非法或无效字符的输入字符串并重新执行程序。

-23104 Error opening required code-set conversion object file.

No object code-set conversion (definition) file exists for the two given code sets. The environment variables DB_LOCALE or CLIENT_LOCALE might have been set to the wrong value, which caused an error condition to be generated. The files might also be missing, or the information that they contain might be garbled. Check the value of the environment variable CLIENT_LOCALE or DB_LOCALE. The object conversion files usually have the .cvo extension.

对于给定的两个代码集，不存在目标代码集转换（定义）文件。环境变量 DB_LOCALE或 CLIENT_LOCALE 可能设置为错误的值，从而导致生成错误条件。文件可能也会丢失，或者它们包含的信息可能会出现乱码。检查环境变量 CLIENT_LOCALE 或 DB_LOCALE 的值。

对象转换文件通常具有 .cvo 扩展名。

When accessing via drda protocol, this error may also mean that the client application is trying to bind a value which is in a different encoding than database locale. Set environment variable GL_USEGLU=1 prior to bringing up the server to initialize the appropriate converters required to handle the codeset conversions. (for example, when using setCharacterStream()interface to bind the LOB data through JCC, the input data may come with double byte encoding and may mismatch with DB_LOCALE)当通过 drda 协议访问时，此错误也可能意味着客户端应用程序试图绑定与数据库语言环境编码不同的值。

在启动服务器以初始化处理代码集转换所需的适当转换器之前，设置环境变量 GL_USEGLU = 1。（例如，使用 setCharacterStream() 接口通过 JCC 绑定 LOB 数据时，输入数据可能采用双字节编码，可能与 DB_LOCALE 不匹配）-23105 The current database engine does not support code-set conversion.

The code-set conversion in the database server is not yet implemented.

Check the value of the CLIENT_LOCALE, SERVER_LOCALE, or DB_LOCALE environment variable.

数据库服务器中的代码集转换尚未实现。检查 CLIENT_LOCALE、SERVER_LOCALE 或 DB_LOCALE 环境变量的值。

-23106 Invalid argument for the code-set conversion initializing function.

An invalid argument has been passed to the internal code-set conversion initializing function. Check the logic of your application program.

内部代码集转换初始化函数传递了无效参数。检查应用程序的逻辑。

-23107 DBLANG and CLIENT_LOCALE environment variables are incompatible.

DBLANG is the environment variable that points to the location where the message files are stored. Usually, the value of DBLANG corresponds with that of CLIENT_LOCALE. The value of DBLANG could be en_US.8859-1 or a value set according to X/Open standards for locale definitions.

The locale is a set of files that defines the characteristics of a particular language (for example, French or Japanese), a particular territory (for example, France or Japan) and a particular code set (for example, MS Windows Code Page 1251 or ISO 8859-1). An example of a locale name for the French language in Canada that is encoded using ISO 8859-1 would be fr_CA.8859-1, and a locale name for the Japanese language that is encoded using EUC (Extended Unix Code) would be ja_JP.ujis.

DBLANG 是指向存储消息文件的位置的环境变量。通常，DBLANG 的值与 CLIENT_LOCALE的值相对应。DBLANG 的值可以是 en_US.8859-1，也可以是根据语言环境定义的 X/Open标准设置的值。语言环境是一组定义特定语言（例如法语或日语），特定领域（例如法国或日本）和特定代码集（例如 MS Windows 代码页 1251 或ISO 8859-1）。使用 ISO 8859-1编码的加拿大法语语言的语言环境名称示例为 fr_CA.8859-1 ，使用 EUC（扩展 Unix 代码）编码的日语语言环境名称为 ja_JP.ujis。

Reexamine the value of the environment variables, DBLANG and CLIENT_LOCALE.

重新检查环境变量 DBLANG 和 CLIENT_LOCALE 的值。

-23108 An error occurred during locale structure creation.

The locale initialization failed. The program cannot allocate enough memory for the internal locale table. The memory might be exhausted due to the execution of too many processes. Rerun the program after you free some memory.

语言环境初始化失败。程序无法为内部语言环境表分配足够的内存。由于执行了太多的进程，内存可能会耗尽。释放内存后重新运行该程序。

-23109 Invalid locale specification.

A locale, with which all locale-sensitive processing occurs, is established on both the client and database server side. This processing locale is set with information from environment variables and from data that is stored in the database. An internal function could not compose the long form of the NLS locale in its internal array. Not all the categories (LC_COLLATE, LC_CTYPE, LC_MONETARY,LC_NUMERIC, LC_TIME) could be composed. Check the value of the environment variables CLIENT_LOCALE and DB_LOCALE. Also check the value of GBS_HOME and GBS_DATA.

在客户端和数据库服务器端都建立了一个语言环境，所有与语言环境有关的处理都在该语言环境中进行。此处理语言环境使用来自环境变量和存储在数据库中的数据的信息进行设置。内部函数不能在其内部数组中构成 NLS 语言环境的长格式。并非所有类别（LC_COLLATE、LC_CTYPE、LC_MONETARY、LC_NUMERIC、LC_TIME）都可以组成。检查环境变量 CLIENT_LOCALE 和 DB_LOCALE 的值。还要检查 GBS_HOME 和 GBS_DATA 的值。

-23110 An error occurred during environment variable processing.

The GLS initialization function encountered an error while it was processing the list of environment variables. The environment variables are read onto a stack for further use by various internal functions.

The environment variable values are read either from resource files or directly as shell environment variables. While the GLS initialization function was processing these values, it might have been encountered the following exceptions: end-of-file, not-found, illegal-value,unknown-value, null-value, max-path exceeded. Any of these exceptions can cause this error. Check the semantics and contents of the defined environment variables.

GLS 初始化函数在处理环境变量列表时遇到错误。环境变量被读入堆栈以供各种内部函数进一步使用。环境变量值可以从资源文件中读取，也可以直接作为 shell 环境变量读取。

虽然 GLS 初始化函数正在处理这些值，但可能遇到以下异常：文件结束、未找到、非法值、未知值、空值、超出最大路径。任何这些异常都可能导致此错误。检查定义的环境变量的语义和内容。

-23111 Internal error. Illegal argument for locale initialization.

An internal function used an illegal argument while it was initializing the GLS structures. The arguments can only be one of the following:FE_PROC, BE_PROC, or SESS_PROC. If the error recurs, see your Administrator's Guide or Reference to acquire additional diagnostics and contact GBase Technical Support with the diagnostic information.

内部函数在初始化 GLS 结构时使用了非法参数。参数只能是以下之一：FE_PROC、BE_PROC或 SESS_PROC。如果错误再次出现，请参阅“管理员指南”或“管理员参考”以获取其他诊断信息，并与诊断信息联系 GBase 技术支持。

-23112 Place holder for invalid GCV argument.

During code-set conversion, if both the input buffer and the output buffer are of NULL length, code-set conversion does not proceed, and the conversion process terminates after this error is returned. Check the logic of your application program.

在代码集转换期间，如果输入缓冲区和输出缓冲区的长度均为 NULL，则代码集转换不会继续，并且在返回此错误后转换过程将终止。检查应用程序的逻辑。

-23113 Place holder for unknown GCV error.

During code-set conversion, if the input buffer is of NULL length, this error is returned. Code-set conversion requires an input buffer and an output buffer. The input buffer is the string passed to the database server from the application program as a result of an insert or update.

Check the logic of your application program.

在代码集转换期间，如果输入缓冲区的长度为 NULL，则返回此错误。代码集转换需要输入缓冲区和输出缓冲区。输入缓冲区是由于插入或更新而从应用程序传递到数据库服务器的字符串。检查应用程序的逻辑。

-23114 Place holder for GCV truncation.

During code-set conversion of tuple data, if the output buffer is not large enough to hold the result of a code-set conversion, and the resultant string could not be truncated into the available buffer successfully, this error is returned. This error occurs in the SQL interface layer between the application program and the database server. Increase the size of the host variable that will hold the possibly expanded string that is returned after code-set conversion from a SELECT or FETCH statement.

在元组数据的代码集转换期间，如果输出缓冲区不够大，无法容纳代码集转换的结果，并且无法成功地将结果字符串截断到可用的缓冲区中，则返回此错误。此错误发生在应用程序和数据库服务器之间的SQL接口层。增加主机变量的大小，该变量将保存从SELECT 或 FETCH 语句进行代码集转换后返回的可能扩展的字符串。

-23115 Code sets of the locale categories are not the same.

On the client side or database server side, the locale is established with the following precedence of announcement mechanisms, the CLIENT_LOCALE, LANG, LC_*, and the English locale, en_US.8859-1. Given this precedence, the six categories of the processing locale are set in the following way: COLLATION, CTYPE, TIME, MONEY, NUMBER, MESSAGES.

在客户端或数据库服务器端，使用以下优先级公告机制（CLIENT_LOCALE、LANG、LC_ *和英语语言环境 en_US.8859-1）建立语言环境。鉴于此优先级，按以下方式设置处理语言环境的六个类别：COLLATION、CTYPE、TIME、MONEY、NUMBER、MESSAGES。

The GLS initialization function returned this error because an invalid locale was specified. The locale specifier is usually the environment variables. Check the value of GBS_HOME and CLIENT_LOCALE.

GBS_HOME should point to a valid directory where the GBase 8s products are installed. This directory should also contain the /gls directory where the locale and code-set files reside.

GLS 初始化函数返回此错误，因为指定了无效的语言环境。语言环境说明符通常是环境变量。检查 GBS_HOME 和 CLIENT_LOCALE 的值。GBS_HOME 应指向安装GBase 8s 产品的有效目录。该目录还应包含语言环境和代码集文件所在的 /gls 目录。

-23190 Multibyte database name is not allowed in this system.

The SE server does not allow a multibyte database name in the specified environment. Change the database name.

SE 服务器不允许在指定环境中使用多字节数据库名称。更改数据库名称。

-23194 Code-set conversion restore failed.

The database server has failed to restore the code-set conversion table to the previous state. Not enough memory is available to hold table information. Reexecute the program after you free some memory.

数据库服务器无法将代码集转换表还原到以前的状态。没有足够的内存可用于保存表信息。

释放一些内存后重新执行程序。

-23195 Reset locale failed. Connection refused.

The database server failed to change the database processing locale to en_US.8859-1. The server refused the connection. Not enough memory is available in the server for the new locale table. Reexecute the program after you free some memory.

数据库服务器无法将数据库处理语言环境更改为en_US.8859-1。服务器拒绝连接。

服务器中没有足够的内存可用于新的语言环境表。释放一些内存后重新执行程序。

-23196 Unknown locale in selected database.

The locale information that is stored in the system catalog systables of the selected database does not match the value that the DB_LOCALE environment variable specifies. Check the value of DB_LOCALE. If it is correct, drop the database and re-create it with the correct value of DB_LOCALE.

存储在所选数据库的系统目录 systables 中的语言环境信息与 DB_LOCALE 环境变量指定的值不匹配。检查 DB_LOCALE 的值。如果正确，请删除数据库并使用正确的 DB_LOCALE值重新创建它。

-23197 Database locale information mismatch.

The locale information GL_CTYPE or GL_COLLATE in the system catalog of the specified database does not match the locale information in the specified environment variable DB_LOCALE. Check the value of DB_LOCALE.

指定数据库的系统目录中的语言环境信息 GL_CTYPE 或 GL_COLLATE 与指定环境变量DB_LOCALE 中的语言环境信息不一致。检查 DB_LOCALE 的值。

-23198 GL-COLLATE information is missing from the system catalogs.

No locale information GL_COLLATE exists in the system catalog. The system catalog systables might be missing or corrupted. Drop the database and re-create it with the correct value for DB_LOCALE.

系统目录中不存在语言环境信息 GL_COLLATE。系统目录 systables 可能已丢失或损坏。删除数据库并使用正确的 DB_LOCALE 值重新创建它。

-23199 GL_CTYPE information is missing from the system catalogs.

No locale information GL_CTYPE exists in the system catalog. The system catalog systables might be missing or corrupted. Drop the database and re-create it with the correct value for DB_LOCALE.

系统目录中不存在语言环境信息 GL_CTYPE。系统目录 systables 可能已丢失或损坏。删除数据库并使用正确的 DB_LOCALE 值重新创建它。

-23501 CM error: Operation not supported on secondary coservers.

A Configuration Manager (CM) service that can be requested only on a CM coserver was made on a non-CM coserver. Contact GBase Technical Support.

配置管理器(ConfigurationManager，CM)服务只能在 CM 协同服务器上请求，该服务是在非 CM 协同服务器上生成的。

-23502 CM error: Cannot allocate memory.

The database server detected an error when it attempted to acquire a block of virtual memory from the operating system.

数据库服务器在尝试从操作系统获取虚拟内存块时检测到错误。

Contact GBase Technical Support.

请联系 GBase 技术支持。

-23503 CM error: No such dbspace.

A request for information about a dbspace, to delete a dbspace, to either add or drop a chunk from a dbspace, or to read dbspace information during startup failed because of an invalid or unused dbspace name.

请求有关 dbspace、删除d bspace、从 dbspace 中添加或删除块或在启动期间读取dbspace 信息的请求由于 dbspace 名称无效或未使用而失败。

Correct the name of the dbspace and resubmit the request. Contact GBase Technical Support.

更正 dbspace 的名称，然后重新提交请求。请联系 GBase 技术支持。

-23504 CM error: dbspace already exists.

An attempt to create a dbspace failed because a dbslice or dbspace of that name already exists.

尝试创建 dbspace 失败，因为该名称的 dbslice 或 dbspace 已存在。

Select a name that is not in use and resubmit the request using the new name, or drop the existing dbspace or dbslice and resubmit the request using the same name.

选择未使用的名称，然后使用新名称重新提交请求，或删除现有 dbspace 或 dbslice，然后使用相同的名称重新提交请求。

-23505 CM error: dbspace table overflow.

A new dbspace or dbslice was requested, but the maximum number allowed is already in use. Drop one or more obsolete dbspaces or dbslices and resubmit the request.

请求了新的 dbspace 或 dbslice，但允许的最大数量已在使用中。删除一个或多个过时的dbspace 或 dbslices，然后重新提交请求。

-23506 CM error: No such chunk.

A request to drop a chunk or to read chunk information during startup failed because the specified pathname and offset do not match any existing chunk.

在启动期间删除 chunk 或读取 chunk 信息的请求失败，因为指定的路径名和偏移量与任何现有 chunk 不一致。

Correct the pathname and offset of the chunk and resubmit the request.

If necessary, contact GBase Technical Support.

更正 chunk 的路径名和偏移量并重新提交请求。如有必要，联系 GBase 技术支持。

-23507 CM error: Chunk already exists.

A request to add a chunk to a coserver failed because the specified pathname and offset are already configured for an existing chunk.

向协同服务器添加 chunk 的请求失败，因为已为现有 chunk 配置了指定的路径名和偏移量。

To add a new chunk in addition to the existing one, either choose a different pathname for it or specify an offset beyond the end of the existing chunk within the same pathname.

要添加现有 chunk 以外的新 chunk，请为其选择不同的路径名，或者在同一路径名中指定超出现有 chunk 的末尾的偏移量。

-23508 CM error: Chunk table overflow.

An attempt to create a new chunk failed because the maximum allowed number of chunks is already in use.

尝试创建新 chunk 失败，因为最大允许的块数已在使用中。

Drop one or more obsolete chunks and resubmit the request.

删除一个或多个过时的 chunk ,并重新提交请求。

-23510 CM error: Cannot drop first chunk.

An attempt to delete the first chunk in a dbspace failed because deleting the first chunk in a dbspace is an invalid operation.

尝试删除 dbspace 中的第一个 chunk 失败，因为删除 dbspace 中的第一个 chunk 是无效操作。

Check which chunk should be dropped. To drop the dbspace after the chunk, simply drop the dbspace.

检查应删除哪个 chunk。要删除 chunk 之后删除 dbspace，只需删除 dbspace 即可。

-23511 CM error: No such dbslice.

A request for information about a dbslice, to delete a dbslice, to identify a dbslice as the basis for a logslice, or to read dbslice information during startup failed because the referenced dbslice is not in use.

由于引用的 dbslice 不在使用中，因此请求有关 dbslice 的信息、删除 dbslice、标识 dbslice 作为 logslice 的基础，或在启动期间读取 dbslice 信息的请求失败。

Correct the name of the dbslice and resubmit the request. If necessary, contact GBase Technical Support.

请更正 dbslice 的名称并重新提交请求。如有必要，请与 GBase 技术支持部门联系。

-23512 CM error: dbslice already exists.

A request for a new dbslice failed because a dbslice of that name already exists. Select a name that is not in use and resubmit the request with the new name.

对新 dbslice 的请求失败，因为该名称的 dbslice 已存在。选择未使用的名称，然后使用新名称重新提交请求。

-23513 CM error: dbslice table overflow.

A request for a new dbslice failed because the maximum allowed number is already in use. Drop one or more obsolete dbslices and resubmit the request.

由于已在使用允许的最大数目，因此请求新的 dbslice 失败。删除一个或多个过时的dbslices 并重新提交请求。

-23514 CM error: No such cogroup.

A request for information about a cogroup, to delete a cogroup, to add a coserver to a cogroup, to drop a coserver from a cogroup, to obtain a list of the coservers in a cogroup, or to read corrupted cogroup information during startup failed because the cogroup or coserver name is invalid.

请求获取有关 cogroup 的信息、删除 cogroup、将 coerver 添加到 cogroup、从cogroup 中删除协同服务器、获取 cogroup 中的协同服务器列表、或者在启动期间读取损坏的 cogroup 信息的操作失败，这是因为 cogroup 或 coserver 名称无效。

Correct the name of the cogroup and resubmit the request. If necessary, contact GBase Technical Support.

更正 cogroup 的名称，然后重新提交请求。如有必要，请与 GBase 技术支持联系。

-23515 CM error: Cogroup already exists.

An attempt to create a new cogroup failed because the name of the new cogroup is already being used by another cogroup. Choose a cogroup name that is not already in use and resubmit the request.

尝试创建新的 cogroup 失败，因为新 cogroup 的名称已被另一个 cogroup 使用。

选择尚未使用的组名称，然后重新提交请求。

-23516 CM error: Cogroup table overflow.

An attempt to create a cogroup or add a coserver to a cogroup fails because the maximum allowed number is already in use.

尝试创建 cogroup 或向协同组添加协同服务器失败，因为已允许的最大允许数量已在使用中。

Drop one or more obsolete cogroups or cogroup members and resubmit the request.

删除一个或多个过时的 cogroups 或 cogroup 成员，然后重新提交请求。

-23517 CM error: Cannot drop or alter a system defined cogroup.

A request to drop cogroup_all fails because cogroup_all cannot be dropped.

删除 cogroup_all 的请求失败，因为无法删除 cogroup_all。

Avoid requests to drop cogroup_all.

避免请求删除 cogroup_all。

-23518 CM error: No such coserver.

An invalid coserver ID caused the failure of a request to acquire information about a named coserver, to add or delete a coserver,to add a dbspace on a coserver, or to read coserver information during startup.

无效的协同服务器 ID 导致请求失败，无法获取有关命名协同服务器的信息，添加或删除协同服务器，在协同服务器上添加数据库空间，或在启动期间读取协同服务器信息。

Correct the name or ID of the coserver and resubmit the request. If necessary, contact GBase Technical Support.

更正协同服务器的名称或 ID，然后重新提交请求。如有必要，请与 GBase 技术支持联系。

-23519 CM error: Coserver already exists.

A request to add a new coserver failed because the coserver with that ID is already in use by the current instance of the database server.

添加新协同服务器的请求失败，因为带有该 ID 的 Coserver 已被数据库服务器的当前实例使用。

Recheck the coserver ID before proceeding.

继续之前，请重新检查协同服务器 ID。

-23520 CM error: Coserver table overflow.

A request to create a coserver fails because the maximum allowed number is already in use.

创建协同服务器的请求失败，因为已达到使用的最大允许数量。

-23521 CM error: An illegal identifier was specified.

A request fails because it uses an invalid identifier for cogroup or cogroup member (coserver).

请求失败，因为它使用 cogroup 或 cogroup 成员（协同服务器）的无效标识符。

For valid Identifier syntax, refer to your Administrator's Guide or the Feature Enhancements Guide for your database server.

有关有效的标识符语法，请参阅“管理员指南”或数据库服务器的“功能增强指南”。

-23522 CM error: An illegal range identifier was specified.

A request incorrectly specifies the range for a cogroup or coserver name.

The correct format for the range component is %r(first..last), with 'first'a lower number than 'last'. Embedded white space is not allowed.

Correct the specification and resubmit the request.

请求错误地指定了 cogroup 或 coserver 名称的范围。范围组件的正确格式是％r（first..last），“first”的数字低于“last”。不允许嵌入空格。更正规范并重新提交请求。

-23523 CM error: An uneven number of cogroup members was specified.

A request to create a range of cogroups from a range of coservers specified a count of coservers that is not an even multiple of the number of cogroups to create.

请求从多个 Coerers 范围创建一系列协同服务器，该请求指定了一个 coerver 计数，其数量不是要创建的协组数的偶数倍。

Adjust the numbers in the range of existing coservers or in the desired cogroups and resubmit the request.

请在现有的 coerver 范围内或在所需的协同服务器范围内调整这些数目，然后重新提交请求。

-23524 CM error: Nested cogroups not supported.

A request to create one or more cogroups specified at least one cogroup member that is actually a cogroup, rather than a coserver. Cogroup nesting is not supported.

创建一个或多个 cogroup 的请求，该请求指定至少一个 cogroup 成员，实际上是一个 cogroup，而不是一个协同服务器。不支持 Cogroup 嵌套。

Determine which of the cogroup members specified are themselves cogroups, replace their names with valid coserver names, and resubmit the request.

确定指定的哪个 cogroup 成员本身是 cogroups，用有效的协同服务器名称替换它们的名称，然后重新提交请求。

-23525 CM error: All available IDs for fragmented tables are in use.

A request to create a fragmented table failed because the maximum allowed number is already in use.

创建分片表的请求失败，因为已达到使用的最大允许数量。

Drop one or more obsolete fragmented tables and resubmit the query.

删除一个或多个过时的分片表，然后重新提交查询。

-23526 CM error: Unable to create a mutex.

Contact GBase Technical Support for help in addressing this internal error.

请联系 GBase 技术支持获取解决此内部错误的帮助。

-23527 CM error: No such logslice.

A request for information about a logslice, to delete a logslice, or to read logslice information during startup failed because an invalid or unused logslice name was specified.

由于指定了无效或未使用的 loglice 名称，因此在启动期间请求获取有关 loglice 的信息、删除日志或读取 loglice 信息的操作失败。

Correct the name of the logslice and resubmit the request. If necessary, contact GBase Technical Support.

更正日志的名称，然后重新提交请求。如有必要，请与 GBase 技术支持联系。

-23528 CM error: Logslice already exists.

A user attempted to create a logslice when a logslice of that name already exists.

当具有该名称的 logslice 已经存在时，用户试图创建一个 logslice 。

Select a name that is not in use and resubmit the request using the new name, or drop the existing logslice and resubmit the request using the same name.

选择未使用的名称，然后使用新名称重新提交请求，或删除现有的 logslice 并使用相同的名称重新提交请求。

-23529 CM error: Logslice table overflow.

A request to create a new logslice failed because the maximum number allowed is already in use.

创建新 loglice 的请求失败，因为已达到允许的最大数量。

Drop one or more obsolete logslices and resubmit the request.

删除一个或多个过时的 logslices 并重新提交请求。

-23530 CM error: No such DBspace or DBslice.

You have issued a command to the CM system to perform an operation on a dbspace or dbslice with the given name, but the system cannot find it. Make sure you have identified the dbspace or dbslice correctly,and that you are not using some other object name where a dbspace or dbslice name is required.

您已向 CM 系统发出命令，使用给定名称对 dbspace 或 dbslice 执行操作，但系统无法找到它。确保您正确标识 dbspace 或 dbslice，并且在需要 dbspace 或 dbslice 名称的地方，没有使用其他对象名称。

-23547 CM error: This would create two chunks that would overlap each other.

You have issued a command to the CM system that tries to create two chunks that will overlap.

您已向 CM 系统发出命令，尝试创建两个将重叠的 chunk。

Examine your command and re-issue it so that the two chunks are not overlapping.

检查您的命令并重新发出它，以便两个 chunk 不重叠。

-23548 CM error: This would create two chunks with the same name and offset You have issued a command to the CM system that tries to create two chunks that have exactly the same name and offset. This happens most commonly when you create chunks on different coservers (you might want to use "%c" formatting).

您已经向 CM 系统发出了一个命令，该命令试图创建两个完全相同的名称和偏移量的 chunk。

这种情况最常见的情况是在不同的辅助服务器上创建 chunk (您可能希望使用“%c”格式)。

Examine your command and re-issue it so that the two chunks have distinct names.

检查您的命令并重新发出它，以便两个 chunk 不重叠。

-23549 CM error: This would create a chunk that would overlap its own mirror.

You have issued a command to the CM system that tries to create a chunk that overlaps its mirror chunk. This happens most commonly because of arithmetic mistakes in offset calculation.

您已向 CM 系统发出命令，该命令尝试创建与其镜像 chunk 重叠的 chunk。

这种情况最常发生是因为偏移计算中的算术错误。

Examine your command and re-issue it so that the chunk and its mirror will not overlap.

检查您的命令并重新发出它，以便 chunk 和它的镜像不会重叠。

-23550 CM error: This would create a chunk that would overlap an existing chunk.

You have issued a command to the CM system that tries to create a chunk that would overlap an existing chunk.

您已向 CM 系统发出命令，该命令尝试创建与现有 chunk 重叠的 chunk。

Review the location and extent of existing chunks to find the overlap,and change your command so that it will not overlap any existing chunk space.

查看现有 chunk 的位置和范围以查找重叠，并更改命令，使其不会与任何现有 chunk 空间重叠。

-23551 CM error: Cannot alter a Logslice whose Dbslice has not been altered.

You have issued a command to alter a logslice that resides in a dbslice that has not been altered. This happens most commonly because of an incorrect logslice name, or because of being mistaken about whether a dbslice has been altered.

您已经发出一个命令来更改驻留在未被更改的 dbslice 中的 logslice 。这种情况最常见的原因是 logslice 名称不正确，或者是因为错误地认识到 dbslice 是否已被更改。

-23552 The specified dbspace (%s) does not exist.

The specified dbspace (%s) does not exist. You have issued a command to the CM system to perform an operation on the specified dbspace, but the system cannot find it.

指定的 dbspace（％s）不存在。您已向 CM 系统发出命令，对指定的 dbspace 执行操作，但系统无法找到它。

Make sure you have identified the dbspace correctly, and that you are not using a dbslice name, or some other object name, where a dbspace name is required.

确保您已正确识别 dbspace，并且未使用 dbslice 名称或其他对象名称，其中需要 dbspace 名称。

-23553 CM error: Number of read-locks held is less than zero.

This internal error should not occur. If the error recurs, note all circumstances and contact GBase Technical Support.

不应发生此内部错误。如果错误再次出现，请记录所有情况并联系 GBase 技术支持。

-23554 CM error: Number of write-locks held is less than zero.

This internal error should not occur. If the error recurs, note all circumstances and contact GBase Technical Support.

不应发生此内部错误。如果错误再次出现，请记录所有情况并联系 GBase 技术支持。

-23555 CM error: Number of write-options held is less than zero.

This internal error should not occur. If the error recurs, note all circumstances and contact GBase Technical Support.

不应发生此内部错误。如果错误再次出现，请记录所有情况并联系 GBase 技术支持。

-23556 CM error: Attempt to get write-lock without write option.

This internal error should not occur. If the error recurs, note all circumstances and contact GBase Technical Support.

不应发生此内部错误。如果错误再次出现，请记录所有情况并联系 GBase 技术支持。

-23557 CM error: Attempt to drop write-lock without write option.

This internal error should not occur. If the error recurs, note all circumstances and contact GBase Technical Support.

不应发生此内部错误。如果错误再次出现，请记录所有情况并联系 GBase 技术支持。

-23558 CM error: Attempt to drop write option without having it.

This internal error should not occur. If the error recurs, note all circumstances and contact GBase Technical Support.

不应发生此内部错误。如果错误再次出现，请记录所有情况并联系 GBase 技术支持。

-23559 CM error: CM activity detected during reversion.

CM activity (table, dbspace, dbslice, logslice, or chunk creation or deletion) detected during CM reversion. No such activity should be taking place. If it is, the reversion might not succeed.

CM 返回期间检测到的 CM 活动（表、dbspace、dbslice、loglice 或 chunk 创建或删除）。

不应该进行这样的活动。如果执行了，则复原可能不会成功。

Check whether there are any unintended connections to the database server and then restart reversion.

检查是否存在与数据库服务器的任何意外连接，然后重新启动复原。

-23561 CM error: Can't delete a Coserver ID that is not the highest ID.

You cannot delete a coserver if another coserver has a higher coserver ID.

如果另一个协同服务器具有更高的协同服务器 ID，则无法删除协同服务器。

Delete specific-purpose coservers in the reverse of their coserver ID number order.

删除与其协同服务器 ID 号顺序相反的特定用途协同服务器。

-23562 CM error: Can't delete a Coserver ID that exists in the ONCONFIG file.

You cannot delete a coserver if it is still defined in the ONCONFIG file.

如果在 ONCONFIG 文件中定义了协同服务器，则无法删除它。

Before you can use onutil to remove a coserver, you must edit The ONCONFIG file and remove the COSERVER section that defines the coserver you want to delete.

在使用 onutil 删除协同服务器之前，必须编辑 ONCONFIG 文件，删除定义要删除的协同服务器的 COSERVER 部分。

-23563 CM error: Can't enable a capability on a coserver configured as fully capable.

Fully capable coservers do not have capabilities that you can enable or disable.

功能齐全的协同服务器没有您可以启用或禁用的功能。

-23564 CM error: Can't disable a capability on a coserver configured as fully capable.

Fully capable coservers do not have capabilities that you can enable or disable.

功能齐全的协同服务器没有您可以启用或禁用的功能。

-23565 CM error: Capability is not configured on coserver.

The coserver you specified is not configured with the capability you specified.

指定的协同服务器未配置您指定的功能。

You cannot enable or disable this capability for this coserver.

您无法为此协同服务器启用或禁用此功能。

-23566 CM error: Coserver counts are inconsistent, only the delete coserver command is allowed.

The number of coservers specified in the onconfig file is less than the number of coservers that the database server discovered.

Onconfig 文件中指定的协同服务器数小于数据库服务器发现的协同服务器数。

You must delete one of the coservers.

您必须删除其中一个协同服务器。

-23567 CM error: Dynamic Coserver Management is not currently supported.

The IFMX_DCM_ENABLED environment variable is not set to 'Y'.

IFMX_DCM_ENABLED 环境变量未设置为“Y”。

To enable Dynamic Coserver Management, set the IFMX_DCM_ENABLED environment variable to 'Y'.

要启用 Dynamic Coserver Management，请将 IFMX_DCM_ENABLED 环境变量设置为“Y”。

-23568 CM error: Deleting fully-capable coserver is not supported.

You can delete only coservers configured with specific capabilities.

您只能删除配置了特定功能的协同服务器。

-23569 CM error: Permanent dbspaces are not supported on a target coserver.

The target coserver is a specific-purpose coserver that cannot host permanent table data.

目标协同服务器是一个特定目的协同服务器，不能托管永久表数据。

-23570 CM error: XTM must start in idle state to allow removing coservers from the system.

Global transactions were left running when you shut down the database server.

关闭数据库服务器时，全局事务处于运行状态。

Global transactions must be complete before you shut down the database server to remove specific-purpose coservers.

在关闭数据库服务器以删除特定用途的协同服务器之前，必须完成全局事务。

-23571 CM error: Coserver 1 must be a fully-capable coserver.

You cannot define coserver 1 as a specific-purpose coserver.

您不能将 coserver 1 定义为特定用途的协同服务器。

-23572 CM error: The Capabilities for coserver have changed.

The coserver definition in the onconfig file does not match the capabilities stored in the safewrite area when the coserver was added. You cannot change the defined capabilities of a specific-purpose coserver just by editing the onconfig file.

添加协处理器时，onconfig 文件中的协同服务器定义与 safewrite 区域中存储的功能不一致。您不能仅通过编辑 onconfig 文件来更改特定用途协同服务器的已定义功能。

You must first return the onconfig file to its previous coserver definitions and then remove the coserver, using the documented method. After you remove the coserver, you can add it again,using the documented method to define the capabilities you want it to have.

您必须首先将 onconfig 文件返回到其先前的协同服务器定义，然后使用记录的方法删除协处理器。删除协同服务器后，可以再次添加它，使用记录的方法来定义您希望它具有的功能。

-23573 CM error: The coserver type specified is invalid.

This error is internal and indicates that some function querying the CM subsystem for information about coservers has supplied an invalid coserver qualifier.

此错误是内部错误，表明某些函数在 CM 子系统中查询有关 coervers 的信息时提供了无效的 coerver 限定符。

If the error recurs, note all circumstances and contact GBase Technical Support.

如果错误再次出现，请记录所有情况并联系 GBase 技术支持。

-23600 Backup Manager Error: Out of memory.

This could be caused by either not enough main (operating system) memory or not enough internal (database server) memory. Refer to your operating-system documentation or increase the virtual memory size (SHMVIRTSIZE), the size of the added segments (SHMADD) or your total shared memory size (SHMTOTAL).

这可能是由于主内存（操作系统）不足或内部内存（数据库服务器）不足造成的。请参阅操作系统文档或增加虚拟内存大小（SHMVIRTSIZE），添加的段的大小（ SHMADD ）或总共享内存大小（SHMTOTAL）。

-23601 Backup Manager Error: A coserver can support at most one storage manager.

A coserver id has been used for the BAR_WORKER_COSVR onconfig file parameter in more than one storage manager section. Edit the onconfig file so that the values of BAR_WORKER_COSVR for each storage manager section do not overlap.

在多个存储管理器部分中，BAR_WORKER_COSVR 文件参数使用了 coserver id。编辑 onconfig 文件，使每个存储管理器部分的 BAR_WORKER_COSVR 值不重叠。

-23602 Backup Manager Error: A dbspace backup/restore is already active for this dbspace.

An attempt was made to backup or restore a dbspace that was already queued in the Backup Manager. Check the status of backup and restore sessions using"onstat -g bus" and "onstat -g bus_sm".

尝试备份或还原已在备份管理器中排队的 dbspace。使用“onstat -g bus”和“onstat -g bus_sm”检查备份和恢复会话的状态。

-23603 Invalid session name.

The specified backup or restore session name is invalid. This error displays if you use an invalid session name in the onbar [off | on | -d] session_name command, onbar -q session_name command, or onutil EBR block command.

指定的备份或还原会话名称无效。如果在 onbar [off | on | -d] session_name 命令、onbar -q session_name 命令或 onutil EBR block 命令中使用无效的会话名称，则会显示此错误。

Use onstat -g bus to list the valid backup and restore session names and retry the previous command with a valid session name.

使用 onstat -g bus 列出有效的备份和还原会话名称，并使用有效的会话名称重试上一个命令。

-23604 Backup Manager Error: This coserver does not support a storage manager.

An attempt was made to start an onbar_w process on a coserver where no storage manager was configured. Check the BAR_WORKER_COSVR parameters in the onconfig file to determine where onbar_w processes can execute. You can also use onstat -g bus_sm to obtain this information.

尝试在未配置存储管理器的协同服务器上启动 onbar_w 进程。检查 onconfig 文件中的BAR_WORKER_COSVR 参数，以确定 onbar_w 进程可以执行的位置。还可以使用 onstat -g bus_sm来获取此信息。

-23605 Backup Manager Error: An unrecognised worker id was supplied.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请注意所有情况，并联系 GBase 技术支持。

-23606 Backup Manager Error: This worker is already waiting or busy.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请注意所有情况，并联系 GBase 技术支持。

-23607 Backup Manager Error: Wait on a session which is already waiting.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请注意所有情况，并联系 GBase 技术支持。

-23608 Backup Manager Error: No object allocated to worker.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请注意所有情况，并联系 GBase 技术支持。

-23609 Backup Manager Error: Type different to that allocated to worker.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请注意所有情况，并联系 GBase 技术支持。

-23610 Backup Manager Error: Internal error - No workers ready to run.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请注意所有情况，并联系 GBase 技术支持。

-23611 Backup Manager Error: Internal error - Object not allocated.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请注意所有情况，并联系 GBase 技术支持。

-23612 Backup Manager Error: Internal coding error.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请注意所有情况，并联系 GBase 技术支持。

-23613 Backup Manager Error: The session id is already in use by another session.

A session ID supplied to onbar is the same as a currently active session ID. Resubmit the onbar command using a different session ID.

提供给 onbar 的会话 ID 与当前活动的会话 ID 相同。使用不同的会话 ID 重新提交 onbar 命令。

-23614 Backup Manager Error: Priority must be between 0 and 100.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请注意所有情况，并联系 GBase 技术支持。

-23615 Backup Manager Error: Unrecognised event type.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请注意所有情况，并联系 GBase 技术支持。

-23616 Backup Manager Error: The set placement failed for this object.

The storage manager where the backup for an object was taken could not be determined at restore time. Make sure the storage manager configuration is the same as it was when the backup was taken.

在恢复时无法确定用于获取对象备份的存储管理器。确保存储管理器配置与进行备份时的配置相同。

-23617 Backup Manager Error: That session is already suspended.

An attempt was made to suspend a session that is currently suspended. Check the status of current backup and restore sessions using onstat -g bus.

试图暂停当前已暂停的会话。使用 onstat -g bus 检查当前备份和还原会话的状态。

-23618 Backup Manager Error: That session is not suspended.

An attempt was made to resume a session that was not suspended. Check the status of current backup and restore sessions using onstat -g bus.

尝试恢复未暂停的会话。使用 onstat -g bus 检查当前备份和还原会话的状态。

-23619 Backup Manager Error: The supplied placement does not match a configured storage manager.

The storage manager that was used to back up an object is no longer configured.

Make sure the storage-manager configuration is the same as it was when the backup was taken.

用于备份对象的存储管理器已不再配置。确保存储管理器配置与备份时相同。

-23620 Backup Manager Error: The supplied timestamp value disagrees with another existing value.

The point-in-time value for a logical restore is different than the point-in-time value of a restore that is currently active. Check currently active backup and restore operations using onstat -g bus and onstat -g bus_sm.

逻辑还原的时间点值与当前活动的还原的时间点值不同。使用 onstat -g bus 和 onstat -g bus_sm检查当前活动的备份和还原操作。

-23621 Backup Manager Error: The session has been aborted.

An attempt was made to modify a backup and restore session that was aborted. Check currently active backup and restore operations using onstat -g bus and onstat -g bus_sm.

尝试修改已中止的备份和还原会话。使用onstat -g bus 和 onstat -g bus_sm检查当前活动的备份和还原操作。

-23622 Backup Manager Error: Internal error: mt_create_mutex failed.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请注意所有情况并联系 GBase 技术支持。

-23623 Backup Manager Error: Internal error: mt_create_thread failed.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请注意所有情况并联系 GBase 技术支持。

-23624 Backup Manager Error: Internal error: xmf_bf_alloc failed.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请注意所有情况并联系 GBase 技术支持。

-23625 Backup Manager Error: Internal error: xmf_reqt failed.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请注意所有情况并联系 GBase 技术支持。

-23626 Backup Manager Error: Internal error: xmf_resp failed.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请注意所有情况并联系 GBase 技术支持。

-23627 Backup Manager Error: The Dbspace is unknown to the system.

The dbspace that you have specified does not exist in your system.

Is the storage space that you specified a dbslice instead of a dbspace?Create the necessary dbspace or, if you have a dbslice, modify your statement and try again.

您指定的 dbspace 在系统中不存在。您指定的存储空间是 dbslice 而不是 dbspace吗？创建必要的 dbspace，或者，如果有 dbslice，请修改语句，然后重试。

-23628 Backup Manager Error: Internal error: cm_dbs_info failed.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请注意所有情况并联系 GBase 技术支持。

-23629 Backup Manager Warning: There are no storage managers configured. All operations will be queued.

No storage managers are configured in the onconfig files. Backup and restore requests will be queued by the Backup Manager but will not be processed until a storage manager is configured. Configure at least one storage manager in the onconfig file.

onconfig 文件中未配置存储管理器。备份管理器将对备份和还原请求进行排队，但在配置存储管理器之前不会对其进行处理。在 onconfig 文件中至少配置一个存储管理器。

-23630 Backup Manager Error: Internal error: xmf_send failed.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请注意所有情况并联系 GBase 技术支持。

-23631 Backup Manager Error: A worker onbar died while processing this object.

Refer to the Gbackuprestore logs for more information about this error.

有关此错误的详细信息，请参阅 Gbackuprestore 日志。

-23632 Backup Manager Error: There are running backups/restores on a specified coserver - all coservers can't be blocked.

You cannot block the coserver because backups or restores are currently active.

无法阻止协同服务器，因为备份或还原处于活动状态。

Wait until the backup or restore completes and retry the onutil EBR BLOCK command.

等待备份或还原完成，然后重试 onutil EBR BLOCK 命令。

-23632 The backup manager cannot do any backups or restores while LOG_BACKUP_MODE is set to NONE.

Change the setting of the LOG_BACKUP_MODE parameter in your configuration file to MANUAL or CONT and retry the request.

将配置文件中 LOG_BACKUP_MODE 参数的设置更改为 MANUAL 或 CONT，然后重试该请求。

-23633 The specified logfile does not exist.

An invalid logstream or logid was specified for a backup or restore. Check command-line parameters to onbar and retry the operation.

为备份或还原指定了无效的日志流或 logid。检查命令行参数为 onbar 并重试该操作。

-23634 Multiple storage managers backing up a single logstream is currently not supported.

A logstream ID has been used for the BAR_LOG_COSVR onconfig file parameter in more than one storage manager section. Edit the onconfig file so that the values of BAR_LOG_COSVR for each storage manager section do not overlap.

在多个存储管理器部分中，BAR_LOG_COSVR onconfig 文件参数使用了一个 logstream ID。

编辑 onconfig 文件，以便每个存储管理器节的 bar_log_COSVR 的值不会重叠。

-23635 BACKUP Manager Error (23635)The start_worker.sh shell script file in the etc sub-directory is missing or its execute permission is revoked. The Backup Manager cannot start a worker to process ON-Bar commands because it cannot execute the start_worker.sh file.

etc 子目录中的 start_worker.sh shell 脚本文件丢失或其执行权限被撤销。备份管理器无法启动工作人员处理 onbar 命令，因为它不能执行 start_worker.sh 文件。

Make sure start_worker.sh exists and can be executed by gbasedbt or root.

请确保 start_worker.sh 存在，并且可以由 Gbasedbt 或 root 执行。

-23636 Invalid coserver ID.

The specified coserver ID is invalid. This error can occur with an onutil EBR block, logical-log backup, or restore command.

指定的协同服务器 ID 无效。在使用 onutil EBR block 命令、逻辑日志备份命令或还原命令时可能会发生此错误。

Use xctl onstat - to list the valid coserver IDs and retry the previous command with a valid coserver ID.

使用 xctl onstat - 列出有效的协同服务器 ID，并使用有效的协同服务器 ID 重试前面命令。

-23637 Unable to block the coserver. Backups and restores are currently active.

An external backup or restore is already in progress. Only one external backup or restore at a time is allowed.

外部备份或还原已经在进行中。一次只允许一个外部备份或还原。

Use onstat - to see whether the database server is blocked and onstat -g bus to see which sessions are active. When the external backup or restore completes and the database server is unblocked, retry your external backup.

使用 onstat- 查看数据库服务器是否被阻塞，onstat-g bus 查看哪些会话处于活动状态。

当外部备份或还原完成并且数据库服务器解除阻塞时，请重试外部备份。

-23638 Backup Manager Error: Invalid dbspace.

An invalid dbspace name has been submitted as part of a backup or restore command.

已将无效的 dbspace 名称作为备份或还原命令的一部分提交。

Check the command line for the backup or restore operation.

检查命令行以进行备份或还原操作。

-23700 Could not write to file: coserver-number, errno, filename.

An error occurred when the database server tried to write to the reject file.

数据库服务器尝试写入拒绝文件时发生错误。

Look for operating-system messages that might give more information.

Possible causes include a full disk or a disk quota limit.

查找可能提供更多信息的操作系统消息。可能的原因包括完整磁盘或磁盘配额限制。

-23701 PLOAD: could not exclusively lock external table.

Another user is currently using the external table.

Wait for the external table to be unlocked before you proceed.

另一个用户当前正在使用外部表。

等待外部表解锁，然后再继续。

-23702 PLOAD: could not close external table.

An error occurred when the database server tried to close the external table lock. Note all circumstances and contact GBase Technical Support.

数据库服务器尝试关闭外部表锁时发生错误。请注意所有情况并联系 GBase 技术支持。

-23705 Could not open file: coserver-number, errno, filename.

An error occurred when the database server tried to open the file. Check the accompanying errno for more information. Possible causes include missing file or incorrect permissions.

数据库服务器尝试打开文件时发生错误。查看随附的 errno 以获取更多信息。

可能的原因包括丢失文件或不正确的权限。

-23706 Could not close file: coserver-number, errno, filename.

An error occurred when the database server tried to close the file. Look for operating-system messages that might give more information.

Possible causes include a full disk or hardware errors.

数据库服务器尝试关闭该文件时发生错误。查找可能提供更多信息的操作系统消息。

可能的原因包括完整磁盘或硬件错误。

-23707 Failed to read from file: coserver-number, errno, filename.

An error occurred when the database server tried to read from the file.

Check the accompanying errno for more information.

数据库服务器尝试从该文件读取时发生错误。查看随附的 errno 以获取更多信息。

-23709 File specified as a FILE type but is not: (cosvr, file)=(%s).

The file named in the external table was called a "FILE" file type,but it is not. If this file is a UNIX named pipe, change the file type in the external table to "PIPE". When the file type is declared as FILE,the server is expecting a disk file.

外部表中命名的文件被称为“FILE”文件类型，但它不是。如果此文件是 UNIX 命名管道，则将外部表中的文件类型更改为“PIPE”。当文件类型声明为文件时，服务器正在等待磁盘文件。

-23710 File specified as a PIPE type but is not: (cosvr, file)=(%s).

The file named in the external table was called a "PIPE" file type,but it is not. If this file is a disk file, change the file type in the external table to "FILE". When the file type is declared as PIPE,the server expects to open a UNIX named pipe.

外部表中命名的文件被称为“PIPE”文件类型，但它不是。如果此文件是磁盘文件，则将外部表中的文件类型更改为“FILE”。当文件类型声明为 PIPE 时，服务器打开一个UNIX 命名的 PIPE。

-23712 Illegal AIO buffer status coserver-number, errno, filename.

An error occurred when the database server tried to read or write from an internal AIO buffer. Note all circumstances and contact GBase Technical Support.

数据库服务器尝试从内部 AIO 缓冲区读取或写入时发生错误。请注意所有情况并联系 GBase 技术支持。

-23724 Could not remove file: coserver-number, errno, filename.

An error occurred when the database server tried to remove the indicated file. Look for operating-system messages that might give more information. A likely cause is improper permissions.

数据库服务器尝试删除指定的文件时发生错误。查找可能提供更多信息的操作系统消息。

可能的原因是权限不正确。

-23725 PLOAD internal error in coserver-number, errno, filename.

Note all circumstances and contact GBase Technical Support regarding this internal error.

请注意所有情况，并与 GBase 技术支持部门联系以了解此内部错误。

-23726 PLOAD (load or unload) failed to start an AIO operation errno,coserver-number, filename.

An error occurred when the database server tried to read or write to a datafile. Check the accompanying errno for more information.

数据库服务器尝试读取或写入数据文件时发生错误。查看随附的 errno 以获取更多信息。

-23730 PLOAD (unload): conversion failure.

A conversion failure occurred when the database server tried to convert the data to ASCII or EBCDIC format.

当数据库服务器尝试将数据转换为 ASCII 或 EBCDIC 格式时发生转换失败。

Check that the external table columns have enough space reserved to write the ASCII or EBCDIC representation of the data and that the columns in the external table are compatible with the data selected.

检查外部表列是否有足够的空间来写入数据的 ASCII 或 EBCDIC 表示，以及外部表中的列是否与所选数据兼容。

-23731 PLOAD (unload): datafile full.

An error occurred when the database server tried to write to the unload data file. No more space is available for writing additional data.

数据库服务器尝试写入卸载数据文件时发生错误。没有更多空间可用于编写其他数据。

Allocate more space and try again.

分配更多空间，然后再试一次。

-23732 PLOAD (unload): datafile AIO write error errno.

An error occurred when the database server tried to write to the unload datafile. Check the accompanying errno for more information.

数据库服务器尝试写入卸载数据文件时发生错误。查看随附的 errno 以获取更多信息。

-23733 PLOAD (unload): all data files are either full or bad.

An error occurred during the unload. Look for operating-system messages that might give more information. Possibly all disks are full where data files are being written or hardware problems occurred.

卸载期间发生错误。查找可能提供更多信息的操作系统消息。可能所有磁盘都已满，其中正在写入数据文件或发生硬件问题。

-23734 PLOAD: row size of target table is too large coserver-number, errno,filename.

The target table for the load has a row size that is too large. The largest row size must be the page size minus 32 bytes.

加载的目标表的行大小太大。最大行大小必须是页面大小减去 32 个字节。

-23735 PLOAD conversion error: coserver-number, errno, filename.

When the database server tried to load from the file, it encountered an error. Unless a reject file is specified in the external table, the database server returns the error message, and the load job ends without saving loaded data.

当数据库服务器试图从文件中加载时，它会遇到一个错误。除非在外部表中指定了拒绝文件，否则数据库服务器将返回错误消息，加载作业结束而不保存加载的数据。

Check for conversion errors, rows that violate constraints defined on the external table, or null columns that were defined as NOT NULL.

检查转换错误，检查违反外部表定义的约束的行，或者检查定义为 NOT NULL 的空列。

-23736 PLOAD failed to access file: coserver-number, errno, filename.

An error occurred when the database server tried to write to the reject file.

数据库服务器尝试写入拒绝文件时发生错误。

Check the accompanying operating-system error indication for more information.

有关详细信息，请查看随附的操作系统错误指示。

-23737 PLOAD could not find record end: must abort.

An error occurred when the database server tried to find a record delimiter in the delimited load file.

数据库服务器尝试在分隔的加载文件中查找记录分隔符时发生错误。

Check to see that the file has record delimiters (normally new-line characters) and that the external table has defined the correct record delimiter.

检查文件是否有记录分隔符（通常是换行符），并且外部表已定义了正确的记录分隔符。

-23738 PLOAD (unload) cannot undo partial write to filename when detecting disk full.

An error occurred when the database server tried to continue after running out of space for one data file. When the database server detects the disk-full condition, it writes to the data file a partial record, which cannot be truncated.

数据库服务器在耗尽一个数据文件的空间后继续运行时发生错误。当数据库服务器检测到磁盘已满状态时，它会向数据文件写入部分记录，该记录不会被截断。

Look for operating-system messages that might give more information.

查找可能提供更多信息的操作系统消息。

-23739 Cannot open PLOAD log file.

An error occurred when the database server tried to open the log file for a load or unload operation.

数据库服务器尝试打开日志文件进行加载或卸载操作时发生错误。

This situation occurs when one of the directories in the specified log-file name does not exist, or the directory is write protected.

当指定的日志文件名中的某个目录不存在或目录处于写保护状态时，会出现这种情况。

Check that the directory path is valid and that group gbasedbt can write to the directory.

检查目录路径是否有效，gbasedbt 组可以写入目录。

-23740 CREATE EXTERNAL TABLE: Too many keyword keywords in USING clause.

The CREATE EXTERNAL table statement (or SELECT...INTO EXTERNAL statement) contains more than one occurrence of a keyword expected in the USING clause.

CREATE EXTERNAL 表语句（或 SELECT ... INTO EXTERNA L语句）包含 USING 子句中预期的多个关键字。

Review the statement. If you meant to use another keyword, correct the statement before you reissue it.

查看语句。如果打算使用其他关键字，请在重新发布之前更正该语句。

-23741 CREATE EXTERNAL TABLE: Invalid value for keyword.

The CREATE EXTERNAL TABLE statement (or SELECT...INTO EXTERNAL statement) contains an invalid value for one of the USING clause keywords.

CREATE EXTERNAL TABLE 语句（或 SELECT ... INTO EXTERNAL 语句）包含一个无效关键字值。

Review the statement to see if the value of the keyword is misspelled.

For the MAXERRORS keyword, make sure the value is a valid number.

查看该语句以查看关键字的值是否拼写错误。对于 MAXERRORS 关键字，请确保该值为有效数字。

-23742 CREATE EXTERNAL TABLE: Invalid DATAFILES entry.

A DATAFILES entry does not have the correct format. The format for an entry is filetype:coserver-info:rooted-path-name.

DATAFILES 条目的格式不正确。条目的格式为 filetype:coserver-info:rooted-path-name。

Check that the file type is a valid type (DISK or PIPE), that the second item names a cogroup or a coserver number, and that the last item names a file that can be accessed by the coserver that manages it.

检查文件类型是否为有效类型（DISK 或 PIPE），第二项是否指定了 cogroup 或 coserver编号，以及最后一项是否指定了可由管理该文件的 coerver 访问的文件。

-23743 CREATE EXTERNAL TABLE: Missing DATAFILE entries.

The DATAFILES entry in the CREATE EXTERNAL TABLE statement (or SELECT...INTO EXTERNAL statement) is missing. Add a DATAFILES entry and reissue the statement.

在 CREATE EXTERNAL TABLE 语句（或S ELECT ... INTO EXTERNAL 语句）中缺少DATAFILES 条目。添加 DATAFILES 条目并重新发出该语句。

-23744 CREATE EXTERNAL TABLE: Cannot use SAMEAS for FIXED format tables.

The CREATE EXTERNAL TABLE statement does not allow SAMEAS for FIXED format tables. The column entries must also define an external type to describe how to access (or write) the data in the fixed file.

CREATE EXTERNAL TABLE 语句不允许对 FIXED 格式表使用 SAMEAS。列条目还必须定义外部类型，以描述如何访问（或写入）固定文件中的数据。

Revise the CREATE EXTERNAL TABLE statement to enumerate the column information and reissue the statement.

修改 CREATE EXTERNAL TABLE 语句以枚举列信息并重新发出该语句。

-23745 CREATE EXTERNAL TABLE: Internal column types must be defined column-name.

The CREATE EXTERNAL TABLE statement requires a column type for each column enumerated in the statement.

CREATE EXTERNAL TABLE 语句需要在语句中枚举的每个列的列类型。

Revise the statement. Add the appropriate column type and then reissue the statement.

修改此语句。添加适当的列类型，然后重新发出语句。

-23746 CREATE EXTERNAL TABLE: Invalid external column type column-name.

The CREATE EXTERNAL TABLE statement contains an invalid external column type.

CREATE EXTERNAL TABLE 语句包含无效的外部列类型。

Make sure the external-column types are valid: CHAR, PACKED, ZONED, or BINARY. CHAR data must be enclosed in quotes.

确保外部列类型有效：CHAR、PACKED、ZONED 或 BINARY。CHAR 数据必须用引号括起来。

-23747 CREATE EXTERNAL TABLE: FIXED or DELIMITED columns must be external chars column-name.

The CREATE EXTERNAL TABLE statement contains an external column type that is invalid. If the table describes a FIXED format file, the valid external- column types are CHAR, PACKED, ZONED, and BINARY. CHAR data must be enclosed in quotes.

CREATE EXTERNAL TABLE 语句包含无效的外部列类型。如果表描述了 FIXED 格式文件，则有效的外部列类型为 CHAR、PACKED、ZONED 和 BINARY。CHAR 数据必须用引号括起来。

If the table describes a DELIMITED format file and includes external-column types, then the type must be CHAR. A table that describes DELIMITED format files does not need to include external-column-type information.

如果表描述 DELIMITED 格式文件并包含外部列类型，则类型必须为 CHAR。

描述 DELIMITED 格式文件的表不需要包含外部列类型信息。

-23748 CREATE EXTERNAL TABLE: Missing external-column-type column-name.

The CREATE EXTERNAL TABLE statement is missing the external-column-type information. This information is required for tables that describe FIXED format files.

CREATE EXTERNAL TABLE 语句缺少外部列类型信息。描述 FIXED 格式文件的表需要此信息。

Add the column-type information and resubmit the statement.

添加列类型信息并重新提交该语句。

-23749 CREATE EXTERNAL TABLE: Only FIXED format columns can declare null column-name.

The CREATE EXTERNAL TABLE table statement has found a column defining a null string with the NULL "null-string" syntax that is invalid. Only tables that describe FIXED format files can have a null value defined with the NULL keyword.

CREATE EXTERNAL TABLE 表语句找到一个定义空字符串的列，其中 NULL "null-string"语法无效。只有描述 FIXED 格式文件的表可以使用 NULL 关键字定义空值。

Rework the statement and resubmit it.

修改此语句并重新提交。

-23750 Invalid file type in DATAFILES string datafile entry.

An error occurred when the database server tried to expand the DATAFILES entries in an INSERT or SELECT statement for an external table. The external table has a DATAFILES entry with an illegal file type. Only DISK and PIPE file types are allowed for external tables.

当数据库服务器尝试在外部表的 INSERT 或 SELECT 语句中展开 DATAFILES 条目时发生错误。外部表具有非法文件类型的 DATAFILES 条目。外部表只允许使用 DISK和 PIPE 文件类型。

Examine the external-table entry, drop the external table, and reissue a corrected CREATE EXTERNAL TABLE statement to correct this error.

检查外部表条目，删除外部表，然后重新发出修改后的 CREATE EXTERNAL TABLE语句以更正此错误。

-23751 Could not replace n macro in filename entry.

An error occurred when the database server tried to expand the node host-name macro in the filename in a DATAFILES entry in an INSERT or SELECT statement for an external table.

数据库服务器试图在外部表的 INSERT 或 SELECT 语句中的 DATAFILES 条目中的文件名中展开节点主机名宏时发生错误。

If the error recurs, note all circumstances and contact GBase Technical Support.

如果错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-23752 Could not find coserver name for coserver coserver-number, errno,filename.

An error occurred when the database server tried to expand the data files entries in an INSERT or SELECT statement for an external table.

The error occurred when the database server tried to find the coserver name in order to expand the node host-name macro in the filename.

数据库服务器试图为外部表展开 INSERT 或 SELECT 语句中的数据文件条目时发生错误。

当数据库服务器试图查找 coerver 名称以展开文件名中的节点主机名宏时，发生了此错误。

If the error recurs, note all circumstances and contact GBase Technical Support.

如果错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-23753 Could not replace %r macro in filename entry.

An error occurred when the database server tried to expand the DATAFILES entries in an INSERT or SELECT statement for an external table. The error occurred when the database server tried to expand the %r macro in the filename. Check that the syntax for the %r() macro is correct.

当数据库服务器尝试在外部表的 INSERT 或 SELECT 语句中展开 DATAFILES 条目时发生错误。

数据库服务器尝试在文件名中展开％ r宏时发生错误。检查％r() 宏的语法是否正确。

-23754 Could not replace c macro in filename entry.

当数据库服务器尝试在外部表的 INSERT 或 SELECT 语句中展开 DATAFILES 条目时发生错误。

数据库服务器尝试展开文件名中的 coserver-number 宏时发生错误。

If the error recurs, note all circumstances and contact GBase Technical Support.

如果错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-23755 Missing delimiter at end of coserver item coserver-number, errno,filename.

An error occurred when the database server tried to expand the DATAFILES entries in an INSERT or SELECT statement for an external table. The external table has a DATAFILES entry that does not have the expected colon separators between entries. The format for an entry is filetype:coserver-info:rooted-path-name.

当数据库服务器尝试在外部表的 INSERT 或 SELECT 语句中展开 DATAFILES 条目时发生错误。

外部表有一个 DATAFILES 条目，在条目之间没有预期的冒号分隔符。条目的格式为filetype:coserver-info:rooted-path-name。

Examine the external tables entry, drop the external table, and reissue a corrected CREATE EXTERNAL TABLE statement.

检查外部表条目，删除外部表，然后重新发出更正的 CREATE EXTERNAL TABLE 语句。

-23756 Unknown coserver coserver number.

当数据库服务器尝试在外部表的 INSERT 或 SELECT 语句中展开 DATAFILES 条目时发生错误。

外部表具有 DATAFILES 条目，该条目没有已知的协同服务器编号。

Examine the external tables entry, drop the external table, and reissue a corrected create external statement.

检查外部表条目，删除外部表，然后重新发出 CREATE EXTERNAL TABLE 语句。

-23757 Unknown cogroup cogroup name.

当数据库服务器尝试在外部表的 INSERT 或 SELECT 语句中展开 DATAFILES 条目时发生错误。

外部表具有 DATAFILES 条目，该条目没有已知的组名称。

Examine the external tables entry, drop the external table, and reissue the CREATE EXTERNAL TABLE statement.

检查外部表条目，删除外部表，然后重新发出 CREATE EXTERNAL TABLE 语句。

-23758 Could not parse %r macro in filename entry.

当数据库服务器尝试在外部表的 INSERT 或 SELECT 语句中展开 DATAFILES 条目时发生错误。

数据库服务器尝试在文件名中展开％r 宏时发生错误。检查％r() 宏的语法是否正确。

-23759 None of the DATAFILES strings name valid data files.

An error occurred when the database server tried to expand the DATAFILES entries in an INSERT or SELECT statement for an external table. No valid filenames were found in the DATAFILES entries.

当数据库服务器尝试在外部表的 INSERT 或 SELECT 语句中展开 DATAFILES 条目时发生错误。

在 DATAFILES 条目中找不到有效的文件名。

Examine the external tables entry, drop the external table, and reissue a corrected CREATE EXTERNAL TABLE statement.

检查外部表条目，删除外部表，然后重新发出 CREATE EXTERNAL TABLE 语句。

-23760 File name is too long (file_name).

The name of the file in the external table is too long (after expanding all the file macros). Check to see that the full path name of the file is less than 257 characters long.

外部表中文件的名称太长（在展开所有文件宏之后）。检查文件的完整路径名是否小于 257 个字符。

-23761 Cannot select from multiple external tables.

Only one external table can be used in a select query. For unions/intersects/minuses, each union/intersect/minus contributor can have one external table.

External tables are allowed as participants in joins and subqueries along with other database tables.

在 select 查询中只能使用一个外部表。对于交集/并集/差集，每个交集/并集/差集，贡献者可以有一个外部表。允许外部表与其他数据库表一起作为联接和子查询的参与者。

Check that the FROM clause contains only one external table.

检查 FROM 子句只包含一个外部表。

-23762 Null string longer than external column length or of bad format string.

The CREATE EXTERNAL TABLE statement has a column with invalid NULL"null-string" syntax. The NULL string for this column is longer than the external column length declared or is not a recognized format for the external type. If "null-string" is used to declare a NULL on a PACKED or ZONED decimal, it must conform to the formats allowed. BINARY external types must contain valid numeric values.

CREATE EXTERNAL TABLE 语句具有一个具有无效 NULL“null-string”语法的列。此列的NULL 字符串比声明的外部列长度长，或者不是外部类型的可识别格式。如果"null-string"用于在 PACKED 或 ZONED 十进制上声明 NULL，则它必须符合允许的格式。BINARY 外部类型必须包含有效的数值。

Check the CREATE EXTERNAL TABLE statement to make sure that the NULL"null-string" length agrees with the size and format defined for the external column type.

检查 CREATE EXTERNAL TABLE 语句以确保 NULL“null-string”长度与为外部列类型定义的大小和格式一致。

-23763 Cannot use a FOR UPDATE or FIRST n clause with a SELECT into an external table.

The SELECT statement contains a FOR UPDATE or FIRST n clause. When the database server unloads to an external table, these clauses are not allowed.

SELECT 语句包含 FOR UPDATE 或 FIRST n 子句。当数据库服务器卸载到外部表时，不允许使用这些子句。

Check the SELECT statement or when the SELECT cursor was defined, and make sure you do not include either of these clauses.

检查 SELECT 语句或定义 SELECT 游标时，确保不包含这些子句。

-23764 Insert into an external table must provide values for all columns in the table.

The INSERT statement does not list all the columns that the external table defines. When the database server unloads to an external table,all columns must have values described by the SELECT list.

INSERT 语句不会列出外部表定义的所有列。当数据库服务器卸载到外部表时，所有列都必须具有 SELECT 列表描述的值。

Check the INSERT statement to make sure that all columns are included in the INSERT clause and that every column has a value supplied by the SELECT list.

检查 INSERT 语句以确保 INSERT 子句中包含所有列，并且每列都具有由 SELECT 列表提供的值。

-23765 Cannot use a FOR UPDATE clause with a select from external table.

The SELECT statement contains a FOR UPDATE clause. When the database server selects from an external table, this clause is not allowed.

SELECT 语句包含 FOR UPDATE 子句。当数据库服务器从外部表中进行选择时，不允许使用此子句。

Check the SELECT statement or the cursor declared to make sure you do not include this clause.

检查 SELECT 语句或声明的游标以确保不包含此子句。

-23766 Illegal use of an external table tablename in query.

This statement describes an illegal operation on an external table. The types of operations allowed for external tables are CREATE TABLE,SELECT, SELECT INTO, INSERT, DROP TABLE, GRANT, REVOKE, CREATE SYNONYM,RENAME COLUMN, and RENAME TABLE.

该语句描述了外部表上的非法操作。外部表允许的操作类型是 CREATE TABLE、SELECT、SELECT INTO、INSERT、DROP TABLE、GRANT、REVOKE、CREATE SYNONYM、RENAME COLUMN和 RENAME TABLE。

-23767 Column too long for fixed field. (Val = value, Col = colno,Len = converted length, Max = maxLen).

When the database server tries to convert the column to FIXED file format, the size of the converted value was longer than the maximum size defined for the fixed- size field.

当数据库服务器尝试将列转换为 FIXED 文件格式时，转换后的值的大小长于为固定大小字段定义的最大大小。

Check that the external table description defines enough space in the external column type to hold the data selected after conversion.

检查外部表描述是否在外部列类型中定义了足够的空间来保存转换后选择的数据。

-23768 External table must be fixed format for external column type column-name.

An external column type of PACKED, ZONED or BINARY was found for an external table that is not defined as a FIXED-format file.

为外部表找到了外部列类型 PACKED、ZONED 或 BINARY，该外部表未定义为 FIXED 格式文件。

Only FIXED-format files can define external-column types that are not CHAR.

只有 FIXED 格式的文件才能定义非 CHAR 的外部列类型。

-23769 Unknown external column type column-name.

The CREATE EXTERNAL TABLE statement contains an external-column type that was not recognized. Valid external-column types are CHAR, PACKED,ZONED, and BINARY. CHAR values must be in quotes.

CREATE EXTERNAL TABLE 语句包含无法识别的外部列类型。有效的外部列类型是CHAR、PACKED、ZONED 和 BINARY。CHAR 值必须用引号括起来。

Check the CREATE EXTERNAL TABLE statement to make sure that the external-column types are valid.

检查 CREATE EXTERNAL TABLE 语句以确保外部列类型是有效的。

-23770 Only check constraints can be defined for external tables.

The CREATE EXTERNAL TABLE statement contains one or more types of constraint that are not allowed.

CREATE EXTERNAL TABLE语句包含一个或多个不允许的约束类型。

Check the statement for primary-key, referential, or unique constraints on a column or for the table.

检查语句中列或表的主键、参照或唯一约束。

-23771 Internal type must be a numeric type column-name.

The CREATE EXTERNAL TABLE statement contains external-column types that do not agree with the internal-column type. Whenever the external-column type is PACKED, ZONED or BINARY, the internal type must be a numeric type such as INTEGER, SMALLINT, FLOAT, or DECIMAL.

CREATE EXTERNAL TABLE 语句包含与内部列类型不一致的外部列类型。只要外部列类型为PACKED、ZONED 或 BINARY，内部类型必须是数字类型，例如 INTEGER、SMALLINT、FLOAT或 DECIMAL。

Check the CREATE EXTERNAL TABLE statement to make sure any external-column types agree with the internal-column type.

检查 CREATE EXTERNAL TABLE 语句以确保任何外部类型类型与内部列类型一致。

-23772 Internal type must be a small integer or integer column-name.

The CREATE EXTERNAL TABLE statement contains external-column types that do not agree with the internal-column type. Whenever the external-column type is BINARY, the internal type must be SMALL INTEGER or INTEGER.

CREATE EXTERNAL TABLE 语句包含与内部列类型不一致的外部列类型。只要外部列类型为BINARY，内部类型必须为 SMALL INTEGER 或 INTEGER。

Check the CREATE EXTERNAL TABLE statement to make sure any external-column types agree with the internal-column type.

检查 CREATE EXTERNAL TABLE 语句以确保任何外部列类型与内部列类型一致。

-23773 Reached max error during load coserver-number, errno, filename.

When the database server tried to load the data from the external table,one of the coservers reached the MAXERRORS limit defined for the external table.

当数据库服务器尝试从外部表加载数据时，其中一个协同服务器达到了为外部表定义的MAXERRORS 限制。

-23774 Create external table for table_name failed.

The CREATE EXTERNAL table encountered an error trying to create the catalog entry for the table. Check the accompanying ISAM error code for further information about the failure.

CREATE EXTERNAL 表在尝试为表创建目录项时遇到错误。请查看随附的 ISAM 错误代码，以获取有关故障的更多信息。

-23800 An internal error has occurred in the XTM facility.

Note all circumstances and contact GBase Technical Support regarding this internal error.

请注意所有情况，并与 GBase 技术支持部门联系以了解此内部错误。

-23801 A memory allocation error has occurred in the XTM facility.

The database server needed to allocate data-space memory to process the query, but none was available. This situation might reflect a hardware limit, an operating-system configuration limit, or a temporary shortage of space.

数据库服务器需要分配数据空间内存来处理查询，但没有一个可用。这种情况可能反映了硬件限制、操作系统配置限制或临时空间不足。

-23802 A request to idle an XTM participant has failed. Transactions are in an inconsistent state.

A nonrecoverable internal error occurred within the transaction-management system.

在事务管理系统中发生了不可恢复的内部错误。

Note all circumstances and contact GBase Technical Support.

请注意所有情况并联系 GBase 技术支持。

-23803 An XMF send has failed within the XTM facility.

An internal error occurred within the transaction-management system.

事务管理系统中发生内部错误。

Note all circumstances and contact GBase Technical Support.

请注意所有情况并联系 GBase 技术支持。

-23804 An XMF receive has failed within the XTM facility.

An internal error occurred within the transaction-management system.

事务管理系统中发生内部错误。

Note all circumstances and contact GBase Technical Support.

请注意所有情况并联系 GBase 技术支持。

-23805 An unknown transaction ID was encountered in the XTM transaction management system.

A nonrecoverable error occurred within the transaction-management system.

事务管理系统中发生了不可恢复的错误。

Note all circumstances and contact GBase Technical Support regarding this internal error.

请注意所有情况，并与 GBase 技术支持部门联系以了解此内部错误。

-23807 The backup information for the XTM coordinator is corrupted.

A nonrecoverable error occurred within the transaction-management system.

事务管理系统中发生了不可恢复的错误。

Note all circumstances and contact GBase Technical Support regarding this internal error.

请注意所有情况，并与 GBase 技术支持部门联系以了解此内部错误。

-23808 The creation of the XMF port for the XTM facility failed.

A nonrecoverable error occurred within the transaction-management system.

事务管理系统中发生了不可恢复的错误。

Note all circumstances and contact GBase Technical Support regarding this internal error.

请注意所有情况，并与 GBase 技术支持部门联系以了解此内部错误。

-23850 Table type specified twice.

The CREATE TABLE statement contains more than one table type.

CREATE TABLE 语句包含多个表类型。

Check the statement to make sure that only one table type is defined.

检查语句以确保只定义了一个表类型。

-23851 This operation is not allowed on a table where the type is raw or scratch.

An illegal operation (for example, trying to create an index) has been attempted on a RAW or SCRATCH table.

在 RAW 或 SCRATCH 表上尝试了非法操作（例如，尝试创建索引）。

You might want to alter the table type to a type that supports the operation.

您可能希望将表类型更改为支持该操作的类型。

-23852 This operation is not allowed on a table where the type is static.

The statement issued tries to modify data in the table with an UPDATE,INSERT, or DELETE statement. Data modification is not allowed on tables of type STATIC. You might want to alter the type to one of the other types that support data modification.

发出的语句尝试使用 UPDATE、INSERT 或 DELETE 语句修改表中的数据。STATIC 类型的表上不允许进行数据修改。您可能希望将类型更改为支持数据修改的其他类型。

-23853 Unable to change the type of table tablename.

An error occurred when the database server tried to alter the type of the table. Possibly you tried to alter the table type to RAW when indexes are defined on the table, or you tried to change a table to STANDARD when an archive has not been made.

数据库服务器尝试更改表的类型时发生错误。您可能尝试在表上定义索引时将表类型更改为 RAW，或者在尚未创建存档时尝试将表更改为 STANDARD。

-23854 Indexes and constraints are not allowed on tables if type is raw or scratch.

This error could occur if you try to alter a STANDARD table to RAW or SCRATCH but the table has indexes or referential constraints.

The CREATE TABLE statement contains indexes or constraints that are not allowed for RAW or SCRATCH tables. Check your statement to make sure you do not define these kinds of constraints or indexes on RAW or SCRATCH tables.

如果尝试将 STANDARD 表更改为 RAW 或 SCRATCH ，但该表具有索引或引用约束，则可能会发生此错误。CREATE TABLE 语句包含 RAW 或 SCRATCH 表不允许的索引或约束。检查语句以确保不在 RAW 或 SCRATCH 表上定义这些类型的约束或索引。

You must alter the RAW or SCRATCH table to a STANDARD table if you want to use indexes and referential constraints.

如果要使用索引和引用约束，则必须将 RAW 或 SCRATCH 表更改为 STANDARD 表。

-23855 Express mode loads are not permitted for this type of table.

An error occurred when the database server tried to execute an express-mode load on an external table created with the EXPRESS keyword. This error can happen if the external table contains blob columns or if the internal table requires logging inserts.

An internal table will require logging inserts whenever it has the type STANDARD or has referential or unique constraints.

当数据库服务器尝试在使用 EXPRESS 关键字创建的外部表上执行快速模式加载时发生错误。

如果外部表包含 blob 列或内部表需要插入日志记录，则会发生此错误。只要内部表具有STANDARD 类型或具有引用或唯一约束，它就需要记录插入。

If the internal table requires logged inserts or the external table contains blob columns, re-create the external table description without the EXPRESS keyword.

如果内部表需要日志插入，或者外部表包含 BLOB 列，则在不使用 Express 关键字的情况下重新创建外部表描述。

-23857 This operation is not allowed on tables where the type is raw or static.

An illegal operation (for example, trying to do an alter table for anything but table type) has been attempted on a RAW or STATIC table.

在 RAW 或 STATIC 表上尝试了非法操作（例如，尝试为表类型以外的任何操作执行 alter table）。

You might want to alter the table type to a type that supports the operation. Do the operation that failed. Alter the table back to the original type.

您可能希望将表类型更改为支持该操作的类型。做失败的操作。将表改回原始类型。

-23858 This operation is not allowed on a temporary table ().

The specified table is a temporary table, and the attempted operation is not allowed on a temporary table.

指定的表是临时表，并且临时表上不允许此操作。

Specify a table that is not temporary and retry the operation.

指定非临时表并重试该操作。

-23859 This operation is not allowed on a violations/diagnostics table ().

The specified table is a violations or diagnostics table, and the attempted operation is not allowed on such a table.

指定的表是违例表或诊断表，不允许在此类表上执行此操作。

Specify a table that is not a violations or diagnostics table and retry the operation.

请指定不是违例表或诊断表的表，然后重试该操作。

-23860 This operation is not allowed on a duplicated table ().

The specified table has been duplicated with the CREATE DUPLICATE statement. The attempted operation is not allowed on a duplicated table.

已使用 CREATE DUPLICATE 语句复制指定的表。重复的表上不允许尝试的操作。

To perform the operation, first issue a DROP DUPLICATE statement for . After you perform the operation against the nonduplicated table, consider whether you need to issue another CREATE DUPLICATE command to duplicate the table again.

要执行此操作，请首先为发出 DROP DUPLICATE 语句。

对非重复表执行操作后，请考虑是否需要再次发出另一 CREATE DUPLICATE命令来复制表。

-23900 freeshdic FAILED: non-exclusive access dic ref lk possible memory loss.

An error occurred when the database server tried to free memory for a shared dictionary entry. If this internal error recurs, note all circumstances and contact GBase Technical Support.

数据库服务器尝试释放共享字典条目的内存时发生错误。如果再次出现此内部错误，请记录所有情况并联系 GBase 技术支持。

-23901 Index name (index_name) with leading byte 0x20 not allowed.

In some situations, such as when a constraint is defined, the database server creates indexes internally. These indexes, by convention, always have a leading ASCII blank (hex 20) as the first byte of their name. To avoid a conflict, user-created indexes cannot have an ASCII blank (hex 20)as the first byte of their name. This rule is enforced regardless of the locale. This rule is also enforced regardless of the use of the DELIMIDENT environment variable.

在某些情况下，例如定义约束时，数据库服务器在内部创建索引。按照惯例，这些索引的名字的第一个字节总是有一个前导 ASCII 空白(hex 20)。为了避免冲突，用户创建的索引不能将ASCII 空白(hex 20)作为其名称的第一个字节。无论语言环境如何，此规则都是强制执行的。

无论 DELIMIDENT 环境变量的使用情况如何，也会强制执行此规则。

-23901 Alter table is not allowed in a multi-statement transaction.

Try separating the ALTER TABLE statement into its own single-statement transaction.

尝试将 ALTER TABLE 语句分隔为单语句事务。

-23902 Operation is not supported in SMI database (%s).

UPDATE STATISTICS cannot be run on the sysmaster database. Check your statement and make sure that the table on which you are running update statistics is not in the sysmaster database.

UPDATE STATISTICS 无法在 sysmaster 数据库上运行。检查您的语句，确保运行update statistics 的表不在 sysmaster 数据库中。

-23903 The EXPLAIN output file name must be a NON-NULL CHAR or VARCHAR.

The name given to the EXPLAIN output file is null. Provide a name for the EXPLAIN output file.

为 EXPLAIN 输出文件指定的名称为 null。提供 EXPLAIN 输出文件的名称。

-23904 Attached table (tabname) has an incompatible hash column specification.

The hash column specification of the table named in the error message is not compatible with that of the surviving table or a prior table in the attach list. All tables involved in the attach that have hash-column specifications must have identical hash-column specifications.

错误消息中指定的表的哈希列规范与附加列表中的幸存表或先前表的哈希列规范不兼容。

附加中涉及具有哈希列规范的所有表必须具有相同的哈希列规范。

-23905 Attached table (tabname) has an incompatible table type.

The table type (standard, raw, etc.) of each attached table must match that of the surviving table.

每个附加表的表类型（standard、raw 等）必须与幸存表的表类型相匹配。

-23906 Dbslice lookup failed.

This code indicates that the dbslice specified in the operation(for example, in the IN clause of the CREATE TABLE ... FRAGMENT BY statement) has not been defined. Make sure that the specified dbslice is indeed the name of an existing dbslice and not of a dbspace.

You can run the onstat utility with the -d option to see the names of defined dbspaces. Names ending with .number are dbspaces that belong to a dbslice (for example, dbsl.1 and dbsl.2 are two spaces in the dbslice dbsl).

此代码表示尚未定义操作中指定的 dbslice（例如，在 CREATE TABLE ... FRAGMENT BY语句的 IN 子句中）。确保指定的 dbslice 确实是现有 dbslice 的名称，而不是 dbspace的名称。可以使用 -d 选项运行 onstat 实用程序以查看已定义的 dbspace 的名称。

以.number 结尾的名称是属于 dbslice 的 dbspace（例如，dbsl.1 和 dbsl.2 是dbslice dbsl 中的两个空格）。

-23907 Column columnname for hash fragmentation doesn't exist.

The column name specified for hash or hybrid fragmentation was not found in the table.

在表中找不到为哈希或 hybrid 分片指定的列名。

-23908 Alter Fragment option not supported for hash fragmentation.

The surviving table has hash fragmentation and an ALTER FRAGMENT ON TABLE option other than INIT or ATTACH was specified. INIT and ATTACH are the only supported options for hash-fragmented tables.

幸存表具有散列碎片，并且指定了除 INIT 或 ATTACH 之外的 ALTER FRAGMENT ON TABLE 选项。

INIT 和 ATTACH 是散列分片表的唯一支持的选项。

-23910 Result types from case expression must be compatible.

The case expression has a result type that is incompatible with other result types in this expression. Only one type can be returned in a case expression. Review the data types in your case expression and make sure that only compatible result types are returned.

case 表达式的结果类型与此表达式中的其他结果类型不兼容。在 case 表达式中只能返回一种类型。查看 case 表达式中的数据类型，并确保返回兼容的结果类型。

-23911 Cannot update a row twice in a joined-row update.

If you do an update join, the join condition and any filters must be sufficiently strict so that no row of the update target table is produced more than once for updating. The error occurred because the same row came around twice. The query was terminated abnormally.

如果执行更新连接，则连接条件和任何过滤器必须足够严格，以使更新目标表中的行不会多次用于更新。发生此错误是因为同一行出现了两次。查询异常终止。

Either clean the data source or sources, or make the query more restrictive so that no target table row is produced more than once for updating.

要么清理数据源，要么使查询更具限制性，这样就不会产生超过一次用于更新的目标表行。

-23913 SAMPLE/LOCAL specifiers apply to tables. is not a table.

The select statement includes a SAMPLE or LOCAL keyword, but the table_name specified in the FROM clause is not a database table.

Check to see that the tables specified by the SAMPLE or LOCAL keyword in the FROM clause are not VIEWS or EXTERNAL TABLES.

select 语句包含 SAMPLE 或 LOCAL 关键字，但 FROM 子句中指定的table_name 不是数据库表。检查 FROM 子句中 SAMPLE 或 LOCAL 关键字指定的表不是 VIEWS 或 EXTERNAL TABLES。

-23914 Operation not supported on secondary coservers.

An operation that can only be performed on the MDM Primary coserver was attempted from another coserver. This is an internal error.

Note all circumstances and contact GBase Technical Support.

尝试从另一个 scerver 中执行只能在 MDM 主辅助服务器上执行的操作。

这是内部错误。注意所有情况，并与 GBase 技术支持部门联系。

-23915 Alter Fragment option not supported for hybrid fragmentation.

The surviving table has hybrid fragmentation and an ALTER FRAGMENT ON TABLE option other than INIT, ATTACH, or DETACH was specified. INIT, ATTACH,and DETACH are the only supported options for hybrid-fragmented tables.

幸存的表具有 hybrid 分片，并且指定了 INIT、ATTACH 或 DETACH 之外的 ALTE R FRAGMENT ON TABLE 选项。 INIT、ATTACH 或 DETACH 是 hybrid 分片表唯一受支持的选项。

-23916 Attached table (tabname) has an incompatible fragmentation scheme.

The fragmentation scheme of the table named in the error message is not a kind that can be attached to the surviving table in the ALTER FRAGMENT ON TABLE command.

错误消息中命名的表的分片模式不是可以附加到 ALTER FRAGMENT ON TABLE 命令中幸存的表的类型。

-23917 Unable to lock row for hold cursor.

When a lock is required for a row in a hold cursor, it must be a special type of lock so that it is not released prematurely. This error indicates that the hold cursor lock attribute could not be acquired.

当在保持光标中的行需要锁时，它必须是一种特殊类型的锁，因此它不会过早释放。

此错误指示无法获取保持光标锁的属性。

The accompanying ISAM error code might indicate the reason.

附带的ISAM错误代码可能指示原因。

-23918 Cannot create detached cluster index.

Fragmentation scheme cannot be specified when creating cluster index.

创建集群索引时无法指定分片模式。

-23920 Could not create bitmap index due to outstanding in-place alter.

A create index using bitmap statement was specified on a table that has outstanding in-place alters. The in-place alter must complete before such an index can be created. A dummy update of the entire table will cause the in-place alter to complete.

使用位图语句创建索引是在具有未完成的定点更改的表上指定的。在创建这样的索引之前，必须完成定点更改。整个表的虚拟更新将导致定点更改完成。

An example of a dummy update is an update that changes all the rows in the table and specifies that a column be set to itself.

虚拟更新的一个示例是更新，它更改表中的所有行并指定将列设置为自身。

-23921 Cannot alter table type in combination with other alter table options.

You must use separate statements to alter the table type with an ALTER TABLE statement. It cannot be done in combination with other ALTER TABLE options.

必须使用单独的语句来使用 ALTER TABLE 语句更改表类型。它不能与其他ALTER TABLE 选项组合使用。

-23922 Serial column usage incompatible with fragmentation scheme.

A table can be fragmented on a serial column only if the table is fragmented by hash and the serial column is the only column in the key. Tables fragmented by expression or hybrid that use serial columns in the fragmentation are not valid. Neither are hash-fragmented tables that have any columns in addition to the serial column used for fragmentation.

只有当表被哈希分割，而串行列是键中唯一的列时，才能在串行列上分割表。在分片中使用串行列的表达式或混合分片的表无效。除了用于分片的串行列之外，哈希分片表也不具有任何列。

-23923 HAVING clause should be accompanied by a GROUP clause or with aggregates on all columns in the SELECT clause.

The HAVING clause in a query should be accompanied by a GROUP BY clause or by a SELECT clause containing only AGGREGATES on columns or column-expressions. The HAVING clause is used to apply filter expressions on a "grouped" result. A grouped result is obtained either by using a GROUP BY clause or by using only AGGREGATES in the SELECT clause. In the latter case,the result involves only one group and the result contains only one aggregated row.

查询中的 HAVING 子句应该伴随 GROUP BY 子句或者只包含列或列表达式上的 AGGREGATES 的SELECT 子句。HAVING 子句应用于“分组”结果的过滤器表达式。分组结果是通过使用 GROUP BY子句或仅使用 SELECT 子句中的 AGGREGATES 获得的。在后一种情况下，结果只涉及一个组，结果只包含一个聚合行。

-23925 Second arg of dbinfo(dbspace/coserverid) cannot specify a view.

The dbinfo() function call has either 'dbspace' or 'coserverid' as the first argument and the second argument specifies a column name. Column names qualified by view names are not supported.

dbinfo() 函数调用 'dbspace'或 'coserverid' 作为第一个参数，第二个参数指定列名称。

不支持由视图名称限定的列名。

Check to see that the second argument specifies a column name qualified by a table name.

检查第二个参数是否指定了表名限定的列名。

-23926 Second arg of dbinfo(dbspace/coserverid) must specify a column.

The dbinfo() function has either 'dbspace' or 'coserverid' as the first argument and the second argument does not specify a column.

调用 dbinfo() 函数时，使用‘dbspace’或‘coserverid’作为第一个参数，然后以列名作为第二个参数和无效的第三个参数。

Check to see that the second argument specifies a column name qualified by a table name.

检查第二个参数是否指定了由表名限定的列名。

-23927 Third arg of dbinfo(dbspace/coserverid) must be string'currentrow'.

The dbinfo() function was called with either 'dbspace' or 'coserverid' as the first argument followed by a column name as the second argument and an invalid third argument.

调用 dbinfo() 函数时，使用‘dbspace’或‘coserverid’作为第一个参数，然后以列名作为第二个参数和无效的第三个参数。

Check to see that the third argument corresponds to the quoted string constant 'currentrow'.

检查第三个参数是否对应于引用的字符串常量‘currentrow’。

-23929 Cannot set memory resident status for a view.

The memory residency status for views cannot be changed.

无法更改视图的内存驻留状态。

-23930 GK-index creation syntax error: (message)The database server cannot create a general-key index for the reason stated in the error message. Correct the CREATE GK INDEX statement.

数据库服务器无法根据错误消息中指出的原因创建通用键索引。更正 CREATE GK INDEX 语句。

-23931 GK-index creation: FROM clause must contain LOCAL, STATIC BASE tables only.

The database server cannot create a general-key index because one of the tables in the FROM clause is either a remote table, a non-static table,or a view. Correct the CREATE GK INDEX statement.

数据库服务器无法创建通用键索引，因为 FROM 子句中的某个表是远程表、非静态表或视图。

更正 CREATE GK INDEX 语句。

-23932 GK-index creation: indexed table missing in the SELECT statement.

The FROM clause must include the table on which the index is defined. The indexed table in the FROM clause cannot be aliased. Rewrite the FROM clause of the statement.

FROM 子句必须包含定义索引的表。FROM 子句中的索引表不能为别名。重写语句的 FROM 子句。

-23933 GAM sanity error: (message)If this internal error recurs, note all circumstances and contact GBase Technical Support. Be sure to record the information given in the error message.

如果再次出现此内部错误，请记注意录所有情况并联系 GBase 技术支持。

请务必记录错误消息中给出的信息。

-23934 GAM internal error: (error_number)If this internal error recurs, note all circumstances and contact GBase Technical Support. Be sure to record the information given in the error message.

如果再次出现此内部错误，请记注意录所有情况并联系 GBase 技术支持。

请务必记录错误消息中给出的信息。

-23935 GAM: HCNF not supported yet.

This error indicates that the SELECT clause cannot be transformed into the Hybrid Conjunctive Normal Form (HCNF), an internal query representation that checks whether the index can be applied to the current query.

此错误表示 SELECT 子句无法转换为混合联合范式（HCNF），这是一种内部查询表示，用于检查索引是否可以应用于当前查询。

-23936 There are GK-indexes depending on a table in the statement.

This statement cannot be executed because general-key indexes exist that depend on a table or tables involved in the statement. Drop the general-key index that depends on the table.

无法执行此语句，因为存在依赖于语句中涉及的一个或多个表的通用键索引。

删除依赖于表的通用键索引。

To determine which GK indexes need to be dropped to correct this error,run the following query on the system catalog table:要确定需要删除哪些 GK 索引以更正此错误，请在系统目录表上运行以下查询：SELECT sysindexes.idxname, sysindexes.owner FROM systables, sysindexes, sysnewdepend WHERE systables.tabname = "<table_name>"AND systables.tabid = sysnewdepend.destid1 AND sysnewdepend.srcid2 = sysindexes.tabid AND sysnewdepend.srcid1 = sysindexes.idxname When a particular column of the GK index is involved (for example, in the case of a RENAME COLUMN statement), run the following query to determine which GK indexes need to be dropped:当涉及 GK 索引的特定列时（例如，在 RENAME COLUMN 语句中），运行以下查询以确定需要删除哪些 GK 索引：SELECT sysindexes.idxname, sysindexes.owner FROM sysindexes, systables, syscolumns, sysnewdepend WHERE systables.tabname = "<table_name>"AND syscolumns.colname = "<column_name>"AND systables.tabid = sysnewdepend.destid1 AND syscolumns.colno = sysnewdepend.destid2 AND sysnewdepend.srcid2 = sysindexes.tabid AND sysnewdepend.srcid1 = sysindexes.idxname-23937 GK-index creation: table (table_name) isn't join-on-key to the indexed table.

The error message shows the name (table_name) of the table that is not correctly joined in the WHERE clause of the statement. Change the WHERE clause to include an equality test.

该错误消息显示在语句的 WHERE 子句中未正确连接表（table_name）。更改 WHERE子句以包括相等性测试。

-23950 XBAR error: Error during dbspace backup.

Refer to the Gbackuprestore activity log and server message log for more information.

有关更多信息，请参阅 Gbackuprestore 活动日志和服务器消息日志。

-23951 XBAR error: Error during logical log backup.

Refer to the Gbackuprestore activity log and server message log for more information.

有关更多信息，请参阅 Gbackuprestore 活动日志和服务器消息日志。

-23952 XBAR error: Error during physical restore.

Refer to the Gbackuprestore activity log and server message log for more information.

有关更多信息，请参阅 Gbackuprestore 活动日志和服务器消息日志。

-23953 XBAR error: Error during logical log restore.

Refer to the Gbackuprestore activity log and server message log for more information.

有关更多信息，请参阅 Gbackuprestore 活动日志和服务器消息日志。

-23954 XBAR error: No such dbspace.

The dbspace that you have specified does not exist in your system. Check that the dbspace supplied on the onbar command line is valid.

您指定的 dbspace 在系统中不存在。检查 onbar 命令行上提供的 dbspace 是否有效。

-23958 XBAR error: Invalid argument.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次出现，请注意所有情况，并与 GBase 技术支持部门联系。

-23959 XBAR error: Internal error - Error %d from DFM %s at file %s line %d.

The Data Flow Manager (DFM) has reported an error to the XBAR subsystem.

数据流管理器(DFM)向 XBAR 子系统报告了一个错误。

Contact product support.

请联系产品支持。

-23960 XBAR error: Internal error - Unexpected message type %d received at file %s line %d.

The XBAR subsystem recieved an unexpected message for another XBAR thread.

XBAR 子系统收到另一个 XBAR 线程的意外消息。

Contact product support.

请联系产品支持。

-23961 XBAR error: Not all buffers have been backed up.

A backup client requested to commit a backup without reading all of the backup data from the database server.

备份客户端请求提交备份，而不读取数据库服务器中的所有备份数据。

Contact product support.

联系产品支持。

-23962 XBAR error: Detected error on local xplan thread. Remote thread aborting.

An XBAR thread detected an error on the client connection coserver.

XBAR 线程检测到客户端连接协服务器上的错误。

Examine the server log and onbar activity logs for the error that preceded this error.

请检查服务器日志和 onbar 活动日志，以了解此错误之前的错误。

-23963 XBAR error: Memory allocation failed.

The XBAR substem was unable to perform a memeory allocation.

XBAR 子项无法执行内存分配。

-23964 XBAR error: Internal error - Error %d from SCH %s at file %s line %d.

The Scheduler (SCH) has reported an error to the XBAR subsystem.

调度程序（SCH）已向 XBAR 子系统报告错误。

Contact product support.

联系产品支持。

-23965 XBAR error: Internal error - Error %d from XPL %s at file %s line %d.

The Xplan (XPL) subsystem has reported an error to the XBAR subsystem.

Contact product support.

Xplan（XPL）子系统向 XBAR 子系统报告了一个错误。联系产品支持。

-23966 XBAR error: Interrupt received.

The XBAR subsytem detected that its user session was interrupted.

This can occur when the client has recieved a signal or when the session was terminated using onmode.

XBAR 子系统检测到其用户会话被中断。当客户端收到信号或使用 onmode 终止会话时，可能会发生这种情况。

Retry the operation that was interrupted.

重试被中断的操作。

-23967 XBAR error: XPLAN has been aborted.

An Xplan thread has detected that Xplan was aborted.

Xplan 线程检测到 Xplan 已中止。

Consult the server message log and client message log for more information.

有关更多信息，请参阅服务器消息日志和客户端消息日志。

-23968 XBAR error: Internal error - Error %d from RSAM %s at file %s line %d.

The RSAM subsytem has reported an internal error to the XBAR subsytem.

RSAM 子系统已向 XBAR 子系统报告内部错误。

Contact product support.

联系产品支持。

-23969 XBAR error: Invalid argument to %s: %s.

An invalid argument was supplied to an XBAR interface routine.

向 XBAR 接口例程提供了无效参数。

Check the command that resulted in the error to ensure it contains valid arguments.

检查导致错误的命令，确保它包含有效参数。

-23970 XBAR error: Internal error - session control block is NULL.

An internal data structure that the XBAR subsytem needs to execute an operation does not exist.

XBAR 子系统需要执行操作的内部数据结构不存在。

Check the server log and client message logs for preceding errors.

Contact product support.

检查服务器日志和客户端消息日志以查找先前的错误。联系产品支持。

-23971 XBAR error: Internal error - operation control block is NULL.

An internal data structure that the XBAR subsytem needs to execute an operation does not exist.

XBAR子系统需要执行操作的内部数据结构不存在。

Check the server log and client message logs for preceding errors.

Contact product support.

检查服务器日志和客户端消息日志以查找先前的错误。联系产品支持。

-23972 XBAR error: Fatal error detected on xplan.

An Xplan thread has detected that Xplan was aborted.

Xplan 线程检测到 Xplan 已中止。

more information.

-23973 XBAR error: Internal error - Error %d from CM %s at file %s line %d.

The Configuration Manager (CM) has reported an error to the XBAR subsystem.

Configuration Manager（CM）已向 XBAR 子系统报告错误。

Contact product support.

联系产品支持。

-23974 XBAR error: Invalid transport buffer.

The XBAR subsytem was unable to allocate the first transport buffer for a restore.

XBAR 子系统无法为恢复分配第一个传输缓冲区。

Make sure transport buffers are configured properly. Contact product support.

确保正确配置传输缓冲区。联系产品支持。

-23975 XBAR error: Internal error - Error %d from MT %s at file %s line %d.

The MT subsytem has reported an error to the XBAR subsystem.

MT 子系统已向 XBAR 子系统报告错误。

Contact product support.

联系产品支持。

-23976 XBAR error: At least one dbspace must be specified for this operation.

No dbspace was specified for an Archecker operation.

没有为 Archeckker 操作指定 dbspace。

-23977 XBAR error: Internal error - Fatal error executing external restore. Not all dbspaces are complete.

An external restore operation finished, but not all dbspaces specified were restored.

已完成外部还原操作，但并未还原所有指定的 dbspace。

Check the server message log and client message log for more information.

检查服务器消息日志和客户端消息日志以获取更多信息。

-23979 XBAR error: Invalid coserver id.

An invalid coserver ID was specified for backup or restore.

为备份或还原指定了无效的 coserver ID。

Make sure that the coservers specified on the command line for backup or restore are valid. Check the server message log and client message log for more information.

确保命令行上指定的用于备份或还原的协同服务器有效。检查服务器消息日志和客户端消息日志以获取更多信息。

-23980 XBAR error: Duplicate coserver id.

A duplicate coserver ID was specified for backup or restore.

为备份或还原指定了重复的 coserver ID。

Make sure that the coservers specified on the command line for backup or restore do not contain duplicates. Check server message log and client message log for more information.

确保在命令行上指定的用于备份或还原的协同服务器不包含重复项。检查服务器消息日志和客户端消息日志以获取更多信息-23981 XBAR error: Allocate transport buffer failed.

An error occurred when the database server tried to allocate the transport buffers.

数据库服务器尝试分配传输缓冲区时发生错误。

Note all circumstances, save a copy of the ON-Bar activity log and database server message log, and contact GBase Technical Support.

请注意所有情况，保存 ON-Bar 活动日志和数据库服务器消息日志的副本，并与 GBase 技术支持联系。

-23982 XBAR error: Free transport buffer failed.

An error occurred when the database server tried to free the transport buffers.

数据库服务器尝试释放传输缓冲区时发生错误。

Note all circumstances, save a copy of the ON-Bar activity log and database server message log, and contact GBase Technical Support.

请注意所有情况，保存 ON-Bar 活动日志和数据库服务器消息日志的副本，并与 GBase 技术支持联系。

-24100 Cannot alter index lock mode.

An attempt to alter the lock mode of an index has failed.

尝试更改索引的锁定模式失败。

Check the accompanying ISAM error code for more information.

有关更多信息，请查看随附的 ISAM 错误代码。

-24101 Cannot specify lock mode for an index on a temporary table.

The temporary tables are session specific, which implies that there will not be any locking contention between different users. For this reason, altering the lock mode of an index on such tables is not deemed necessary.

临时表是特定于会话的，这意味着不同用户之间不会发生任何锁定争用。

因此，不需要更改此类表上索引的锁定模式。

-24112 Cannot update column (%s).

This error is generated when a user tries to update a column that is not from the target table. For example:当用户尝试更新不是目标表的列时，会生成此错误。例如：create table tab1 (col1 int, col2 int);create table tab2 (col3 int, col4 int);update tab1 set col4 = col3 + 1 from tab1, tab2 where col1 = col4;This will generate the following error because the column col4 is not from the target table tab1:这将生成以下错误，因为列 col4 不是来自目标表 tab1：24112: Cannot update column (col4).

Error in line 1 Near character position 1-24113 Table () is not a duplicated table.

The attempted operation is valid only for duplicated tables.

is not a duplicated table.

尝试的操作仅对重复的表有效。不是复制表。

Specify a duplicated table and retry the operation.

指定复制表并重试该操作。

-24114 Number of dbspace lists does not match number of fragments in table.

In the CREATE DUPLICATE statement, the number of supplied dbspace lists must match the number of fragments in the original table.

在 CREATE DUPLICATE 语句中，提供的 dbspace 列表的数量必须与原始表中的分片数一致。

Rewrite the CREATE DUPLICATE statement and specify a list of dbspaces for each original fragment of the table.

重写 CREATE DUPLICATE 语句并为表的每个原始分片指定 dbspace 列表。

-24115 Number of dbspaces per dbspace list must be identical.

In the CREATE DUPLICATE statement, the number of dbspaces in each dbspace list must be the same.

在 CREATE DUPLICATE 语句中，每个 dbspace 列表中的 dbspace 数必须相同。

Rewrite the statement to satisfy this criterion. Remember that dbslices are expanded into their component dbspaces, excluding a dbspace that the original table uses.

重写语句以满足此标准。请记住，dbslices 会扩展到其组件 dbspace 中，不包括原始表使用的 dbspace。

-24116 Duplicate dbspace () detected in CREATE DUPLICATE specification.

A dbspace name occurs more than once in this statement. In a CREATE DUPLICATE you cannot specify a dbspace name more than once.

在此语句中，dbspace 名称出现多次。在 CREATE DUPLICATE 中，不能多次指定 dbspace 名称。

Rewrite the statement using only unique dbspace names. Remember that dbslices are expanded into their component dbspaces, excluding a dbspace that the original table uses.

仅使用唯一的 dbspace 名称重写该语句。请记住，dbslices 会扩展到其组件 dbspace中，不包括原始表使用的 dbspace。

-24117 Dbspace () in CREATE DUPLICATE specification already exists in table.

The specified dbspace already contains a fragment of the table,so you cannot use the dbspace name in the CREATE DUPLICATE command.

指定的 dbspace 已经包含表的一个分片，因此不能在 CREATE DUPLICATE 命令中使用dbspace 名称。

Rewrite the statement to avoid specifying any dbspace that the original table already uses.

重写语句以避免指定原始表已经使用的 dbspace。

-24118 This ddl operation is not allowed due to deferred constraints pending on this table and dependent tables.

This transaction is running with constraint checking deferred.

After executing a DML command (INSERT/UPDATE/DELETE), a DDL command was executed on the same table. To check the pending constraints, the schema of the table cannot be changed. DDL commands can change the schema of the table; therefore, they are not allowed. If this table has a primary key and there is a foreign key referencing it,schema changes are not allowed on the table containing the foreign key. This is to check pending referential constraints. The table containing the foreign key is also referred to as a dependent table.

此事务正在运行，约束检查延迟。执行 DML 命令（INSERT/UPDATE/DELETE）后，在同一个表上执行了 DDL 命令。要检查挂起的约束，不能更改表的架构。DDL命令会更改表的模式；因此，不允许使用 DDL 命令。如果此表具有主键并且存在引用它的外键，则不允许对包含外键的表结构进行更改。这是为了检查挂起的引用约束。包含外键的表也称为从属表。

If you would like to change the schema of the table, first set the constraint mode to immediate and then retry the failing DDL command.

如果要更改表的结构，请首先将约束模式设置为 immediate，然后重试失败的 DDL 命令。

-24120 Cannot use dbinfo function in HAVING clause.

The dbinfo function cannot be used in the HAVING clause of a query.

不能在查询的 HAVING 子句中使用 dbinfo 函数。

-24121 Data Dictionary locking error (%s).

This error can occur when there is a conflict between a DML statement running on a given table and a concurrent DDL statement trying to modify that same table. The table name is specified in the error message. This conflict can occur between 2 different users, or even with a single user if that single user has an open cursor on the table being modified. In the latter case, the ISAM error code will be set to -106, non-exclusive access. The combination of SQL error code -24121 and ISAM error code -106 will uniquely indentify this situation.

当在给定表上运行的 DML 语句与尝试修改同一个表的并发 DDL 语句之间存在冲突时，可能会发生此错误。表名在错误消息中指定。这种冲突可能发生在 2 个不同的用户之间，或者甚至是单个用户，如果该单个用户在被修改的表上有一个打开的游标。在后一种情况下，ISAM 错误代码将设置为 -106，非独占访问。SQL 错误代码 -24121 和ISAM 错误代码 -106 的组合将唯一地识别这种情况。

The corrective action is to first close any cursors that reference the table being modified. The ISAM error code can give further details on the particular conflict resolution in the event the problem is multi-user related. For example, the error code might indicate that a timeout has occurred. In that case, the corrective action might be to increase the wait time (set by the command SET LOCK MODE TO WAIT).

Other error codes can indicate that a deadlock has occurred and you can look up the recommendations for the ISAM error code for descriptions and corrective actions.

纠正措施是首先关闭引用正在修改的表的任何游标。如果问题与多用户相关，ISAM 错误代码可以提供有关特定冲突解决方案的更多详细信息。例如，错误代码可能表示发生了超时。在这种情况下，纠正措施可能是增加等待时间（通过 SET LOCK MODE TO WAIT 命令设置）。

其他错误代码可能表示发生了死锁，您可以查找 ISAM 错误代码的建议以获取描述和纠正措施。

This situation is not influenced by ISOLATION LEVEL and can occur at any isolation level. This internal locking that occurs is necessary to enforce consistent metadata. Without this consistency, a variety of unpredictable and inconsistent, potentially fatal, errors can occur.

这种情况不受 ISOLATION LEVEL 的影响，并且可以发生在任何隔离级别上。发生此内部锁定是强制执行一致元数据所必需的。如果没有这种一致性，就会发生各种不可预测和不一致，可能致命的错误。

-24122 Column not specified for hash/hybrid fragmentation and there is no primary key for the table.

When a table is created with hash or hybrid fragmentation, if no column is specified as the hash key in hash or hybrid fragmentation, then the database server uses the primary key for the table as the hash key.

This error occurred because there is no primary key for the table and no hash column was specified.

当使用哈希或混合分片创建表时，如果哈希或混合分片中没有指定列作为哈希键，则数据库服务器将表的主键用作哈希键。发生此错误是因为表中没有主键，也没有指定哈希列。

For example, the following statement will get error -24122:例如，下面的语句将得到错误 -24122：create table tab (c1 int,c1 int,c2 char(10)) fragment by hybrid expression c1< 1000 in db1,remainder in db2;There are two ways to fix this statement.

有两种方式修改此语句。

1). Add a hybrid column:添加一个 hybrid 列：create table tab1 (c1 int,c2 char(10)) fragment by hybrid(c2) expression c1< 1000 in db1,remainder in db2;2). Add a primary key:添加一个主键：create table tab2 (c1 int primary key,c2 char(10)) fragment by hybrid expression c1< 1000 in db1,remainder in db2;-24123 Blobs are not allowed in the "Union" clause.

You selected a TEXT or BYTE column in a UNION query. The SELECT clause of each query cannot include any TEXT or BYTE columns. These columns are not allowed in a UNION clause because TEXT and BYTE columns cannot be tested for equality. A UNION ALL clause, however, can include TEXT and BYTE columns (in a standalone SELECT statement or in a UNION view).

您在 UNION 查询中选择了 TEXT 或 BYTE 列。每个查询的 SELECT 子句不能包含 TEXT或 BYTE列。UNION 子句中不允许使用这些列，因为无法对 TEXT 和 BYTE 列进行相等性测试。但是，UNION ALL 子句可以包含 TEXT 和 BYTE 列（在独立的 SELECT 语句中或在UNION 视图中）。

-24134 XA transaction aborted.

Statements that were active when the transaction aborted will fail and will be rolled back.

事务中止时，处于活动状态的语句都会失败并回滚。

No action is required.

无需任何操作。

-24135 Cannot prepare XA transaction.

The database server cannot prepare a distributed transaction.

The transaction has been aborted.

数据库服务器无法准备分布式事务。事务已中止。

Report this error to your DBA or DBSA.

将此错误报告给您的 DBA 或 DBSA。

-24136 CREATE DATABASE: dbspace '' not found on coserver one.

In a version 8.x database server, you can only create databases in dbspaces on the first coserver.

在 8.x 版数据库服务器中，只能在第一个协同服务器上的 dbspace 中创建数据库。

Check the dbspace name you specified for the correct spelling. If the spelling is correct, see your database server administrator for the name of a dbspace that exists on coserver one. If you do not specify a dbspace in the CREATE DATABASE statement, the database server uses the dbspace specified in the ONCONFIG file parameter DBCREATE_DBS.

检查为正确拼写指定的 dbspace 名称。如果拼写正确，请向数据库服务器管理员咨询协同服务器上存在的 dbspace 的名称。如果未在 CREATE DATABASE 语句中指定 dbspace，则数据库服务器将使用 ONCONFIG 文件参数 DBCREATE_DBS 中指定的 dbspace。

-24142 Permission denied: User cannot set mutability for environment variables.

Only a user with DBA privileges can set the mutability property of a session environment variable.The statements that set mutability for environment variables are typically used by DBA in a sysdbopen() procedure to affect a user session.

只有具有 DBA 权限的用户才能设置会话环境变量的 mutability 属性。

设置环境变量可更改性的语句通常由 DBA 在 sysdbopen() 过程中使用，以影响用户会话。

-24143 Session environment variable is immutable. Contact DBA.

DBA has made this session environment variable immutable. Contact DBA to have this property changed.

DBA 使此会话环境变量不可变。请与 DBA 联系以更改此属性。

-24145 Only permanent(base) tables can be moved.

Only user-created permanent tables can be moved across databases. The following table types cannot be moved:DBA 使此会话环境变量不可变。联系 DBA 以更改此属性：* TEMP and SCRATCH tables TEMP 和 SCRATCH 表* System catalog tables系统目录表* Active violation tables活动的违例表* Views视图-24146 Username and rolename have conflicting permissions.

During the execution of the MOVE TABLE command, one of the following situations may have occurred:在执行 MOVE TABLE 命令期间，可能发生以下情况之一：* A rolename in the source database conflicts with a username in the destination database源数据库中的角色名与目标数据库中的用户名冲突* A username in the source database conflicts with a rolename in the destination database.

源数据库中的用户名与目标数据库中的角色名冲突。

To correct this error:要更正此错误：* Do not use the ROLES option in the WITH clause of a MOVE TABLE command不要在 MOVE TABLE 命令的 WITH 子句中使用 ROLES 选项* Do not use the WITH clause with the MOVE TABLE command不要将 WITH 子句与 MOVE TABLE 命令一起使用* Revoke these conflicting permissions manually before executing a MOVE TABLE command.

在执行 MOVE TABLE 命令之前手动撤消这些冲突的权限。

-24147 Source and destination database must be different.

Use the MOVE TABLE command to move a table to a different database.

Use the RENAME TABLE command to move a table within the same database.

使用 MOVE TABLE 命令将表移动到其他数据库。使用 RENAME TABLE 命令在同一数据库中移动表。

-24148 Cannot move a table from the sysmaster and sysutils databases.

You cannot move a table from either 'sysmaster' or 'sysutils' system databases.

无法从“sysmaster”或“sysutils”系统数据库中移动表。

-24149 Owner name conflicts with role name in the destination database.

During execution of the MOVE TABLE command, a conflict occurred between the target owner name and the existing role name in the destination database.

在执行 MOVE TABLE 命令期间，目标所有者名称与目标数据库中的现有角色名称之间发生冲突。

To correct this error:要更正此错误：* Drop the conflicting role from the destination database.

从目标数据库中删除冲突的角色。

* Use the RENAME option with the MOVE TABLE command to specify a different target owner name, as in the following example:使用 MOVE TABLE命令和 RENAME 选项可以指定不同的目标所有者名称，如下例所示：- MOVE TABLE 'o1'.t1 TO DATABASE destdb RENAME '02'.t1;-24150 Only users with DBA privileges can move the table.

Only users with DBA privileges on both the source and destination databases are allowed to execute the MOVE TABLE statement.

只有在源数据库和目标数据库上具有 DBA 权限的用户才允许执行 Move table 语句。

-24200 RQM Error: Cannot find the session.

This error is reported when rmfindsession cannot find a session according to a session ID.

当 rmfindsession 根据会话 ID 找不到会话时，会报告此错误。

-24201 RQM Error: Cannot find statement sdb.

This error is reported when the parent statement descriptor cannot be found for UPDATE CURRENT.

当无法找到 UPDATE CURRENT 的父语句描述符时，将报告此错误。

-24300 Column (%s) not found in the target table.

This error is generated when a user tries to insert into a column that is not from the target table. For example:当用户尝试插入不是目标表的列时，会生成此错误。例如：create table bonus (id int, bonus int);create table emp(id int, salary int);MERGE INTO bonus D USING emp S ON D.id = S.id WHEN MATCHED THEN UPDATE SET bonus = bonus + salary*.01 WHEN NOT MATCHED THEN INSERT (id, salary) VALUES (S.id, salary);This will generate the following error because salary in the insert column list is not from the target table, bonuses:这将生成以下错误，因为插入列列表中的工资不是来自目标表，奖金：24300: Column (salary) not found in the target table.

Error in line 4 Near character position 41-24301 Table (%s) is not the target table.

This error is generated when a user tries to insert into a column that is not from the target table. For example:当用户尝试插入不是目标表的列时，会生成此错误。例如：create table bonus (id int, bonus int);create table emp(id int, salary int);MERGE INTO bonus D USING emp S ON D.id = S.id WHEN MATCHED THEN UPDATE SET bonus = bonus + salary*.01 WHEN NOT MATCHED THEN INSERT (id, emp.bonus) VALUES (S.id, salary);This will generate the following error because the emp.bonus table name is not the bonus target table:这将生成以下错误，因为 emp.bonus 表名称不是奖励目标表：24301: Table (emp) is not the target table.

Error in line 4 Near character position 47-24302 Column (%s) not found in the source table.

This error is generated when a user tries to insert into the target table using a column from the target table. For example:当用户试图使用目标表中的列插入目标表时，会生成此错误。例如：create table bonus (id int, bonus int);create table emp(id int, salary int);MERGE INTO bonus D USING emp S ON D.id = S.id WHEN MATCHED THEN UPDATE SET bonus = bonus + salary*.01 WHEN NOT MATCHED THEN INSERT (D.id, D.bonus) VALUES (S.id, bonus);This will generate the following error because in the VALUE clause the bonus column is not from the emp source table:这将产生以下错误，因为在 Value 子句中奖金列不是来自 EMP 源表：24302: Column (bonus) not found in the source table.

Error in line 4 Near character position 66-24303 Table (%s) is not the source table.

This error is generated when a user tries to insert into the target table using the column from the target table. For example:当用户试图插入到该错误时，会生成该错误。例如：create table bonus (id int, bonus int);create table emp(id int, salary int);MERGE INTO bonus D USING emp S ON D.id = S.id WHEN MATCHED THEN UPDATE SET bonus = bonus + salary*.01 WHEN NOT MATCHED THEN INSERT (D.id, D.bonus) VALUES (D.id, salary);This will generate the following error because the salary column in the VALUE clause is not from the source table, emp:这将生成以下错误，因为 VALUE 子句中的工资列不是来自源表 emp：24303: Table (d) is not the source table.

Error in line 4 Near character position 61-25539 Invalid connection-type.

The connection-type is invalid for the database server. This message appears when the database server is configured to address specific connection requests, for example for an ER or HDR connection.

连接类型对数据库服务器无效。当数据库服务器被配置为处理特定的连接请求时(例如，对于 ER 或 HDR 连接)，就会出现此消息。

-25546 Invalid network association control.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次出现，请注意所有情况，并与 GBase 技术支持部门联系。

-25548 Too many active connections.

If this sqlexecd internal error recurs, note all circumstances and contact GBase Technical Support.

如果该 sqlexecd 内部错误再次出现，请注意所有情况，并与 GBase 技术支持部门联系。

-25553 Sqlhosts file not found or cannot be opened.

The sqlhosts file is required to determine information to establish connection to a local or remote server. Create an sqlhosts file in the directory $GBS_DATA/conf according to the format that the manual for your database server product describes.

需要 sqlhosts 文件来确定与本地或远程服务器建立连接的信息。根据数据库服务器产品手册描述的格式，在 $GBS_DATA/conf 目录中创建一个 sqlhosts 文件。

-25555 Server server-name is not listed as a dbserver name in sqlhosts.

The database server name that is mentioned in the current command is not listed in the sqlhosts file. Check the server name for accuracy.

Check that all database servers to be accessed are included in the sqlhosts file.

sqlhosts 文件中未列出当前命令中提到的数据库服务器名称。检查服务器名称的准确性。

检查所有要访问的数据库服务器是否都包含在 sqlhosts 文件中。

If you are using GBase 8s SE, your current working directory might be an NFS-mounted directory. Change your current working directory to a local directory, or add appropriate local directories to your DBPATH.

如果您使用的是 GBase 8s SE，则当前工作目录可能是 NFS 安装目录。将当前工作目录更改为本地目录，或将本地目录添加到 DBPATH。

-25556 Invalid sqlhosts file format.

Check that each field in the $GBS_DATA/conf/sqlhosts file is correct and contains supported values or that the sqlhosts information in the Windows registry is correct. If you are using GBase 8s Dynamic Server,GBase 8s Universal Server, or GBase 8s OnLine Dynamic Server, check the SERVERNUM, and NETTYPE parameters in the onconfig configuration file or the gbasedbtserver entries in the registry. If you are using GBase 8s SE, check the dbservername, nettype, hostname, and servicename fields in the sqlhosts file to make sure that you have entered the correct values. For additional information, refer to your Administrator's Guide.

检查 $GBS_DATA/conf/sqlhost 文件中的每个字段是否正确并包含受支持的值，或者检查 Windows 注册表中的 sqlhost 信息是否正确。如果使用的是 GBase 8s Dynamic Server、GBase 8s Universal Server 或 GBase 8s Online Dynamic Server，请检查 ONCONFIG 配置文件或注册表中的 Gbasedbtserver 条目中的 SERVERNUM 和 NETTYPE 参数。如果使用 GBase 8s SE，请检查 sqlhost 文件中的 dbserverame、nettype、hostname 和 servicename 字段，以确保输入了正确的值。有关其他信息，请参阅“管理员指南”。

For ESQL/C: If you receive this message from an ESQL/C application in a Windows environment, check the information in the network parameters that the client computer defines. For information on setting the parameters, refer to the GBase 8s ESQL/C Programmer's Supplement for Microsoft Windows Environments.

对于 ESQL/C：如果从 Windows 环境中的 ESQL/C 应用程序收到此消息，请检查客户端计算机定义的网络参数中的信息。有关设置参数的信息，请参阅适用于 Microsoft Windows的《GBase 8s ESQL/C 程序员手册》。

For ESQL/COBOL: If you receive this message from an ESQL/COBOL application in a Windows environment, check the information in the network parameters that the client computer defines. For information on setting the parameters, refer to the GBase 8s ESQL/COBOL Programmer's Supplement for Microsoft Windows Environments.

对于 ESQL/COBOL：如果从 Windows 环境中的 ESQL/COBOL 应用程序收到此消息，请检查客户端计算机定义的网络参数中的信息。有关设置参数的信息，请参阅适用于Microsoft Windows 环境的《GBase 8s ESQL / COBOL 程序员手册》。

-25557 Network internal error.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次出现，请注意所有情况，并与 GBase 技术支持部门联系。

-25558 The NFS/RFS host host-name is not listed as a dbserver name in sqlhosts.

The database server that is mentioned in the current command resides on an NFS- or RFS-mounted file system. However, no entry exists with the NFS or RFS host for the dbservername that is listed in the sqlhosts file. Ask your GBase 8s database administrator to add the entry to the sqlhosts file. If you are using GBase 8s SE, be sure that an sqlexecd daemon is running on the NFS or RFS host.

当前命令中提到的数据库服务器驻留在 NFS 或 RFS 安装的文件系统上。但是，对于sqlhosts 文件中列出的 dbservername、NFS 或 RFS 主机，不存在任何条目。请您的GBase 8s 数库管理员将该条目添加到 sqlhosts 文件中。如果您使用的是 GBase 8s SE，请确保在 NFS 或 RFS 主机上运行 sqlexecd 守护程序。

-25559 DBPATH server server-name is not listed as a dbserver name in sqlhosts.

The database server that your DBPATH environment variable setting specifies is not listed in the $GBS_DATA/conf/sqlhosts file. Check that every database server that is mentioned in DBPATH corresponds to an entry in the sqlhosts file.

DBPATH 环境变量设置指定的数据库服务器未在 $GBS_DATA/conf/sqlhosts 文件中列出。

检查 DBPATH 中提到的每个数据库服务器是否与 sqlhosts 文件中的条目相对应。

-25561 Invalid authentication type.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次出现，请注意所有情况，并与 GBase 技术支持部门联系。

-25565 Cannot get process information.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次出现，请注意所有情况，并与 GBase 技术支持部门联系。

-25566 System time error.

See the system administrator regarding this operating-system error.

Check that the system clock is set correctly.

有关此操作系统错误，请咨询系统管理员。检查系统时钟是否设置正确。

-25567 Internal communications buffer management error detected.

Memory corruption or incorrect use of buffer-management routines usually causes this error. Check that no memory corruption problem exists in the current process space. If the error recurs, note all circumstances and contact GBase Technical Support.

内存损坏或错误使用缓冲区管理例程通常会导致此错误。检查当前进程空间中是否存在内存损坏问题。如果错误再次出现，请记录所有情况并联系 GBase 技术支持。

-25568 Debugging utility error.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此内部错误再次出现，请注意所有情况，并与 GBase 技术支持部门联系。

-25570 Network driver cannot execute the fork system call.

A system call has failed. See the system administrator for assistance.

系统调用失败。请与系统管理员联系以获取帮助。

-25571 Cannot create a user thread.

The database server cannot create or spawn a user thread for a client that is trying to establish a connection.

数据库服务器无法为尝试建立连接的客户端创建或生成用户线程。

Probable causes of the error and corrective actions include:错误和纠正措施的可能原因包括：* The database server cannot allocate system resources for the user thread at the moment. The client can retry the connection later. When other clients finish their work, some system resources should become available again. Check to see if the user is the right person to execute the utility or the program. For information about who can use what utilities, refer to the Trusted Facility Manual or your Administrator's Guide.

数据库服务器目前无法为用户线程分配系统资源。客户端可以稍后重试连接。当其他客户端完成他们的工作时，一些系统资源将再次可用。检查用户是否是执行实用程序或程序的合适人选。

有关谁可以使用哪些实用程序的信息，请参阅“受信任设施手册”或“管理员指南”。

* A user who is not allowed to use a particular client application to connect to the database server tried to use the utility to connect. Client applications include SQL APIs, DB-Access,and all the database server utilities.

不允许使用特定客户端应用程序连接到数据库服务器的用户尝试使用该实用程序进行连接。

客户端应用程序包括 SQLAPI、DB-Access 和所有数据库服务器实用程序。

* A request for a Global Language Support (GLS) structure failed.

Refer to the corrective actions for errors -23100, -23101, - 23102, -23104,-23108, and -23110 for possible solutions.

请求全局语言支持(GLS)结构失败。可能的解决方案请参阅错误纠正措施-23100、-23101、-23102、-23104、-23108 和 -23110。

* A user attempting to connect to the database server does not belong to the database server user group, as defined in$GBS_HOME/dbssodir/seccfg on a UNIX system or in the registry on a Windows system. Make sure that the user belongs to a user group that can access the database server. For more information about DBSSO users, see the Trusted Facility Manual.

试图连接到数据库服务器的用户不属于数据库服务器用户组，如 UNIX 系统上的$GBS_HOME/dbssodir/seccfg 或 Windows 系统上的注册表中所定义。确保该用户属于可以访问数据库服务器的用户组。有关 DBSSO 用户的详细信息，参阅“受信任设施手册”。

-25572 Network driver cannot bind a name to the port.

A system call has failed. The sqlexecd daemon or database server cannot access the network port that is specified by the servicename in the sqlhosts file. This situation might occur because the network port is already in use by another sqlexecd, database server, or other application.

系统调用失败。sqlexecd 守护程序或数据库服务器无法访问 sqlhosts 文件中 servicename指定的网络端口。出现这种情况的原因可能是网络端口已被其他 sqlexecd、数据库服务器或其他应用程序使用。

-25573 Network driver cannot accept a connection on the port.

A system call has failed. See the system administrator for assistance.

系统调用失败。请与系统管理员联系以获取帮助。

-25574 Network driver cannot open the network device.

A system call has failed. See the system administrator for assistance.

系统调用失败。请与系统管理员联系以获取帮助。

-25575 Network driver cannot allocate the call structure.

A system call has failed. See the system administrator for assistance.

系统调用失败。请与系统管理员联系以获取帮助。

-25576 Network driver cannot allocate the return structure.

A system call has failed. See the system administrator for assistance.

系统调用失败。请与系统管理员联系以获取帮助。

-25577 Network driver cannot get a host structure.

A system call has failed. See the system administrator for assistance.

系统调用失败。请与系统管理员联系以获取帮助。

-25578 Network driver cannot disconnect from the network.

A system call has failed. See the system administrator for assistance.

系统调用失败。请与系统管理员联系以获取帮助。

-25579 Network function was issued in the wrong sequence.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请记录所有情况并联系 GBase 技术支持。

-25580 System error occurred in network function.

A system call has failed. For assistance, contact your system administrator or GBase Technical Support.

系统调用失败。如需帮助，请联系系统管理员或 GBase 技术支持。

-25581 Transport Layer memory free error.

This message indicates a system problem. It might be a problem with freeing memory. Retry the connection and then see the system administrator for assistance.

此消息表示系统问题。这可能是释放内存的问题。重试连接，然后向系统管理员寻求帮助。

-25582 Network connection is broken.

The connection terminated because the network is down, the database server is offline, or the client is offline. If you receive this error on a client,check the network connection, and the database server. If you receive this error on the database server, check the network connection, and the client.

连接因网络中断、数据库服务脱机或客户端脱机而终止。如果在客户端上收到此错误，请检查网络连接和数据库服务器。如果在数据库服务器上收到此错误，请检查网络连接和客户端。

-25583 Unknown network error.

See the system administrator or the network administrator for assistance.

请与系统管理员或网络管理员联系并获取帮助。

-25584 Network driver cannot access the server program program-name.

Check that the GBASEDBTSERVER environment variable correctly specifies the default server name and that the default server name and the service name entries in the sqlhosts file are correct.

检查 GBASEDBTSERVER 环境变量是否正确指定了缺省服务器名称，以及 sqlhosts 文件中的缺省服务器名称和服务名称条目是否正确。

-25585 Invalid buffer size.

The buffer size that is specified in the servicename column is not valid. Check that the servicename column of your sqlhosts file is correct.

servicename 列中指定的缓冲区大小无效。检查 sqlhosts 文件的 servicename 列是否正确。

-25586 Network send failed.

A system call has failed. See the system administrator for assistance.

系统调用失败。请与系统管理员联系以获取帮助-25587 Network receive failed.

A system call has failed. Perform a DISCONNECT and then check the status of the server. See the system administrator for assistance.

系统调用失败。执行 DISCONNECT，然后检查服务器的状态。请与系统管理员联系以获取帮助。

-25588 The appl process cannot connect to Dynamic Server.

An error in the application can produce this message. Check your CONNECT statement and the sqlhosts file. A system failure can also produce this message. If you can find no immediate cause for the failure, note the circumstances and contact your database server administrator for assistance.

应用程序中的错误可以生成此消息。检查 CONNECT 语句和 sqlhosts 文件。

系统故障也可以产生此消息。如果找不到导致故障的直接原因，请记录相关情况并与数据库服务器管理员联系以获取帮助。

The shared memory communication subsystem is down or not functioning.

Contact the database server administrator to report the problem.

共享内存通信子系统已关闭或无法运行。请联系数据库服务器管理员以报告问题。

-25589 Invalid database server mail-box message type.

A system call has failed. See your system administrator for assistance.

系统调用失败。请与系统管理员联系以获取帮助。

-25590 Authentication error.

This error indicates that an invalid user ID or password was used to connect to the database server. Provide a valid user ID and password.

此错误表示使用了无效的用户标识或密码来连接到数据库服务器。提供有效的用户 ID 和密码。

This error can also occur if the CSM option is enabled on the database server side but disabled on the client application side, or vice versa.

If you want to use a CSM, make sure that the CSM option is set in the sqlhosts file for both the database server and client application.

如果在数据库服务器端启用了 CSM 选项但在客户端应用程序端禁用了 CSM 选项，则也会发生此错误，反之亦然。如果要使用 CSM，请确保在 sqlhosts 文件中为数据库服务器和客户端应用程序设置了 CSM 选项。

-25591 Transport control received an invalid connection address.

Check the hostname and servicename entries in the $GBS_DATA/conf/sqlhosts file for the desired database server. Verify with the DBA and the system administrator that the hostname and servicename are spelled correctly. If you are using TCP/IP, also verify that the hostname and servicename have corresponding entries in the /etc/hosts and the /etc/services files,respectively, on the client computer.

检查 $GBS_DATA/conf/sqlhosts 文件中的 hostname 和 servicename 条目，以查找所需的数据库服务器。与 DBA 和系统管理员确认主机名和服务名称拼写正确。如果您使用的是 TCP/IP，还要验证主机名和服务名称在客户端计算机上的 /etc/hosts 和 /et/services 文件中是否分别有相应的条目。

-25592 Communications service not supported by network driver.

The network service that was requested for this connection, such as TCP with sockets or TCP with TLI, is not available on the desired system or the specified database server. Use a supported network service; verify that the nettype field is correctly specified for the desired database server in the $GBS_DATA/conf/sqlhosts file. If the network service is available on the system but not on the database server, ask your DBA to turn on the service when the DBA initializes the database server.

为此连接请求的网络服务（例如带有套接字的 TCP 或带有 TLI 的 TCP）在所需系统或指定的数据库服务器上不可用。使用支持的网络服务;验证是否在 $GBS_DATA/conf/sqlhosts文件中为所需的数据库服务器正确指定了 nettype 字段。如果网络服务在系统上可用但在数据库服务器上不可用，请在 DBA 初始化数据库服务器时请求 DBA 打开服务。

-25593 Network listener failed to make an open I/O channel to be non-blocking.

Report this operating-system error to the operating-system administrator. It might require a system reboot.

将此操作系统错误报告给操作系统管理员。它可能需要重新启动系统。

-25594 Shared Memory client failed to alert the database server for service.

There are two possible reasons for this error:这个错误有两个可能的原因：If the error number is zero, the problem is memory corruption.

如果错误号为零，则问题是内存损坏。

If the error number is not zero, an operating system call failed, usually because a semaphore operation could not be performed.

如果错误号不为零，则操作系统调用失败，通常是因为无法执行信号量操作。

Report the problem to the system administrator, who should restart the database server or restart the computer. In either case, call GBase Support.

For operating system call failure, Support might advise you to set the environment variables IFX_SEMOP_INTERVAL or IFX_SEMOP_RETRY.

将问题报告给系统管理员，系统管理员应重新启动数据库服务器或重新启动计算机。在任何一种情况下，请致电 GBase 技术支持。对于操作系统调用失败，建议您设置环境变量 IFX_SEMOP_INTERVAL 或 IFX_SEMOP_RETRY。

-25595 Invalid message received during connection attempt.

An error occurred when you tried to connect to the desired database server.

尝试连接到所需的数据库服务器时发生错误。

If you are using GBase 8s Dynamic Server, GBase 8s Universal Server, or GBase 8s OnLine Dynamic Server, verify that the database server is still online. If you are using GBase 8s SE, verify that the sqlexecd daemon for the database server is still running. Also, verify that the$GBS_DATA/conf/sqlhosts file entry for the database server is correct.

如果您使用的是 GBase 8s Dynamic Server、GBase 8s Universal Server 或GBase 8s OnLine Dynamic Server，请验证数据库服务器是否仍在联机状态。

如果您使用的是 GBase 8s SE，请验证数据库服务器的 sqlexecd 守护程序是否仍在运行。另外，验证数据库服务器的 $GBS_DATA/conf/sqlhosts 文件条目是否正确。

-25597 Error in system pipe processing.

This system failure might indicate a problem accessing environment variables. Note the system error number and see the operating-system administrator for assistance.

此系统故障可能表示访问环境变量时出现问题。请记下系统错误编号，并向操作系统管理员寻求帮助。

-25598 Communications usage error: Invalid state transition.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请注意所有情况并联系 GBase 技术支持。

-25599 Network connection error - no listener.

The client application is attempting to connect to a remote server.

However, no listener daemon is running on the remote host. Check that the listener daemon is started on the remote host and retry the connection.

客户端应用程序正在尝试连接到远程服务器。但是，远程主机上没有运行 listener 守护程序。检查是否在远程主机上启动了 listener 守护程序，然后重试连接。

-25600 The relay module cannot get environment variable SQLRM. System error error-number.

Check with your system administrator for problems with the system.

有关系统问题，请咨询系统管理员。

-25601 This relay module cannot execute relay module module-name for another protocol.

Validate that the named relay module is installed on your system.

验证系统上是否已安装指定的中继模块。

-25602 The local database server server-name cannot be forked by the relay module. System error number.

Check with your system administrator for problems with the system.

有关系统问题，请咨询系统管理员。

-25603 Attempt to prepare more than one statement before connecting to a database.

Check your application to make sure that you prepare only one of the CREATE DATABASE, START DATABASE, or DROP DATABASE statements before you connect to a database.

检查应用程序以确保在连接到数据库之前只准备一个 CREATE DATABASE、START DATABASE或 DROP DATABASE 语句。

-25604 The database name syntax conflicts with the options in the statement.

Check your application to make sure that your database syntax uses the correct options accordingly in the statements.

检查应用程序以确保数据库语法在语句中相应地使用正确的选项。

-25605 SQLEXEC must be set to create a local database using the relay module.

Check that you have set the SQLEXEC environment variable to the local GBase 8s SE database server。

检查是否已将 SQLEXEC 环境变量设置为本地 GBase 8s SE 数据库服务器。

-25606 Unknown product identification string in the database server on the local machine.

Check that you have installed the database server.

检查是否已安装数据库服务器。

-25607 Statement not supported. Database not selected yet.

You issued an SQL statement that requires an open database, but you did not select a database. Select the desired database and retry the statement.

您发出了一个需要打开数据库的 SQL 语句，但没有选择数据库。选择所需的数据库并重试该语句。

-25700 UUID Cache corrupted/not initialized.

The database server's list of server UUIDs has become corrupted.

数据库服务器的服务器 UUID 列表已损坏。

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此内部错误，请注意所有情况并联系 GBase 技术支持。

-25701 The specified servername is not in SYSSERVERS.

You attempted to use ALTER SERVERUUID with a database server name that is not in the sysservers table of the syscdr database.

您试图将 ALTER SERVERUID 与不在 syscdr 数据库的 sysserver表中的数据库服务器名称一起使用。

Modify the ALTER SERVERUUID statement to use a database server name that is in the sysservers table.

请修改 ALTER SERVERUID 语句，使用 sysservers 表中的数据库服务器名称-25702 Error receiving the UUID from remote server .

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况并与 GBase 技术支持部门联系。

-25703 UUID cache not initialized.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况并与 GBase 技术支持部门联系。

-25704 Attempt to increment/decrement the reference count on a remote smartblob.

You cannot update the reference count for a large object (BLOB or CLOB) that is on a remote server. Also, you cannot store references to a local large object in a remote table.

您无法更新远程服务器上的大对象（BLOB 或 CLOB）的引用计数。此外，不能存储对远程表中的本地大对象的引用。

Verify that all commands that manage reference counts refer only to large objects that are in the local database.

验证管理引用计数的所有命令仅引用本地数据库中的大对象。

-25705 Invalid UUID. Server name corresponding to the UUID cannot be located.

If this error recurs, note all circumstances and contact GBase Technical Support.

如果再次出现此错误，请注意所有情况并联系 GBase 技术支持。

-25706 Attempt to delete ServerUuid entry for the local server.

You issued the statement DROP SERVERUUID where is the current database server. A database server cannot drop its own UUID.

您发出了语句 DROP SERVERUUID ，其中是当前数据库服务器。

数据库服务器无法删除自己的UUID。

Change in your DROP SERVERUUID statement.

修改 DROP SERVERUUID 语句中的。

-25707 Attempt to alter ServerUuid entry for local server.

You issued the statement ALTER SERVERUUID where is the current database server. A database server cannot alter its own UUID.

您发出了语句 ALTER SERVERUUID ，其中是当前数据库服务器。

数据库服务器无法更改自己的UUID。

Change in your ALTER SERVERUUID statement.

修改 ALTER SERVERUUID 语句中的。

-25708 Unable to find servername from UUID.

This error can arise when a client application gets a UUID from one database server and attempts to use that UUID on another system. If, on the second database server, the sysserver table of the syscdr database is not up-to-date, the UUID value on the second database server might either be missing or disagree with the UUID value on the first database server.

当客户端应用程序从一个数据库服务器获取 UUID 并尝试在另一个系统上使用该 UUID 时，可能会出现此错误。如果在第二个数据库服务器上，syscdr 数据库的 sysserver 表不是最新的，则第二个数据库服务器上的 UUID 值可能会丢失或不同意第一个数据库服务器上的 UUID 值。

检查UUID值的来源。验证UUID值是否来自您尝试使用它的数据库服务器，或验证两个数据库服务器上的 syscdr 数据库是否是最新的。

Suppose you had three database servers, A, B, and C. Database server A has communicated with C, thus causing the syscdr tables on A and C to be updated.

However, database server B has never communicated with C, so the syscdr database on B does not contain a UUID for C. If the application obtains a large-object handle from A that refers to a large object on C and then sends that LO handle to B, B can tell that the LO handle refers to a remote site but cannot resolve the UUID.

假设您有三个数据库服务器：A、B 和 C。数据库服务器 A 已与 C 通信，从而导致更新 A 和 C 上的 syscdr 表。但是，数据库服务器 B 从未与 C 通信，因此 B 上的 syscdr 数据库不包含 C 的UUID。如果应用程序从 A 获取大对象句柄，该句柄引用 C 上的大对象，然后发送该 LO 句柄到 B，B 可以判断 LO 句柄引用了远程站点但无法解析 UUID。

Check the source of the UUID value. Verify that the UUID value is from the database server on which you are attempting to use it or verify that the syscdr databases are up-to-date on both database servers.

检查 UUID 值的来源。验证 UUID 值是否来自尝试使用它的数据库服务器，或验证两个数据库服务器上的 syscdr 数据库是否是最新的。

-25710 Invalid routine structure in server to server fastpath call.

This error can occur if you use an invalid MI_FUNC_DESC value.

如果使用无效的 MI_FUNC_DESC 值，则会发生此错误。

However, the error is probably an internal error. If the error recurs,note all circumstances and contact GBase Technical Support.

但是，错误可能是内部错误。如果错误再次出现，请注意所有情况并联系 GBase 技术支持。

-25711 No more than three connections can be involved in a single fastpath call.

You executed a routine that opens a remote connection that in turn calls another routine that opens a remote connection, and so on. The result is that the nested routines try to open more than the maximum allowed number of connections.

您执行了一个打开远程连接的例程，该例程又调用另一个打开远程连接的例程，依此类推。结果是嵌套例程尝试打开的连接数超过允许的最大数量。

Examine your routines and reduce the number of connections requested.

检查您的例程并减少请求的连接数。

-25712 Routine <routine_name> cannot be called from a remote server.

The database server cannot access the routine <routine_name> from a remote database server.

数据库服务器无法访问来自远程数据库服务器的例程 <routine_name>。

Install <routine_name> on your local database server before calling it.

在调用之前，在本地数据库服务器上安装 <routine_name>。

-25713 Attempting to run a cross server routine <routine_name> in parallel.

You have attempted to execute a routine on a remote database server in parallel.Routines that execute remotely should not be parallelizable.

您试图并行执行远程数据库服务器上的例程。远程执行的例程不应该是可并行的。

Remove the PARALLELIZABLE modifier from the definition of the routine<routine_name>.

从例程 <routine_name> 的定义中删除 PARALLELIZABLE 修饰符。

-25718 Cannot insert or update from a nonlogging database to a logging database.

When the local database is nonlogging, the only operations allowed on a remote database are operations that read information. You cannot change information on a remote database when the local database is nonlogging.

当本地数据库是非日志记录时，远程数据库上允许的唯一操作是读取信息的操作。

当本地数据库不进行日志记录时，您无法更改远程数据库上的信息。

Remove the insert or update operation, or change the local database to a logging database, or change the remote database to a nonlogging database.

删除插入或更新操作，或将本地数据库更改为日志记录数据库，或将远程数据库更改为非日志记录数据库。

-25720 Invalid combination of modifiers DISTRIBUTEBINARY and .

An opaque data type cannot have the both the modifier and DISTRIBUTEBINARY.

不透明数据类型不能同时具有修饰符和 DISTRIBUTEBINARY。

Modify your CREATE OPAQUE TYPE or ALTER OPAQUE TYPE statement to remove the inappropriate modifier.

修改 CREATE OPAQUE TYPE 或 ALTER OPAQUE TYPE 语句，删除不适当的修饰符。

-25721 Invalid combination of modifiers ISCANONICAL and DONOTDISTRIBUTE.

An opaque data type cannot have both the ISCANONICAL and DONOTDISTRIBUTE attributes.

不透明数据类型不能同时具有 ISCANONICAL 和 DONOTDISTRIBUTE 属性。

Modify your CREATE OPAQUE TYPE or ALTER OPAQUE TYPE statement to remove one of the modifiers.

修改 CREATE OPAQUE TYPE 或 ALTER OPAQUE TYPE 语句，删除其中一个修饰符。

-25722 Invalid combination of modifiers DONOTDISTRIBUTE and DISTRIBUTESREFERENCES.

An opaque data type cannot have both the DONOTDISTRIBUTE and DISTRIBUTESREFERENCES attributes.

不透明数据类型不能同时具有 DONOTDISTRIBUTE 和 DISTRIBUTESREFERENCES 属性。

Modify your CREATE OPAQUE TYPE or ALTER OPAQUE TYPE statement to remove one of the modifiers.

修改 CREATE OPAQUE TYPE 或 ALTER OPAQUE TYPE 语句，删除其中一个修饰符。

-25723 A modifier may not appear more than once in an ALTER statement.

An ALTER OPAQUE TYPE statement includes a repeated mention of a modifier such as DONOTDISTRIBUTE or ISCANONICAL.

ALTER OPAQUE TYP E语句包括重复的 DONOTDISTRIBUTE 或 ISCANONICAL 的修饰符。

Examine your statement and remove the repeated modifier.

检查您的语句并删除重复的修饰符。

-25724 May not modify built-in type<data_type_name>.

Only user-defined data types are valid with the ALTER OPAQUE TYPE statement.

The data type <data_type_name> is a built-in data type.

只有用户定义的数据类型对 ALTER OPAQUE TYPE 语句有效。

数据类型 <data_type_name> 是内置数据类型。

Remove the ALTER OPAQUE TYPE statement.

删除 ALTER OPAQUE TYPE 句。

-25725 Attempt to add duplicate modifier.

The opaque data type in your ALTER OPAQUE TYPE statement already includes the modifier .

ALTER OPAQUE TYPE 语句中的 opaque 数据类型已包含修饰符。

Remove from the ALTER OPAQUE TYPE statement.

删除 ALTER OPAQUE TYPE 语句中的。

-25726 Attempt to drop non-existent modifier /The modifier that you supplied in the DROP clause of ALTER OPAQUE TYPE is not a modifier for that opaque type. You cannot drop a modifier that is not present.

您在 ALTER OFORCOXT 类型的 DROP 子句中提供的修饰符不是该不透明类型的修饰符。

不能删除不存在的修饰符。

Correct your ALTER OPAQUE TYPE statement. To find the modifiers that are associated with the opaque type, use the following statement:请更正您的 ALTER OCROXYPE 语句。若要查找与不透明类型关联的修饰符，请使用以下语句：SELECT * from sysxtdtypes WHERE name =<opaque_type_name>.

-25727 Modifier is incompatible with SRVSENDRECV/DBSENDRECV cast.

You cannot create a srvsendrecv or dbsendrecv cast for an opaque type defined with the modifier .

您不能为使用修饰符定义的 opaque类型创建 srvsendrecv 或 dbsendrecv 强制转换。

Remove from the definition of the data type or drop the cast.

从数据类型的定义中删除或删除强制转换。

-25728 Type <data_type_name> is not the same in the local and remote database.

The attributes of the user-defined data type <data_type_name> are different on the local and remote databases. A UDT used in a distributed query must have the same attributes in all databases accessed by the query.

用户定义数据类型的属性 <data_type_name> 在本地和远程数据库上是不同的。分布式查询中使用的 UDT 必须在查询访问的所有数据库中具有相同的属性。

Examine the definition of the <data_type_name> UDT in both your local and remote databases. Modify one or both of the UDTs so that they are the same.

检查在本地和远程数据库中定义的 <data_type_name> UDT。修改一个或两个 UDT，使它们相同。

You can use the oncheck utility to check for compatible data types between servers. For example:您可以使用 oncheck 实用程序检查服务器之间的兼容数据类型。例如：oncheck -cvt db1@server1 db2@server2.

-25729 Type <opaque_type_name> may not be used in a distributed query(DONOTDISTRIBUTE).

The user-defined type <opaque_type_name> was created with the DONOTDISTRIBUTE modifier. UDTs with the DONOTDISTRIBUTE attribute cannot be used in queries that access more than one database.

用户定义的类型 <opaque_type_name> 是使用 ONOTDISTRIBUTE 修饰符创建的。不能在访问多个数据库的查询中使用具有 DONOTDISTRIBUTE 属性的 UDT 。

Modify the query or change the attributes of the <opaque_type_name> data type.

修改查询或更改 <opaque_type_name> 数据类型的属性。

-25731 Error Opening the Remote File <opaque_type_name>The database server could not open the requested remote file. Possible causes of the failure include:数据库服务器无法打开请求的远程文件。可能的失败原因包括：The file does not exist.

该文件不存在。

The permissions on the file do not permit this user to access the file.

文件的权限不允许此用户访问该文件。

The file specification is wrong.

文件规范错误。

Verify that the remote file exists, that its access permissions are set correctly, and that the syntax of the filename is correct. Remote files names must be specified with @.

验证远程文件是否存在，其访问权限是否设置正确，以及文件名的语法是否正确。

必须使用 @ 指定远程文件名。

-25733 Error Reading from the Remote File.

The database server could not read the requested remote file. Possible causes数据库服务器无法打开请求的远程文件。可能的失败原因包括：The file does not exist.

该文件不存在。

The permissions on the file do not permit this user to access the file.

文件的权限不允许此用户访问该文件。

The file specification is wrong.

文件规范错误。

Verify that the remote file exists, that its access permissions are set correctly, and that the syntax of the filename is correct. Remote files names must be specified with @.

验证远程文件是否存在，其访问权限是否设置正确，以及文件名的语法是否正确。

必须使用 @ 指定远程文件名。

-25736 The extended type <data_type_name> has not been defined in the local database.

The data type <data_type_name> does not have a definition on the local database. All extended data types that are used in distributed queries must be defined in both the local and remote databases.

数据类型 <data_type_name> 未在本地数据库上定义。

必须在本地和远程数据库中定义分布式查询中使用的所有扩展数据类型。

Make sure that <data_type_name> is defined in both the local and remote databases and that the definitions have the same attributes.

确保在本地和远程数据库中定义了 <data_type_name> ，并且定义具有相同的属性。

-25737 Cluster Indexes cannot be created in an online environment.

ONLINE keyword isn't supported for cluster indexes.

集群索引不支持 ONLINE 关键字。

-25738 Index can be created online only for btree secondary access method.

An index can be successfully created with the ONLINE keyword only if the secondary access method is btree.

仅当辅助访问方法为 btree 时，才能使用 ONLINE 关键字成功创建索引。

-25745 UUID already exists for .

You issued a CREATE UUID for a database server that already is associated with a UUID. That is, is included in the sysservers table of the syscdr database.

您为已经与 UUID 关联的数据库服务器发出了 CREATE UUID 。也就是说，包含在 syscdr 数据库的 sysserver 表中。

If the database server has a new UUID because it was reinitialized, use ALTER SERVERUUID to update the UUID in the sysservers table.

如果数据库服务器有一个新的 UUID，因为它已重新初始化，使用 ALTER SERVERUUID 更新 sysservers 表中的 UUID。

If the database server no longer exists, you can use DROP SERVERUUID to remove the entry from the sysservers table. It is not necessary to remove a nonexistent database server from sysservers. Leaving the entry in the sysservers table does not cause problems.

如果数据库服务器不再存在，可以使用 DROP SERVERUUID 从sysservers 表中删除条目。没有必要从 sysservers 中删除不存在的数据库服务器。

将条目保留在 sysservers 表中不会导致问题。

-25746 UUID does not exist for .

You cannot DROP SERVERUUID or ALTER SERVERUUID unless is associated with a UUID in the sysservers table of the syscdr database.

除非与 syscdr 数据库的 sysservers 表中的 UUID 关联，否则不能删除SERVERUID < 或更改 SERVERUUID 。

To find the names of database servers whose UUIDs exist, use the following query:若要查找存在 UUID 的数据库服务器的名称，请使用以下查询：SELECT * FROM syscdr:sysservers.

-25747 Do not have permissions to execute the drop serveruuid statement.

You must be a DBA to use to DROP SERVERUUID statement.

您必须是DBA才能使用 DROP SERVERUUID 语句。

-25751 Cannot cancel job on the host.

DataExtract cannot cancel the current SELECT clause that has been submitted to the host. For more information, see the accompanying API error message.

DataExtract 无法取消已提交给主机的 SELECT 子句。有关更多信息，请参阅随附的 API 错误消息。

-25753 Cannot write to local configuration file.

DataExtract cannot write to the local configuration file, openview.cfg.

The file is in the path that the ANSAPI environment variable specifies,or in the current directory if ANSAPI is not set. Either the file or path does not have the correct permissions, or not enough disk space is available. Verify that the file and path have the correct permissions and that sufficient disk space is available.

DataExtract 无法写入本地配置文件 openview.cfg。该文件位于 ANSAPI 环境变量指定的路径中，如果未设置 ANSAPI，则位于当前目录中。文件或路径没有正确的权限，或者没有足够可用的磁盘空间。验证文件和路径是否具有正确的权限以及是否有足够的可用磁盘空间。

-25755 Cannot read host configuration file.

DataExtract cannot read the host configuration file, config.txt. The file is in the path that the ANSAPI environment variable specifies, or in the current directory if ANSAPI is not set. Verify that the file and path have the correct permissions.

DataExtract 无法读取主机配置文件 config.txt。该文件位于 ANSAPI 环境变量指定的路径中，如果未设置 ANSAPI，则位于当前目录中。验证文件和路径是否具有正确的权限。

-25756 Cannot read local configuration file.

DataExtract cannot read the local configuration file, openview.cfg. The file is in the path that the ANSAPI environment variable specifies, or in the current directory if ANSAPI is not set. Verify that the file and path have the correct permissions.

DataExtract 无法读取主机配置文件 openview.cfg。该文件位于 ANSAPI 环境变量指定的路径中。如果未设置 ANSAPI，则位于当前目录中。验证文件和路径是否具有正确的权限。

-25757 Glossary database not open.

DataExtract cannot open the glossary database. Either DataExtract encountered an internal error, or the system permissions to the glossary database have been modified. Check the glossary database to make sure that the system permissions to the database have not been altered. If the problem persists, ask the glossary database owner to drop the glossary database and run the glossary Refresh option to re-create it.

DataExtract 无法打开 glossary 数据库。DataExtract 遇到内部错误，或者已修改glossary 数据库的系统权限。检查 glossary 数据库，确保未更改数据库的系统权限。

如果问题仍然存在，请要求 glossary 数据库所有者删除 glossary 数据库并运行glossary 刷新”选项重新创造它。

-25761 Host Environment parameter is invalid.

The value that you entered in the Host Environment parameter on the SETUP screen is not valid or is not supported. Change the value to one of the following: CICS, CMS, IMS, TSO.

您在 SETUP 屏幕上的 Host Environment 参数中输入的值无效或不受支持。

请将值更改为以下之一：CICS、CMS、IMS、TSO。

-25762 CICS Paging Code parameter is required.

A paging code is required if you are using Answer/Extractor in CICS.

Consult your Answer/Extractor DBA to find out the CICS paging code.

如果在 CICS 中使用 Answer/Extractor，则需要分页代码。

请咨询您的 Answer/Extractor DBA ，查找 CICS 分页代码。

-25763 CICS Termination Code parameter is required for the CICS host environment.

A termination code is required if you are using Answer/Extractor in CICS. Consult your Answer/Extractor DBA to find out the CICS termination code.

如果您在 CICS 中使用 Answer/Extractor，则需要终止代码。

请咨询您的 Answer/Extractor DBA ，查找 CICS 终止代码。

-25764 Answer/DB Profile Name parameter is required.

The Answer/Extractor profile name is required to determine your access permissions to the host tables. Consult your Answer/Extractor DBA to find out your Answer/Extractor profile name.

需要 Answer/Extractor 配置文件名称来确定您对主机表的访问权限。

请咨询您的Answer/Extractor DBA ，查找您的 Answer/Extractor 配置文件名称。

-25765 Answer/DB invocation code is required.

The Answer/Extractor invocation code is required to invoke Answer/Extractor. Consult your Answer/Extractor DBA to find out the Answer/Extractor invocation code for your host environment.

需要 Answer/Extractor 调用代码来调用 Answer/Extractor。

请咨询您的 Answer/Extractor DBA，了解您的主机环境 Answer/ Extractor 调用代码。

-25766 Lock Time parameter must be from 1 to 300 seconds.

The lock time that you entered is invalid. Change the lock time to a number from 1 to 300.

输入的锁定时间无效。将锁定时间更改为 1 到 300 之间的数字。

-25767 Stable Time parameter must be from 2 to 18 seconds.

The stable time that you entered is invalid. Change the stable time to a number from 2 to 18.

输入的稳定时间无效。将稳定时间更改为 2 到 18 之间的数字。

-25768 Connect Script parameter is required.

The Connect Script parameter on the SETUP screen is blank. Enter the filename of a valid connect script. You can use the Scripter utility to create a valid connect script if it does not exist.

SETUP 屏幕上的 Connect Script 参数为空。输入有效连接脚本的文件名。

如果 Scripter 实用程序不存在，可以使用 Scripter 实用程序创建有效的连接脚本。

-25769 Cannot access the specified connect script file.

The specified connect script file does not exist or does not have the correct permissions. Check the spelling of the filename. Check that the file exists in the path that the ANSAPI environment variable specifies,or in the current directory if ANSAPI is not set.

指定的连接脚本文件不存在或没有正确的权限。检查文件名的拼写。检查文件是否存在于ANSAPI 环境变量指定的路径中。或者，如果未设置 ANSAPI，则检查当前目录中的文件。

-25770 Disconnect Script parameter is required.

The Disconnect Script parameter on the SETUP screen is blank. Enter the filename of a valid disconnect script. Use the Scripter utility to create a valid script if it does not exist.

SETUP 屏幕上的 Disconnect Script 参数为空白。请输入有效的断开连接脚本的文件名。

如果 Scripter 实用程序不存在，请使用它创建有效的脚本。

-25771 Cannot access the specified disconnect script file.

The specified disconnect script file does not exist or does not have the correct permissions. Check the spelling of the filename. Check that the file exists in the path that the ANSAPI environment variable specifies, or in the current directory if ANSAPI is not set.

指定的断开连接脚本文件不存在或没有正确的权限。检查文件名的拼写。检查文件是否存在于ANSAPI 环境变量指定的路径中。如果未设置 ANSAPI，则检查当前目录中的文件。

-25772 Class parameter must be from 1 to 15.

The specified Answer/Extractor processing class is incorrect. Change the Class parameter to a number from 1 to 15.

指定的 Answer/Extractor 处理类不正确。将 Class 参数更改为从 1 到 15 的数字。

-25773 The Host Process Timeout parameter must be from 1 to 1440 minutes.

The specified processing timeout limit is incorrect. Change the Host Process Timeout parameter to a number from 1 to 1,440.

指定的处理超时限制不正确。将主机进程超时参数从 1 更改为 1440。

-25774 Max Records to Process parameter must be from 1 to 99,999,999.

The specified value is incorrect. Change the value to within the accepted range.

指定的值不正确。将值更改为可接受范围内的值。

-25775 Max Records to Retrieve parameter must be from 0 to 9,999.

The specified value is incorrect. Change the value to within the accepted range.

指定的值不正确。将值更改为可接受范围内的值。

-25776 Commit Frequency parameter must be from 1 to 99,999,999 rows.

The specified value is incorrect. Change the value to within the accepted range.

指定的值不正确。将值更改为可接受范围内的值。

-25777 Invalid value. Must be either Y or N.

You answered a prompt with a letter other than Y or N. Change your answer to Y or N.

您使用 Y 或 N 以外的字母回答了提示。将答案更改为 Y 或 N。

-25778 Error writing to output file.

While DataExtract is extracting host data into a file, it cannot write to the specified file. Verify that enough disk space is available and that the file has the correct permissions.

当 DataExtract 将主机数据提取到文件中时，它无法写入指定的文件。验证是否有足够的可用磁盘空间以及该文件是否具有正确的权限。

-25779 Cannot open output file.

While extracting host data into a file, DataExtract cannot open the specified output file. If the file already exists, check that the file has the correct permissions.

在将主机数据提取到文件中时，DataExtract 无法打开指定的输出文件。

如果该文件已存在，请检查该文件是否具有正确的权限。

-25780 Warning: No field descriptions defined for the host table.

While DataExtract was refreshing your glossary, it found that no field descriptions are defined on the host computer for the host table that is being refreshed. This message is a warning only. Consult your Answer/Extractor DBA about adding field descriptions for the host table.

当 DataExtract 刷新词汇表时，它发现在主机上没有为正在刷新的主机表定义字段描述。

此消息仅为警告。有关添加主机表的字段说明，请咨询您的 Answer/Extractor DBA。

-25781 Missing host table name or FROM clause.

The current EXTRACT statement is missing the host-table name or the entire FROM clause. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句缺少主机表名称或整个 FROM 子句。更正并重新运行 EXTRACT 语句。

-25782 Warning: Incomplete results have been returned from the host.

The data that you selected probably exceeded the disk space that is available to you on the host. The results that were retrieved from the host are incomplete. Take one or more of the following actions:您选择的数据可能超出了主机上可用的磁盘空间。从主机检索的结果不完整。

执行以下一个或多个操作：* Modify your SELECT clause to select less data or fewer fields.

修改 SELECT 子句，选择较少的数据或较少的字段。

* Consult your host Systems Administrator for more disk space.

请咨询主机系统管理员以获取更多磁盘空间。

* Modify your SIZE clause to retrieve fewer rows.

修改您的 SIZE 子句以检索更少的行。

* Modify the Max Records to Retrieve parameter on the SETUP screen.

修改 SETUP 屏幕上的 Max Records to Retrieve 参数。

-25783 Value in SIZE clause is invalid.

SIZE clause contains unacceptable characters. An acceptable value must be a number from 1 to 9,999.

SIZE 子句包含不可接受的字符。可接受的值必须是 1 到 9,999 之间的数字。

-25784 Value in SIZE clause is out of range.

The specified value is incorrect. An acceptable value must be a number from 1 to 9,999.

指定的值不正确。可接受的值必须是 1 到 9,999 之间的数字。

-25785 Cannot create external routine (%s) without the EXTEND role.

You cannot create an external function or a procedure without the privileges of the EXTEND role.

没有 EXTEND 角色的权限，您无法创建外部函数或过程。

-25786 Only DBSA can grant/revoke permissions for the EXTEND role.

Only members of the DBSA group can grant or revoke permissions for the EXTEND role.

只有 DBSA 组的成员才能授予或撤消 EXTEND 角色的权限。

-25787 Drop EXTEND role while converting to 10.00.

You need to drop the role while converting to 10.00 and then try the conversion again.

您需要在转换为 10.0 0时删除该角色，然后再次尝试转换。

-25788 Cannot unload or reload module without the EXTEND role.

You cannot unload or reload an external function or a procedure without the privileges of the EXTEND role.

如果没有 EXTEND 角色的权限，就不能卸载或重新加载外部函数或过程。

-25789 The file name in SET EXPLAIN FILE or SET DEBUG FILE must be a non-null string.

The argument specified for the file name in the SET EXPLAIN FILE or SET DEBUG FILE statement must be a non-null character data type (CHAR or VARCHAR).

在 SET EXPLAIN FILE 或 SET DEBUG FILE 语句中为文件名指定的参数必须是非空字符数据类型（CHAR 或 VARCHAR）。

-25790 File name in SET EXPLAIN FILE or SET DEBUG FILE statement is too long.

The file name provided in the SET EXPLAIN FILE or SET DEBUG FILE statement is longer than maximum allowed length of 256 bytes. Rename the file or store it in a directory with a shorter path.

SET EXPLAIN FILE 或 SET DEBUG FILE 语句中提供的文件名长度超过 256 字节的最大允许长度。

重命名文件或将其存储在路径较短的目录中。

-25791 Cannot execute privileged built-in Java routine without the EXTEND role or DBSA authority.

For security reasons, only a DBSA or users who have been granted the EXTEND role, if the IFX_EXTEND_ROLE configuration parameter is enabled, can execute the following built-in Java routines:install_jar, remove_jar, replace_jar, install_jar_deploy, remove_jar_undeploy,alter_java_path, setUDTExtName, and unsetUDTExtName出于安全原因，只有 DBSA 或已被授予 EXTEND 角色的用户（如果启用了 IFX_EXTEND_ROLE 配置参数）可以执行以下内置 Java 例程：install_jar、remove_jar、replace_jar、install_jar_deploy、remove_jar_undeploy alter_java_path、setUDTExtName 和 unsetUDTExtName。

-25800 Cannot specify overlapping fragment expressions for interval or list fragmentation.

The fragment expressions for interval or list fragmentation cannot overlap.

For example, the following statement generates an error:间隔或列表分片的分片表达式不能重叠。例如，以下语句生成错误：CREATE TABLE address (street VARCHAR(128), city VARCHAR(32),state CHAR(2), zip INT)FRAGMENT BY RANGE(zip)INTERVAL(1000) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< 5000 IN dbs3,PARTITION p2 VALUES< 10000 IN dbs3,PARTITION p3 VALUES< 10000 IN dbs4;The partition p2 and p3 are overlapping. The fragment expressions for p2 and p3 are the same.

分区 p2 和 p3 是重叠的。分区 p2 和 p3 的分片表达式同样。

The following statement also generates an error:以下语句仍生成错误：CREATE INDEX add_state_idx ON address(state)FRAGMENT BY LIST(state)PARTITION p1 VALUES ('CA','OR') IN dbs1,PARTITION p2 VALUES ('NY', 'NJ', 'CA') IN dbs2,PARTITION p3 VALUES (NULL) IN dbs3,PARTITION p4 REMAINDER IN dbs3;The partition p1 and p2 are overlapping. The value 'CA' appears in both p1 and p2 partitions.

分区 p1 和 p2 重叠。值 'CA' 出现在 p1 和 p2 分区中。

-25801 Cannot specify a dbspace more than once in the STORE IN clause.

A dbspace cannot be specified more than once in the STORE IN clause. For example, the following statement generates an error:在STORE IN子句中不能多次指定 dbspace。例如，以下语句生成错误：CREATE TABLE address (street VARCHAR(128), city VARCHAR(32),state CHAR(2), zip INT)FRAGMENT BY RANGE(zip)INTERVAL(1000) STORE IN (dbs1, dbs2, dbs1)PARTITION p1 VALUES< 5000 IN dbs3,PARTITION p2 VALUES< 10000 IN dbs3,PARTITION p3 VALUES< 20000 IN dbs4;The dbspace dbs1 appears twice in the STORE IN clause.

dbspace dbs1在 STORE IN 子句中出现两次。

-25802 The PARTITION clause is mandatory for interval and list fragmentation.

The PARTITION clause is mandatory for interval and list fragmentation.

A partition name must be specified following the PARTITION keyword. For example, the following statement generates an error:对于间隔和列表分片，PARTITION 子句是强制性的。必须在 PARTITION 关键字之后指定分区名称。

例如，以下语句生成错误：CREATE INDEX add_zip_idx ON address(zip)FRAGMENT BY RANGE(zip)INTERVAL(1000) STORE IN (dbs1, dbs2, dbs3)VALUES< 10000 IN dbs3;The following statement is correct:以下语句正确：CREATE INDEX add_zip_idx ON address(zip)FRAGMENT BY RANGE(zip)INTERVAL(1000) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< 10000 IN dbs3;-25803 Interval or list fragmentation must have at least one non-null, non-remainder fragment.

At least one fragment that is not a null fragment and is also not a remainder fragment must be specified for interval or list fragmentation definitions. A "null fragment" is a fragment that can only store NULL data values, A "remainder fragment" is a fragment defined with the REMAINDER keyword.

必须为区间或列表分片定义指定至少一个不是空分片且也不是剩余分片的分片。

“空分片”是只能存储空数据值的分片，“剩余分片”是用 REMAINDER 关键字定义的分片。

The following statements generate an error:以下语句生成错误：CREATE TABLE address (street VARCHAR(128), city VARCHAR(32),state CHAR(2), zip INT)FRAGMENT BY RANGE(zip)INTERVAL(1000) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES IS NULL IN dbs3;CREATE INDEX add_state_idx ON address(state)FRAGMENT BY LIST(state)PARTITION p1 VALUES (NULL) IN dbs2,PARTITION p2 REMAINDER IN dbs3;The above statements violates the interval and list fragmentation requirement that at least one fragment be neither a null nor a remainder fragment.

上面的语句违反了间隔和列表分片的要求，即至少有一个分片既不是 NULL 也不是剩余分片。

The following statements are correct:以下语句是正确的：CREATE TABLE address (street VARCHAR(128), city VARCHAR(32),state CHAR(2), zip INT)FRAGMENT BY RANGE(zip)INTERVAL(1000) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< 10000 IN dbs3;CREATE INDEX add_state_idx ON address(state)FRAGMENT BY LIST(state)PARTITION p1 VALUES ('CA','OR') IN dbs1,PARTITION p3 VALUES (NULL) IN dbs2,PARTITION p4 REMAINDER IN dbs3;CREATE INDEX add_zip_idx ON address(zip)FRAGMENT BY RANGE(zip)INTERVAL(1000) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< 10000 IN dbs3,PARTITION p2 VALUES IS NULL IN dbs4;In the statements abvoe, the p1 fragment is a non-null, non-remainder fragment, thereby satisfying the requirement for interval and list fragmentation.

在上面的语句中，p1 分片是一个非空的、非剩余的分片，从而满足了间隔和列表分片的要求。

-25804 The interval value must be a non-zero positive constant.

The resultant value of the expression for the interval value must be a non-zero positive constant. For example, the following statement generates an error:区间值表达式的结果值必须是一个非零的正常量.例如，以下语句生成错误：CREATE TABLE address (street VARCHAR(128), city VARCHAR(32),state CHAR(2), zip INT)FRAGMENT BY RANGE(zip)INTERVAL(-1000) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< 10000 IN dbs3;The interval value is negative.

间隔值是负数。

The following statement also generates an error:以下语句也生成错误：CREATE TABLE address (street VARCHAR(128), city VARCHAR(32),state CHAR(2), zip INT)FRAGMENT BY RANGE(zip)INTERVAL(zip) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< 10000 IN dbs3;The interval value is the column zip, which is not a constant.

Interval 值是列 zip，它不是常量。

-25805 The interval value must be a numeric or INTERVAL data type.

The resultant data type of the expression for an interval value must satisfy one of these two sets of conditions:INTERVAL 值的表达式的结果数据类型必须满足以下两组条件之一：<1> If the fragment key is a numeric type, the expression must return a built-in numeric data type. This cannot be a MONEY data type,and it cannot have a fractional part.

如果分片键是数字类型，则表达式必须返回内置数值数据类型。不能是 MONEY 数据类型，也不能包含小数部分。

<2> If the fragment key is a DATE or DATETIME type, the expression must return an INTERVAL data type whose last field qualifier cannot be a FRACTION.

如果分片键是 DATE 或 DATETIME 类型，则表达式必须返回 INTERVAL 数据类型，其最后一个字段限定符不能是 FRACTION。

INTERVAL 值“123”既不是数值数据类型也不是 INTERVAL 数据类型。

CREATE INDEX add_zip_idx ON address(zip)FRAGMENT BY RANGE(zip)INTERVAL(1000.20) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< 10000 IN dbs3;The interval value 1000.20 has a fractional part.

INTERVAL 值 1000.20 具有小数部分。

The following statement is correct:以下语句是正确的：CREATE INDEX add_zip_idx ON address(zip)FRAGMENT BY RANGE(zip)INTERVAL(100+900) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< 10000 IN dbs3;The interval value (100+900)is an expression whose result is numeric without a fractional part.

INTERVAL 值(100+900) 是一个表达式，其结果是数字而没有小数部分。

-25806 The fragment key for interval fragmentation must be a numeric, DATE, or DATETIME type.

The fragment key, which is the column expression on which the table or index is fragmented, must be a numeric, DATE, or DATETIME type. For example, the following statement generates an error:分片键，即表或索引在其上分段的列表达式，必须是数字、DATE 或 DATETIME 类型。

例如，以下语句生成错误：CREATE TABLE address (street VARCHAR(128), city VARCHAR(32),state CHAR(2), zip INT)FRAGMENT BY RANGE(city)INTERVAL(5) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< 10000 IN dbs3;The fragment key is the column city, which is of type CHAR.

分片建是列 city，其类型为 CHAR。

The following statements are correct:以下语句正确：CREATE TABLE orders (order_num INT, order_date DATE, customer_num INT,ship_instruct_code CHAR(1))FRAGMENT BY RANGE(order_date)INTERVAL(INTERVAL(3) MONTH TO MONTH) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< DATE('01/01/2009') IN dbs1;CREATE INDEX ord_ship_idx ON orders(ship_instruct_code)FRAGMENT BY RANGE(ASCII(ship_instruct_code))INTERVAL(10) STORE IN (dbs1, dbs2)PARTITION p1 VALUES< 65 IN dbs1;-25807 The fragment key for interval fragmentation must be a single column expression.

The fragment key, which is the column expression on which the table or index is fragmented, must be a single column expression. For example, the following statement generates an error:分片键，即表或索引在其上分片的列表达式，必须是单个列表达式。

例如，下面的语句产生一个错误：CREATE TABLE employee (emp_id INTEGER, emp_name CHAR(64), ssn CHAR(12),basepay FLOAT, varpay FLOAT, dept_id SMALLINT)FRAGMENT BY RANGE(ROUND(basepay+varpay))INTERVAL(2000) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< 0 IN dbs3;The fragment key references two columns, basepay and varpay, which is not allowed.

分片建引用了两列 basepay 和 varpay，这是不允许的。

-25808 The expression defining the upper limit of each fragment must be a constant.

The fragment expression for interval fragmentation is of the form VALUES <upper_limit_expr>. The expression for the upper limit must be a constant. For example, the following statement generates an error:间隔分片的分片表达式的形式为 VALUES <upper_limit_expr>。表达式的上限必须是常量。

例如，下面的语句产生一个错误：CREATE TABLE employee (emp_id INTEGER, emp_name CHAR(64), ssn CHAR(12),basepay FLOAT, varpay FLOAT, dept_id SMALLINT)FRAGMENT BY RANGE(emp_id)INTERVAL(2000) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< emp_id+1 IN dbs3;The upper limit of fragment p1 is a column expression, emp_id+1, which is not a constant.

分片 p1 的上限是列表达式 emp_id+1，它不是一个常量。

-25809 One or more dbspaces specified in the STORE IN clause does not exist.

One or more dbspaces specified in the STORE IN clause does not exist. Ensure that the dbspaces specified in the STORE IN clause exist and are of the same pagesize. If the table has an initial set of range fragments, the pagesize of the dbspaces in the STORE IN clause must match the pagesize of the dbspaces for the range fragments.

STORE IN 子句中指定的一个或多个 dbspace 不存在。确保 STORE IN 子句中指定的 dbspace存在并且具有相同的 pagesize。如果表具有一组初始范围片段，则 STORE IN 子句中 dbspace的 pagesize 必须与范围分片的 dbspace 的 pagesize 相匹配。

-25810 The fragment key, interval value, and upper limit of the fragments are not compatible.

The fragment key (the column expression on which the table or index is fragmented), the interval value, and the upper limit of fragments are not compatible data types. For a numeric fragment key, the interval value must be a numeric type and the upper limit of a fragment must be numeric. For a fragment key of DATE or DATETIME type, the interval value must be an INTERVAL type and the upper limit of a fragment must be a DATE or DATETIME type.

分片键（表或索引被分段的列表达式），间隔值和分片的上限不是兼容的数据类型。对于数值分片键，间隔值必须是数字类型，分片的上限必须是数字。对于 DATE 或 DATETIME 类型的分片键，间隔值必须是INTERVAL 类型，并且分片的上限必须是 DATE 或 DATETIME 类型。

The error can also occur in each of the following scenarios:在以下场景中也会发生此错误：- For a fragment key of DATETIME type, the first field qualifier of the fragment key is greater than the last field qualifier of the interval value.

对于 DATETIME 类型的分片键，分片键的第一个字段限定符大于间隔值的最后一个字段限定符。

For a fragment key of DATE type, the interval value is not an integer multiple of days (i.e the hours, minutes, seconds or fractions are nonzero).

对于 DATE 类型的分片键，间隔值不是天的整数倍（即小时、分钟、秒或分数非零）。

For a fragment key of DATE or DATETIME type, the first field qualifier of the fragment key and the first field qualifier of the upper limit of a fragment are not the same.

对于 DATE 或 DATETIME 类型的分片键，分片键的第一个字段限定符和分片上限的第一个字段限定符不同。

The resultant type of the upper limit of a fragment is not a built-in data type.

分片的上限的结果类型不是一个内置数据类型。

For example, the following statements generate an error:例如，以下语句生成错误：Example 1:示例 1：CREATE TABLE employee (emp_id INTEGER, emp_name CHAR(64), ssn CHAR(12),basepay FLOAT, varpay FLOAT, dept_id SMALLINT)FRAGMENT BY RANGE(emp_id)INTERVAL(3 UNITS YEAR) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< 3000 IN dbs3;The fragment key and the upper limit of fragment p1 are numeric, but the interval value is of the incompatible INTERVAL type.

分片键和分片 p1 的上限是数字，但间隔值是不兼容的 INTERVAL 类型。

Example 2:示例 2：CREATE TABLE orders (order_num INT, order_time DATETIME HOUR TO SECOND,customer_num INT, ship_instruct_code CHAR(1))FRAGMENT BY RANGE(order_time)INTERVAL(3 UNITS DAY)PARTITION p1 VALUES< DATETIME(01:00:00) HOUR TO SECOND IN dbs1;In the above example the first field qualifier (HOUR) of the fragment key order_time is greater than the last field qualifier (DAY) of the interval value.

在上面的示例中，分片键 order_time 的第一个字段限定符（HOUR）大于间隔值的最后一个字段限定符（DAY）。

The correct usage is as follows:正确的用法如下：CREATE TABLE orders (order_num INT, order_time DATETIME HOUR TO SECOND,customer_num INT, ship_instruct_code CHAR(1))FRAGMENT BY RANGE(order_time)INTERVAL(3 UNITS HOUR)PARTITION p1 VALUES< DATETIME(01:00:00) HOUR TO SECOND IN dbs1;Example 3:示例 3：CREATE TABLE orders (order_num INT, order_time DATETIME YEAR TO SECOND,customer_num INT, ship_instruct_code CHAR(1))FRAGMENT BY RANGE(order_time)INTERVAL(3 UNITS DAY)PARTITION p1 VALUES< DATETIME(01-01 01:00:00) MONTH TO SECOND IN dbs1;In the above example, the first field qualifier (YEAR) of the fragment key order_time is not same as the first field qualifier (MONTH) of the upper limit of the initial range fragment.

在上面的例子中，分片键 order_time 的第一个字段限定符（YEAR）与初始范围片段的上限的第一个字段限定符（MONTH）不同。

The correct usage is as follows:正确用法如下：CREATE TABLE orders (order_num INT, order_time DATETIME YEAR TO SECOND,customer_num INT, ship_instruct_code CHAR(1))FRAGMENT BY RANGE(order_time)INTERVAL(3 UNITS DAY)PARTITION p1 VALUES< DATETIME(2010-01-01 01:00:00) YEAR TO SECOND IN dbs1;Example 4:示例 4：CREATE TABLE orders (order_num INT, order_date DATE,customer_num INT, ship_instruct_code CHAR(1))FRAGMENT BY RANGE(order_date)INTERVAL(3 UNITS HOUR)PARTITION p1 VALUES< DATE('01/01/2009') IN dbs1;In the above example the fragment key order_date is of type DATE but the interval value (3 UNITS HOUR) is not an integer multiple of DAY.

在上面的示例中，分片键 order_date 的类型为 DATE，但间隔值（3 UNITS HOUR）不是 DAY 的整数倍。

The correct usage is as follows:正确的用法是：CREATE TABLE orders (order_num INT, order_date DATE,customer_num INT, ship_instruct_code CHAR(1))FRAGMENT BY RANGE(order_date)INTERVAL(24 UNITS HOUR)PARTITION p1 VALUES< DATE('01/01/2009') IN dbs1;-25811 The transition value for interval fragments must be aligned to the boundary of the interval value type.

The transition value, or the upper limit of the last range fragment, must be aligned to the boundary of the interval value type.

转换值或最后一个范围分片的上限必须与间隔值类型的边界对齐。

The following requirements apply:适用以下要求：- For an interval value of any numeric data type, the transition value cannot have a fractional part.

对于对于数字数据类型的间隔值，转换值不能有小数部分。

For an interval value of INTERVAL type whose first field qualifier is YEAR or MONTH, the transition value cannot not contain field qualifiers smaller than MONTH. Unless the DAY field has a value of 01 and the values of any time units smaller than DAY are zero (for example,01 00:00:00.00000).

对于第一个字段限定符为年份或月份的 INTERVAL 类型的间隔值，转换值不能包含小于月份的字段限定符。除非日期字段的值为01，且任何时间单位小于日的值为零(例如，01 00：00：00.00000)。

For an interval value of INTERVAL type whose first field qualifier is DAY or a smaller time unit, the transition value cannot have FRACTION as the last field qualifier, unless the FRACTION field has a value of zero.

对于第一个字段限定符为 DAY 或较小的时间单位的 INTERVAL 类型的 INTERVAL 值，转换值不能将分数作为最后一个字段限定符，除非分数字段的值为零。

For example, the following statements generate an error:例如，以下语句生成错误：Example 1:示例 1:CREATE TABLE employee (emp_id INTEGER, emp_name CHAR(64), ssn CHAR(12),basepay FLOAT, varpay FLOAT, dept_id SMALLINT,hire_date DATE)FRAGMENT BY RANGE(basepay)INTERVAL(1000) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< 40000.50 IN dbs1,PARTITION p2 VALUES< 60000.50 IN dbs2,PARTITION p3 VALUES< 80000.50 IN dbs3;In the above example the upper limit of first and intermediate range fragments can be of any numeric type, but the upper limit of the last range fragments (which is the transition value for interval fragments)must be an INTEGER. The transition value in the above example, 80000.50,has a fractional part.

在上面的例子中，第一和中间范围分片的上限可以是任何数字类型，但是最后一个范围分片的上限（它是间隔分片的转换值）必须是 INTEGER。上例中的转换值 80000.50 具有小数部分。

The correct usage is as follows:正确用法如下：CREATE TABLE employee (emp_id INTEGER, emp_name CHAR(64), ssn CHAR(12),basepay FLOAT, varpay FLOAT, dept_id SMALLINT,hire_date DATE)FRAGMENT BY RANGE(basepay)INTERVAL(1000) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< 40000.50 IN dbs1,PARTITION p2 VALUES< 60000.50 IN dbs2,PARTITION p3 VALUES< 80001 IN dbs3;Example 2:示例 2：CREATE TABLE employee (emp_id INTEGER, emp_name CHAR(64), ssn CHAR(12),basepay FLOAT, varpay FLOAT, dept_id SMALLINT,hire_date DATE)FRAGMENT BY RANGE(hire_date)INTERVAL(3 UNITS YEAR) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< DATE('03/25/2006') IN dbs3;In the above example the interval value is specified in units of YEAR, but the transition value is not aligned to the year or month boundary.

在上面的示例中，间隔值以年份的单位指定，但转换值与年份或月份的边界不对齐。

The correct usage is as follows:正确的用法如下：CREATE TABLE employee (emp_id INTEGER, emp_name CHAR(64), ssn CHAR(12),basepay FLOAT, varpay FLOAT, dept_id SMALLINT,hire_date DATE)FRAGMENT BY RANGE(hire_date)INTERVAL(3 UNITS YEAR) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< DATE('03/01/2006') IN dbs3;Example 3:示例 3：CREATE TABLE orders (order_num INT, order_time DATETIME YEAR TO SECOND,customer_num INT, ship_instruct_code CHAR(1))FRAGMENT BY RANGE(order_time)INTERVAL(INTERVAL(10 12) DAY(2) TO HOUR)PARTITION p1 VALUES< DATETIME(2010-03-25 01:00:00.123) YEAR TO FRACTION(3) IN dbs1;In the above example the interval value is a DAY(2) TO HOUR interval.

The INTERVAL field qualifier transition value is not aligned to the second boundary (because it contains a nonzero FRACTION value).

在上面的例子中，间隔值是 DAY(2) TO HOUR INTERVAL。INTERVAL 字段限定符转换值未与第二边界对齐(因为它包含一个非零 FRACTION 值)。

The correct usage is as follows:正确的用法如下：CREATE TABLE orders (order_num INT, order_time DATETIME YEAR TO SECOND,customer_num INT, ship_instruct_code CHAR(1))FRAGMENT BY RANGE(order_time)INTERVAL(INTERVAL(10 12) DAY(2) TO HOUR)PARTITION p1 VALUES< DATETIME(2010-03-25 01:00:00.000) YEAR TO FRACTION(3) IN dbs1;-25812 The difference between the old and new transition values must be a multiple of the interval value.

If altering the fragmentation scheme changes the transition value, and the table or index has interval fragments, then the difference between the old and new transition values must be a multiple of the interval value.

如果更改分片策略会改变转换值，而表或索引有间隔分片，则新旧转换值之间的差值必须是间隔值的倍数。

For example, consider a table with following schema:例如，创建以下表：CREATE TABLE employee (emp_id INTEGER, emp_name CHAR(64), ssn CHAR(12),basepay FLOAT, varpay FLOAT, dept_id SMALLINT,hire_date DATE)FRAGMENT BY RANGE(emp_id)INTERVAL(3000) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< 4000 IN dbs1,PARTITION p2 VALUES< 6000 IN dbs2,PARTITION p3 VALUES< 8000 IN dbs3;If the above table has interval fragments (added automatically when emp_id values 8000 or greater were inserted), then modifying the transition value to 8500 will not be allowed.

如果表具有间隔分片（当插入的 emp_id 值大于等于 8000 时自动添加)，则不允许将转换值修改为 8500。

The following statement generates an error:以下语句生成错误：ALTER FRAGMENT ON TABLE employee MODIFY INTERVAL TRANSITION TO 8500;The difference between the new transition value, 8500, and the old transition value, 8000, is not a multiple of the interval value, 3000.

新转换值 850 0与旧转换值 8000 之间的差值不是间隔值 3000 的倍数。

Similarly, dropping or detaching the transition fragment or the last range fragment changes the transition value. The gap created by the drop or detach must be a multiple of the interval value.

类似地，删除或拆离转换分片或最后一个范围分片会更改转换值。由 drop 或 detach 创建的间隙必须是间隔值的倍数。

The following statement generates an error:以下语句生成错误：ALTER FRAGMENT ON TABLE employee DROP PARTITION p3;The difference between the new transition value, 6000, and the old transition value, 8000, or the gap created by the drop is not a multiple of the interval value, 3000.

新转换值 6000 与旧转换值 8000 之间的差值或由 DROP 创建的间隔不是间隔值 3000 的倍数。

-25813 The partition name used in the fragmentation scheme is not allowed.

The system-generated partition names for interval fragments start with 'sys_p'.

Therefore, the partition names for initial fragments of an interval fragmented table or index cannot have names that start with the same characters.

系统生成的间隔分片的分区名称以 'sys_p' 开头。因此，间隔分片表或索引的初始分片的分区名称不能有以相同字符开头的名称。

The following statement generates an error:以下语句生成错误：CREATE TABLE employee (emp_id INTEGER, emp_name CHAR(64), ssn CHAR(12),basepay FLOAT, varpay FLOAT, dept_id SMALLINT,hire_date DATE)FRAGMENT BY RANGE(hire_date)INTERVAL(3 UNITS YEAR) STORE IN (dbs1, dbs2, dbs3)PARTITION sys_p1 VALUES< DATE('01/01/2006') IN dbs3;In the above example the partition name starts with 'sys_p', which is not allowed, because the 'sys_p' prefix is reserved for system-defined storage objects.

在上面的示例中，分区名以‘sys_p’开头，这是不允许的，因为‘sys_p’前缀是为系统定义的存储对象保留的。

An incorrect argument has been passed to one of these functions NUMTOYMINTERVAL(), NUMTODSINTERVAL, TO_YMINTERVAL(), TO_DSINTERVAL().

向以下其中一个函数 NUMTOYMINTERVAL()、NUMTODSINTERVAL、TO_YMINTERVAL()、TO_DSINTERVAL() 传递了一个错误的参数。

The formats of these functions are:这些函数的格式为：NUMTOYMINTERVAL(, { "YEAR" | "MONTH" } )TO_YMINTERVAL(, { "YEAR" | "MONTH" } )NUMTODSINTERVAL(, { "DAY" | "HOUR" | "MINUTE" | "SECOND" } )TO_DSINTERVAL(, { "DAY" | "HOUR" | "MINUTE" | "SECOND" } )The variable can be any literal number, or it can be a column with a data type that resolves to a number.

变量可以是任何文字数值，也可以是具有解析为数字的数据类型的列。

The following examples show how to use these functions correctly:以下示例显示如何正确使用这些函数：execute function NUMTOYMINTERVAL(1.5,"YEAR");execute function NUMTODSINTERVAL(120,"MINUTE");Alternatively, you can pass a single string argument to TO_YMINTERVAL(),and TO_DSINTERVAL():或者，可以向 TO_YMINTERVAL() 和 TO_DSINTERVAL() 传递一个字符串参数：TO_YMINTERVAL("YY-mm")TO_DSINTERVAL("DD HH:MM:SS")Where:其中：YY = years mm = months DD = days HH = hours MM = minutes SS = seconds The following examples show how to use a string argument with these functions:以下示例显示如何在这些函数中使用字符串参数：execute function TO_YMINTERVAL("15-6");execute function TO_DSINTERVAL("1 3:3:7");-25815 The expression defining the list of values for a fragment in list fragmentation must be a constant.

The expression defining the list of values for a fragment in list fragmentation must be a constant. For example, the following statement generates an error:定义列表分片中分片的值列表的表达式必须是常量。例如，下面的语句产生错误：CREATE TABLE customer (cust_id INTEGER, cust_name CHAR(20), state CHAR(2))FRAGMENT BY LIST (state)PARTITION p0 VALUES ("KS", "IL") IN dbs0,PARTITION p1 VALUES (name, "NR") IN dbs2;One of the values in the list for fragment p1 is a column, which is not a constant.

分片 p1 列表中有一个值是列，它不是常量。

-25816 The dbspace does not exist in list of dbspaces for interval fragments.

The specified dbspaces does not exist in list of dbspaces for interval fragments of the given table table or index. The following query will give the current list of dbspaces for interval fragments for a table and its indexes:指定的 dbspace 不存在于给定表或索引的间隔分片的 dbspace 列表中。

以下查询将给出表及其索引的间隔分片的当前 dbspace 列表：SELECT t.tabname, f.indexname, f.exprtext FROM sysfragments f, systables t WHERE f.tabid = t.tabid AND f.evalpos = -1 AND t.tabname =;-25817 Cannot drop or detach the only remaining non-null, non-remainder fragment.

The fragmentation scheme cannot be altered to drop or detach the last non-null, non-remainder fragment. Interval or list fragmentation must have at least one non-null, non-remainder fragment.

分片方案不能更改为删除或拆离最后一个非空的非剩余分片。

间隔或列表分片必须至少有一个非空的非剩余片段。

-25818 The specified operation or syntax is not supported.

The specified operation or syntax is not supported with the fragmentation scheme of the table or index.

表或索引的分片方案不支持指定的操作或语法。

-25819 The INTERVAL clause is allowed with interval fragmentation scheme only.

The INTERVAL clause can be specified only while altering the fragmentation scheme of an interval fragmented table/index or altering the fragmentation scheme to interval fragmentation.

只有在更改间隔分片表/索引的分片方案或将分片方案更改为间隔分片时，才能指定 INTERVAL 子句。

-25820 Cannot attach two non-fragmented tables to create an interval or list fragmented table.

For interval and list fragmentation, the surviving table in attach operation must be fragmented by interval or list. If you want to attach two non-fragmented tables, initialize the framentation scheme for one of the non-fragmented tables to interval or list and then attach the second one to it.

对于间隔和列表分片，附加操作中的幸存表必须按间隔或列表进行分片。如果要附加两个非分片表，请将其中一个非分片表的分片方案初始化为 interval 或 list，然后将第二个附加到其中。

-25821 Internal error: The interval or list fragmented table/index has zero fragments.

An internal error occurred while reading the catalog entries for an interval or list fragmented table/index. The table/index does not have any fragments.

If this error recurs, note all circumstances and contact GBase Technical Support.

读取间隔或列表分片表/索引的项时发生内部错误。表/索引没有任何分片。如果再次出现此错误，请注意所有情况并联系 GBase 技术支持。

-25822 Unable to determine fragment position for fragments while moving to new fragmentation scheme.

An error occurred while determining fragment position for fragments in new fragmentation scheme. The fragment position for one of the fragments in the new scheme could have exceeded 2147483646. Consider changing the interval value expression or transition value.

在新分片方案中确定分片的分片位置时发生错误。新方案中其中一个分片的分片位置可能已超过2147483646。考虑更改间隔值表达式或转换值。

-25823 Cannot specify BEFORE or AFTER clause while adding or attaching a fragment.

The BEFORE or AFTER clause cannot be used while adding or attaching a fragment to an interval fragmented table/index. The system internally determines the position of the fragment that is being added ot attached.

在将分片添加或附加到间隔分片表/索引时，不能使用 BEFORE 或 AFTER 子句。

系统内部确定添加到附加的片段的位置。

-25824 The upper limit of the fragment must be aligned to an interval fragment boundary.

While altering the interval fragmentation scheme to add or attach fragments above the transition value, the upper limit of the fragment being added or attached must align at an interval fragment boundary i.e. the upper limit of the fragment must equal transition value plus a multiple of the interval value.

在改变间隔分片方案以在过渡值之上添加或附加分片时，正在添加或附加的分片的上限必须在区间分片边界对齐，即分片的上限必须等于过渡值加上间隔值的倍数。

For example, the following alter generates an error:例如，以下更改会产生一个错误：CREATE TABLE employee (emp_id INTEGER, emp_name CHAR(64), ssn CHAR(12),basepay FLOAT, varpay FLOAT, dept_id SMALLINT,hire_date DATE)FRAGMENT BY RANGE(emp_id)INTERVAL(1000) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< 5000 IN dbs0,PARTITION p2 VALUES< 10000 IN dbs0;ALTER FRAGMENT ON TABLE employee ADD PARTITION p3 VALUES< 15400;In the above example, a fragment is being added above the transition value i.e. an interval fragment is being added. The upper limit of the fragment,15400, is not aligned to an interval fragment boundary.

在上面的例子中，于转换值之上添加了一个分片，即添加一个间隔分片。

分片的上限 15400 未与间隔分片边界对齐。

The correct usage is as follows:正确的用法为：ALTER FRAGMENT ON TABLE employee ADD PARTITION p3 VALUES< 16000;-25825 Cannot specify remainder fragment for interval fragmentation.

Interval fragmentated tabl or index cannot have remainder fragment.

Rewrite the statement to remove the remainder fragment specification.

区间分片的 tabl 或索引不能有剩余分片。重写语句以删除剩余分片规范。

-25826 Cannot specify more than one null fragment for interval or list fragmentation.

Interval or list fragmentated table or index cannot have more than one null fragment. Rewrite the statement to remove the null fragment specification.

间隔或列表分片表或索引不能有多个空分片。重写该语句以删除空分片规范。

-25827 Cannot add or attach a fragment expressions that matches an exisitng fragment expression.

Interval or list fragmentated table or index cannot have overlapping fragment expressions.

间隔或列表分片表或索引不能具有重叠的分片表达式。

-25828 An error occurred while adding or attaching a fragment to the initial range fragments.

An internal error occurred while adding or attaching a fragment to the initial fragments of an interval fragmented table or index. Note all circumstances and contact GBase Technical Support.

将分片添加或附加到间隔分片表或索引的初始分片时发生内部错误。

请注意所有情况并联系 GBase 技术支持。

-25829 Cannot modify the fragment expression for an interval fragment.

The fragment expression for an interval fragment is system generated and cannot be modified.

间隔分片的分片表达式是系统生成的，不能修改。

-25830 The new fragment expression cannot cross adjacent fragment boundaries.

While altering the fragmentation scheme to modify the fragment expression of range fragments, the new fragment expression cannot cross adjacent fragment boundaries. The new upper limit of the range fragment must be greater than the upper limit of the previous range fragment and lesser than that of the next range fragment.

在改变分片方案以修改范围分片的分片表达时，新分片表达式不能跨越相邻分片边界。

范围分片的新上限必须大于前一个范围片段的上限，并且小于下一个范围片段的上限。

For example, the following alters generate error:例如，以下更改会产生错误：CREATE TABLE employee (emp_id INTEGER, emp_name CHAR(64), ssn CHAR(12),basepay FLOAT, varpay FLOAT, dept_id SMALLINT,hire_date DATE)FRAGMENT BY RANGE(emp_id)INTERVAL(1000) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< 5000 IN dbs0,PARTITION p2 VALUES< 10000 IN dbs0,PARTITION p3 VALUES< 20000 IN dbs4,PARTITION p4 VALUES< 25000 IN dbs4;ALTER FRAGMENT ON TABLE employee MODIFY PARTITION p2 TO PARTITION p2 VALUES< 4000 IN dbs0;ALTER FRAGMENT ON TABLE address MODIFY PARTITION p2 TO PARTITION p2 VALUES< 21000 IN dbs0;The new fragment expression in both of the above alters crosses adjacent fragment boundries. The new upper limit 4000 of the first alter is lesser than the upper limit of previous range fragment p1. Similarly, the new upper limit 21000 of the second alter is greater than that of the next range fragment p3. The new upper limit for range fragment p2 must be greater than 5000 and lesser than 20000.

上述两种修改中的新分片表达与相邻的分片边界相交。第一个修改的新上限 4000 小于先前范围分片 p1 的上限。类似地，第二修改的新上限 21000 大于下一范围分片 p3 的新上限 21000。范围分片 p2 的新上限必须大于 5000 且小于 20000。

The correct usage is as follows:正确的用法如下：ALTER FRAGMENT ON TABLE address MODIFY PARTITION p2 TO PARTITION p2 VALUES< 12000 IN dbs0;-25831 Cannot modify fragment expression for transition fragment.

The fragment expression for transition fragment or last range fragment cannot be modified. However, the MODIFY INTERVAL TRANSITION option of the ALTER FRAGMENT statement allows modification of the transition value which in turn can change the fragment expression.

不能修改过渡分片或最后范围分片的分片表达式。但是，ALTER FECTION 语句的 MODIFY间隔转换选项允许修改转换值，这反过来可以更改分片表达式。

For example, the following alter generates an error:例如，下面的 ALTER 生成一个错误：CREATE TABLE employee (emp_id INTEGER, emp_name CHAR(64), ssn CHAR(12),basepay FLOAT, varpay FLOAT, dept_id SMALLINT,hire_date DATE)FRAGMENT BY RANGE(emp_id)INTERVAL(1000) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< 5000 IN dbs0,PARTITION p2 VALUES< 10000 IN dbs0,PARTITION p3 VALUES< 20000 IN dbs4;ALTER FRAGMENT ON TABLE employee MODIFY PARTITION p3 TO PARTITION p3 VALUES< 25000 IN dbs4;The fragment expression for transition fragment p3 cannot be modified using the above syntax.

不能使用上面的语法修改转换分片 p3 的分片表达式。

The following statement that modifies the transition value, will indirectly change the fragment expression for p3:以下语句修改了转换值，它将之间更改 p3 的分片表达式：ALTER FRAGMENT ON TABLE employee MODIFY INTERVAL TRANSITION TO 25000;-25832 Internal error: Could not modify the transition value.

An internal error occurred while modifying the transition value. If this error recurs, note all circumstances and contact GBase Technical Support.

修改转换值时发生内部错误。如果再次出现此错误，请注意所有情况，并与 GBase 技术支持部门联系。

-25833 Internal error: The compact representation of fragment partitioning could not be constructed.

An internal error occured while constructing the compact representation of fragment partitioning for interval or list fragmented table/index.

The fragment expressions either overlap or are non-linear.

在为间隔或列表分片表/索引构造分片分区的缩写表示时，发生了内部错误。

分片表达要么重叠，要么是非线性的。

-25834 The specified alter fragment operation cannot be performed online.

Online alter fragment is supported only with interval fragmented tables.

只有间隔分片表支持联机更改分片。

The following operations can be performed online:- attaching interval fragment- detaching interval fragment- modifying transition value可以在线执行以下操作：- 附加间隔分段- 拆离间隔分片- 修改转换值The following conditions apply for attaching an interval fragment online:以下条件适用于在线附加间隔分片：- The surviving table has to be an interval fragmented table.

幸存的表必须是间隔分片表。

The consumed table has to be non-fragmented. Only one table can be attached at a time.

消耗表必须是非分片的。一次只能附加一个表。

All indexes on the surviving table has to be fragmented same as table i.e. all indexes must be attached.

幸存表上的所有索引必须与表一样分片，即必须附加所有索引。

For each index on the surviving table, there must be a matching index on the consumed table i.e. index on the same set of columns.

对于幸存表上的每个索引，消耗表上必须有匹配的索引，即同一列列上的索引。

The indexes on the consumed table must be detached and stored in a single dbspace. The dbspace for the index must be same as the dbspace for the consumed table.

必须分离消耗表上的索引并将其存储在单个 dbspace 中。索引的 dbspace 必须与使用的表的 dbspace 相同。

If the index on the surviving table is unique, the corresponding matching index on the consumed table must be unique.

如果幸存表上的索引是唯一的，则消耗表上的相应匹配索引必须是唯一的。

The consumed table must have a check constraint that exactly matches the fragment expression being attached and must span a single interval only. This is necessary to ensure no data movement.

所使用的表必须具有与所附加的分片表达式完全匹配的 CHECK 约束，并且必须仅跨越单个间隔。这对于确保没有数据移动是必要的。

The following conditions apply for detaching an interval fragment online:以下条件适用于在线分离间隔分片：- The surviving table has to be an interval fragmented table.

幸存的表必须是间隔分片表。

All indexes on the surviving table has to be fragmented same as table i.e. all indexes must be attached.

幸存表上的所有索引必须与表一样分片，即必须附加所有索引。

-25835 The transition value specified is not valid.

While altering the fragmentation scheme to modify the transition value,the new transition value must be greater than old transition value.

If there are interval fragments following the new transition value then the new transition value must align at an interval fragment boundary.

在更改分片方案以修改转换值时，新转换值必须大于旧转换值。

如果在新的转换值之后存在间隔分片，则新的转换值必须在间隔分片边界处对齐。

For example, consider a table with following schema:例如，考虑具有以下模式的表：CREATE TABLE employee (emp_id INTEGER, emp_name CHAR(64), ssn CHAR(12),basepay FLOAT, varpay FLOAT, dept_id SMALLINT,hire_date DATE)FRAGMENT BY RANGE(emp_id)INTERVAL(1000) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< 4000 IN dbs1,PARTITION p2 VALUES< 6000 IN dbs2,PARTITION p3 VALUES< 8000 IN dbs3;The following statement generates an error:以下语句产生一个错误：ALTER FRAGMENT ON TABLE employee MODIFY INTERVAL TRANSITION TO 7000;The transition value can only be increased. In the above example, the new transition value is lesser than the old one.

转换值只能增加。在上面的示例中，新转换值小于旧转换值。

Lets assume the table has two interval fragments,假定表具有两个间隔分片，sys_p4 >= 8000 AND< 9000 sys_p6 >= 10000 AND< 11000 The following statement generates an error:以下语句产生错误：ALTER FRAGMENT ON TABLE employee MODIFY INTERVAL TRANSITION TO 8500;The new transition value 8500 is not aligned at an interval fragment boundary.

新的转换值 8500 没有与间隔分片的边界对齐。

The following usage is correct:下列用法正确：ALTER FRAGMENT ON TABLE address MODIFY INTERVAL TRANSITION TO 9000;ALTER FRAGMENT ON TABLE address MODIFY INTERVAL TRANSITION TO 10000;The new transition values 9000 and 10000 are aligned at an interval fragment boundary.

新的转换值 9000 和 10000 在间隔分片边界对齐。

The following usage is also correct:以下用法也是正确的：ALTER FRAGMENT ON TABLE address MODIFY INTERVAL TRANSITION TO 12500;Since there are no interval fragments beyond the new transition value, the new transition value need not align at an interval fragment boundary.

由于在新的转换值之外没有间隔分片，所以新的转换值不需要在区间分片边界对齐。

-25836 The transition value must be a non-null constant.

The transition value must be a non-null constant expression.

For example, the following alter generates an error:转换值必须是非空常量表达式.例如，下面的 ALTERT 生成一个错误：CREATE TABLE employee (emp_id INTEGER, emp_name CHAR(64), ssn CHAR(12),basepay FLOAT, varpay FLOAT, dept_id SMALLINT,hire_date DATE)FRAGMENT BY RANGE(emp_id)INTERVAL(1000) STORE IN (dbs1, dbs2, dbs3)PARTITION p1 VALUES< 5000 IN dbs0,PARTITION p2 VALUES< 10000 IN dbs0,PARTITION p3 VALUES< 20000 IN dbs4;ALTER FRAGMENT ON TABLE employee MODIFY INTERVAL TRANSITION TO emp_id+10;The new tranisition value, emp_id+10 is a column expression and not a constant.

新转换值 emp_id+10 是列表达式，不是常量。

-25837 Cannot truncate an index fragment.

An index fragment cannot be truncated. The TRUNCATE option of the ALTER FRAGMENT statement is supported only with table fragments.

不能截断索引分片。只有表分片支持 ALTER FRAGMENT 语句的 TRUNCATE 选项。

-25838 Duplicate partition name in the list of fragments for truncation.

A partition name was specified more than once in the TRUNCATE clause of the ALTER FRAGMENT statement.

在 ALTER FRAGMENT 语句的 TRUNCATE 子句中多次指定了分区名称。

For example, the following statements generate an error:例如，以下语句生成错误：ALTER FRAGMENT ON TABLE employee TRUNCATE PARTITION p1, PARTITION p1,PARTITION p2;The partition p1 appears twice in the TRUNCATE clause.

分区 p1 在 TRUNCATE 子句中出现了两次。

-25839 Internal error: Could not find the transition fragment.

The transition fragment is missing. If this internal error recurs,note all circumstances and contact GBase Technical Support.

转换分片丢失。如果此内部错误再次发生，请注意所有情况，并与 GBase 技术支持部门联系。

-25840 An error occurred during online attach of fragment.

An error occurred during online attach of fragment. Check the accompanying ISAM error code for more information.

联机附加分片过程中发生错误。检查附带的 ISAM 错误代码以获取更多信息。

-25841 An error occurred during online detach of fragment.

An error occurred during online detach of fragment. Check the accompanying ISAM error code for more information.

联机附加分片过程中发生错误。检查附带的 ISAM 错误代码以获取更多信息。

-25842 An online alter fragment operation cannot be performed in a transaction that has modified objects in a database.

The online alter fragment operation must be the first operation in the transaction that does any kind of modification.

联机 alter fragment 操作必须是事务中进行任何修改的第一个操作。

-25843 An online alter fragment operation cannot be performed in a transaction that has explicitly locked the table that is being altered.

A LOCK TABLE statement was issued in the current transaction to lock the table that is being altered. An online alter fragment operation cannot be performed in a transaction that has explicitly locked the table. If you need to lock the table, perform the alter fragment operation offline.

在当前事务中发出了 LOCK TABLE 语句，锁定正在更改的表。无法在已明确锁定表的事务中执行联机 alter fragment 操作。如果需要锁定表，请脱机执行 alter fragment 操作。

-25844 Cannot create an interval fragmented temporary table or index.

Interval fragmentation is not supported with temporary tables and indexes.

临时表和索引不支持间隔分片。

-25845 An online operation is already in progress on this table.

The following online operations are possible on a table:- online create index- online drop index- online alter fragment可以在桌面上进行以下在线操作：- 在线创建索引- 在线删除索引- 在线更改分片Only one of the above online operations can be performed on a table at a time.

Wait until the first online operation is complete before reissuing another online command.

一次只能在一个表上执行上述在线操作中的一个。等到第一个在线操作完成后再重新发出另一个在线命令。

-25846 Cannot alter the fragmentation scheme online if replication is defined on the table.

The fragmentation scheme cannot be altered online if replication is defined on the table. Reissue the statement without the ONLINE keyword.

如果在表上定义了复制，则无法在线更改碎片方案。重新发出不带 ONLINE 关键字的语句。

-25847 The fragments of the table or index have changed.

The fragments of the table or index have changed before an exclusive lock could be obtained on the table. Either an interval fragment was added during some DML activity or an ALTER FRAGMENT ONLINE operation just completed.

This condition is normally transient, retry operation after some delay.

表上可以获得独占锁之前，表或索引的分片已更改。在某些 DML 活动期间添加了间隔分片或刚刚完成ALTER FRAGMENT ONLINE 操作中添加了间隔分片。这种情况通常是暂时的，延迟后再重试操作。

-25848 The functional key argument is invalid.

The error occurred due to one or more of the following reasons:由于以下一个或多个原因导致错误：The first argument to functional index needs to table column.

函数索引的第一个参数需要表列。

If other arguments are constant, it needs to be string type of length less than 128 bytes.

如果其他参数是常量，则它必须是长度小于 128 个字节的字符串类型。

-25849 The indexkey size exceeds the catalog column size.

The error occurred due to encoded indexkey size excceds the szie of sysindcies.indexkey column. If you used functional index with constants reduce the size of the constant.

由于编码的 indexkey 大小导致 sysindcies.indexkey 列的 szie 错误。

如果使用带常量的函数索引，则减小常量的大小。

-25850 The window-frame extent specification requires a window-order clause.

Any window-frame extent specification also requires the window-order clause,unless the window frame is between UNBOUNDED PRECEDING and UNBOUNDED FOLLOWING.

除非窗口框架在 UNBOUNDED PRECEDING 和 UNBOUNDED FOLLOWING 之间，否则任何窗口框架范围规范需要 window-order 子句。

-25851 The window-frame extent value specification are not correct.

If RANGE is specified, then the window-order clause in the window definition must contain a single sort key. The declared data type of the sort key can be numeric, DATETIME, or INTERVAL. The data type of the constant value in FOLLOWING or PRECEDING specifications must be a numeric if the sort key has a numeric data type.

Otherwise, it must be an INTERVAL type that can be added to or subtracted from values of the declared type of the ORDER BY sort key.

如果指定了 RANGE，则窗口定义中的 window-order 子句必须包含单个排序键。排序键的声明数据类型可以是 numeric、DATETIME 或 INTERVAL。如果排序键具有数字数据类型，则 FOLLOWING 或 PRECEDING 规范中的常量值的数据类型必须是数字。否则，它必须是 INTERVAL 类型，可以从 ORDER BY 排序键添加或从已声明的顺序类型的值中减去。

If ROWS is specified, then the declared type of the must be an exact numeric data type with a scale of 0 (zero), such as INTEGER.

如果指定了 ROWS，则的声明类型必须是小数位为 0（零）的精确数字数据类型，例如 INTEGER。

-25852 The window-frame extent BETWEEN options are not valid.

The specified BETWEEN options that define the window-frame extent are not valid.

定义窗口框架范围的 BETWEEN 选项无效。

Use BETWEEN specifications that conform to the documented window-frame extent syntax in your GBase 8s Guide to SQL:Syntax. This is a subset of the BETWEEN syntax for OLAP windowed aggregates that the Cognos product supports.

使用符合《GBase 8s SQL指南：语法》中记录的窗口框架范围语法的 BETWEEN 规范。这是 Cognos产品支持的 OLAP 窗口聚合的 BETWEEN 语法的子集。

-25853 The ntile, lead, lag and ranking window functions require window order.

The aggregate RANK(), DENSE_RANK(), DENSERANK(), PERCENT_RANK(), LAG(), LEAD(),CUME_DIST(), and NTILE() window functions require the window-order clause.

RANK()、DENSE_RANK()、 DENSERANK()、PERCENT_RANK()、LAG()、LEAD()、CUME_DIST()和 NTILE() 聚合窗口函数需要 window-order 子句。

-25854 The ntile, lead, lag, ranking and row numbering window functions cannot have a window-frame extent.

The ROWNUMBER(), ROW_NUMBER(), RANK(), DENSE_RANK(), DENSERANK(), LAG(), LEAD(),PERCENT_RANK(), CUME_DIST(), NTILE() window functions cannot be called if a window-frame extent is also defined for the window.

如果为窗口定义了窗口范围，则无法调用 ROWNUMBER()、ROW_NUMBER()、RANK()、DENSE_RANK()、DENSERANK()、LAG()、LEAD()、PERCENT_RANK()、CUME_DIST()、NTILE() 窗口函数。

-25855 The option specified is not supported in window aggregates.

The following options are not supported in OLAP window aggregates, including aggregates in the PARTITION BY, ORDER BY, and window-frame extent clauses:OLAP 窗口聚合函数中不支持以下选项，包括 PARTITION BY、ORDER BY 和 window-frame extent子句中的聚合：Window aggregates with user-defined aggregates具有用户定义聚合的窗口聚集函数Correlated subqueries相关子查询Collection subqeries集合子查询Complex data types复杂的数据类型CURRVAL or NEXTVAL expressions for sequence objects.

序列对象的 CURRVAL 或 NEXTVAL 表达式。

-25856 Invalid usage of window aggregate in this context.

You can use OLAP window aggregate functions in the Projection clause and in the ORDER BY clause of queries. They cannot be present in the WHERE clause or in the HAVING clause (except within a subquery).

您可以在 Projection 子句和查询的 ORDER BY 子句中使用 OLAP 窗口聚合函数。

它们不能出现在 WHERE 子句或 HAVING 子句中（子查询中除外）。

-25857 Invalid usage of DISTINCT aggregate in this context.

DISTINCT is only allowed for the following OLAP aggregate functions:SUM(), AVG(), COUNT(), MIN(), MAX(), RANGE(), VARIANCE(), STDEV()只有以下 OLAP 聚集函数才允许使用 DISTINCT ：SUM()、AVG()、COUNT()、MIN()、MAX()、RANGE()、VARIANCE()、STDEV()-25858 DISTINCT aggregate can not have ORDER BY clause or window frame extent.

When DISTINCT is specified in OLAP aggregate functions the window function cannot have ORDER BY clause or window frame extent.

在 OLAP 聚集函数中指定 DISTINCT 时，窗口函数不能具有 ORDER BY 子句或窗口框架范围。

-25859 The argument to NTILE window function is invalid.

The argument to NTILE window function needs to be positive non-zero numeric value.

NTILE 窗口函数的参数必须是正的非零数值。

-25860 The offset of the LEAD, LAG window function is invalid.

The argument of LEAD, LAG NTILE window function needs to be positive numeric type with scale 0(zero).

LEAD、LAG NTILE 窗口函数的参数必须是正数数字类型，其小数位为 0（零）。

-25861 The types of default expression and expression of LEAD, LAG are not compatible.

The default expression type shall be compaitble with LEAD, LAG window expression type.

缺省表达式类型应与 LEAD、LAG 窗口表达式类型兼容。

-25862 The argument to RATIO_TO_REPORT window function is invalid.

The argument to RATIO_TO_REPORT window function needs to be of numeric data type.

RATIO_TO_REPORT 窗口函数的参数必须是数值数据类型。

-25898 The total size of the index exceeds 32767 bytes.

The size of the composite index cannot exceed 32767 bytes. Consider reducing the number of index parts until this requirement is met.

复合索引的大小不能超过 32767 个字节。在满足此要求之前，请考虑减少索引部分的数量。

-25899 Same index already exists on given BSON columns.

This CREATE INDEX statement cannot be executed because an index on the given BSON columns with the same key parts already exists.

无法执行此 CREATE INDEX 语句，因为给定的 BSON 列上已经存在具有相同关键部分的索引。

-26000 Locks cannot be limited for a user who has administrative privileges.

You cannot set the IFX_SESSION_LIMIT_LOCKS option to the SET ENVIRONMENT statement for a user who has administrative privileges, such as user gbasedbt or a DBSA user.

Users with administrative privileges are always allowed to have the maximum allowed number of locks per session.

对于拥有管理权限的用户(如 Gbasedbt 用户或 DBSA 用户)，不能将IFX_SESSION_LIMIT_LOCKS 选项设置为 SET ENVIRONMENT 语句。具有管理权限的用户总是允许每个会话拥有允许的最大锁数。

-26001 The encryption/decryption password is not set.

Provide an encryption password in the argument list to the encryption/decryption functions or use the "SET ENCRYPTION PASSWORD"statement.

在参数列表中为加密/解密函数提供加密密码，或使用“SET ENCRYPTION PASSWORD”语句。

-26002 Invalid encryption password data type.

The encryption password is invalid because the specified password data type is not supported. Use a string type (such as CHAR(20) or VARCHAR(40)) for the encryption password.

加密密码无效，因为不支持指定的密码数据类型。使用字符串类型（例如 CHAR(20)或 VARCHAR(40)）作为加密密码。

-26003 The data must be encrypted with a password length between 6 and 128.

The encryption password is invalid because the length of the specified password was less than 6 bytes or greater than 128 bytes.

加密密码无效，因为指定密码的长度小于 6 个字节或大于 128 个字节。

-26004 The encryption hint data type is not supported.

Use a string type (such as CHAR(20) or VARCHAR(40)) for the encryption hint.

使用字符串类型（例如 CHAR(20) 或 VARCHAR(40)）作为加密提示。

-26005 The encrypted data is wrong or corrupted.

The data must be a result of an IDS encryption function. The decryption may have failed because the data was not encrypted, was corrupted, or truncated (e.g. ALTER TABLE operation) since encryption, or was encrypted with an algorithm not supported by this version.

数据必须是使用 IDS 加密函数的结果。解密可能已失败，因为数据未加密、数据已损坏或由于加密数据被截断（例如 ALTER TABLE 操作），或者使用了此版本不支持的算法加密。

-26006 The data type is not supported for encryption functions.

BYTE/TEXT and UDT are not supported. Use BLOB/CLOB instead of BYTE/TEXT,or cast a UDT to a string type such as CHAR or LVARCHAR.

不支持 BYTE/TEXT 和 UDT。使用 BLOB/CLOB 代替 BYTE/TEXT，或者将 UDT 转换为字符串类型，例如 CHAR 或 LVARCHAR。

-26007 The internal encryption function failed.

The internal crypto library encryption API failed.

内部 crypto 库加密 API 失败。

-26008 The internal decryption function failed.

The internal crypto library decryption API failed. This error may be caused by a wrong password or corrupted data.

内部 crypto 库加密 API 失败。错误原因可能是密码错误或数据毁坏。

-26009 Key generation failed.

The internal crypto library key generation API failed.

内部 crypto 库密钥生成 API 失败。

-26010 Random IV generation failed.

The internal crypto library random API failed to generate an initialization vector (IV).

内部 crypto 库随机 API 无法生成初始化向量（IV）。

-26011 The internal base64 encoding function failed.

The internal crypto library base64 encoding API failed.

内部 crypto 库 base64 编码 API 失败。

-26012 The internal base64 decoding function failed.

The internal crypto library base64 decoding API failed.

It may be caused by a corrupted data.

内部 crypto 库 base64 解码 API 失败。它可能是由损坏的数据引起的。

-26013 Encrypt VP mailbox operation failed.

An internal error occurred during communication between a CPU VP and an ENCRYPT VP.

CPU VP 和 ENCRYPT VP 通信期间发生了内部错误。

-26040 Encrypt VP initialization failed.

An internal error occurred during initialization of an ENCRYPT VP.

ENCRYPT VP 初始化期间发生了内部错误。

Contact the operating system administrator to make sure that the required version of GSKit is installed.

联系操作系统管理员，确保安装了所需版本的 GSKit。

-26100 You cannot set the GRANT ACCESS or REVOKE ACCESS properties when the USERMAPPING onconfig parameter is OFF The GRANT ACCESS and REVOKE ACCESS statements can only be used if the ONCONFIG parameter USERMAPPING is ON.

仅当 ONCONFIG 参数 USERMAPPING 为ON时，才能使用 GRANT ACCESS 和 REVOKE ACCESS 语句。

-26101 The specified group name (%s) does not exist.

The group name specified was not found in the operating system's group database. When you specify a surrogate group by name, the surrogate name must exist in in the operating system's group database (/etc/group file or equivalent).

在操作系统的组数据库中找不到指定的组名。按名称指定代理组时，代理名称必须在操作系统的组数据库（/etc/group 文件或等效文件）中存在。

ACTION Either ask the operating system administrator to add the group or change the statement to reference a group name that does exist.

请求操作系统管理员添加组或更改语句，引用确实存在的组名。

-26102 The specified user name (%s) does not exist.

The user name specified was not found in the operating system's user database.

When you specify the surrogate user by name, the surrogate name must exist in in the operating system's user database (/etc/passwd file or equivalent).

在操作系统的用户数据库中找不到指定的用户名。当您按名称指定代理用户时，代理名称必须存在于操作系统的用户数据库（/etc/passwd 文件或等效文件）中。

ACTION Either ask the operating system administrator to add the user or change the statement to reference a user name that does exist.

请求操作系统管理员添加用户或更改语句，引用确实存在的用户名。

-26103 You cannot modify existing access for user %s now. You must revoke access first then grant access.

The named user has already been granted access. To alter a user's access, you must first revoke their existing access rights with REVOKE ACCESS and then grant the new rights with GRANT ACCESS.

已指定的用户已被授予访问权限。要更改用户的访问权限，必须先使用 REVOKE ACCESS 撤消其现有访问权限，然后使用 GRANT ACCESS 授予新权限。

-26104 Reserved for future use.

This message is not currently used.

当前此消息已不再使用。

-26105 You should specify a group for the user.

You must specify at least one group for the mapped user using a group name or group number.

必须使用组名或组编号为映射的用户指定至少一个组。

-26106 You specified more than %d group names or numbers.

You specified more group names or group numbers than the system permits.

您指定的系统名称或组编号超出了系统允许的范围。

-26107 User name (%s) has already been granted access.

The named user has already been granted access. If you need to change their access, you must revoke access before granting the altered access.

命名的用户已被授予访问权限。如果需要更改其访问权限，则必须在授予更改的访问权限之前撤消访问权限。

-26108 You cannot grant root or gbasedbt user privilege to the user.

The GRANT ACCESS command listed either one of the user names root or gbasedbt,or the user numbers corresponding to those names. You cannot grant a mapped user the privileges of a surrogate user equivalent to either user root or gbasedbt.

GRANT ACCESS 命令列出了用户名 root 或 gbasedbt ，或者与这些名称对应的用户编号。

无法向映射用户授予与 root 或 gbasedbt 用户等效的代理用户的权限。

-26109 You cannot grant access to user gbasedbt or root.

The users gbasedbt and root cannot be treated as mapped users; they must both be regular unmapped users known to the operating system.

用户 Gbasedbt 和 root 用户不能被视为映射用户；它们都必须是操作系统已知的常规未映射用户。

-26110 The specified group has administrative privileges. You must either specify userauth properties or not include the group in the GRANT ACCESS statement.

One of the groups identified in the group clause is an administrative group(the DBSA, DBSSO, AAO group or bargroup) but the user was not identified as belonging to the group with the userauth properties clause. You cannot accidentally grant a user administrative privileges by listing the group name or group number; you must do so explicitly.

GROUP 子句中标识的组是管理组（DBSA、DBSSO、AAO组或 bargroup），但未将用户标识为属于具有userauth 属性子句的组。不能通过列出组名称或组编号来意外授予用户管理权限；必须明确地这样做。

-26111 The specified userauth (%s) property does not exist. The valid values-are dbsa, dbsso, dbaao or bargroup.

You specified an administrative property in the userauth clause that is not recognized. You may only use one of the values listed.

您在 userauth 子句中指定了一个无法识别的管理属性。只能使用所列的一个值。

-26112 The home directory is already specified.

The home directory was specified twice but may only be specified once.

主目录已指定两次，但只能指定一次。

-26113 The group name is already specified.

One of the group names or numbers specifies the same group as another group name or number. You may only list any group once, either by name or by number but not both.

其中一个组名称或组编号指定了与另一个组名称或编号相同的组。您只能按名称或编号列出任何一组，但不能同时列出两个组。

-26114 The userauth property is already specified.

The userauth property was specified twice but may only be specified once.

userauth 属性已指定两次，但只能指定一次。

-26104 API error: Out of memory.

This message indicates a memory-allocation error. Memory Manager could not allocate memory. Exit DataExtract and retry the option.

此消息表示内存分配错误。内存管理器无法分配内存。退出 DataExtract 并重试该选项。

-26201 API error: Cannot find message file.

The Answer/Extractor message file, message.txt, cannot be found. Check that the ANSAPI environment variable is set correctly. If necessary,copy the message file from $GBS_HOME/etc to your ANSAPI directory,or to the current directory if ANSAPI is not set.

无法找到 Answer/Extractor 消息文件 message.txt。检查 ANSAPI 环境变量是否设置正确。如有必要，将消息文件从 $GBS_HOME etc 复制到 ANSAPI 目录，如果未设置ANSAPI，则复制到当前目录。

-26202 API error: No room for message file.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26203 API error: Message file is too short.

The Answer/Extractor message file, message.txt, is incorrect or corrupt. Recopy the message file from $GBS_HOME/etc to the directory that the ANSAPI environment variable specifies, or to the current directory if ANSAPI is not set.

Answer/Extractor 消息文件 message.txt 不正确或已损坏。将消息文件从$GBS_HOME/etc 重新复制到 ANSAPI 环境变量指定的目录，如果未设置ANSAPI，则重新映射到当前目录。

-26204 API error: Message file is too long.

-26205 API error: Error reading message file.

The Answer/Extractor message file, message.txt, does not have the correct permissions or is corrupted. Verify that the file has the correct permissions. The file should be in the directory that the ANSAPI environment variable specifies, or in the current directory if ANSAPI is not set. If the file is corrupt, recopy the file from$GBS_HOME/etc.

Answer/Extractor 消息文件 message.txt 没有正确的权限或已损坏。验证该文件是否具有正确的权限。该文件应位于 ANSAPI 环境变量指定的目录中，如果未设置 ANSAPI，则应位于当前目录中。如果文件已损坏，请从 $GBS_HOME/etc 重新复制该文件。

-26206 API error: Cannot find configuration file.

The host configuration file, config.txt, cannot be found. Use the Setup option on the DataExtract Main Menu to access the SETUP screen and create the configuration file.

找不到主机配置文件 config.txt。使用 DataExtract 主菜单上的“设置”选项访问“SETUP”屏幕并创建配置文件。

-26207 API error: No room for configuration file.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26208 API error: Configuration file is too short.

The host configuration file, config.txt, is incorrect or corrupt. Use the Setup option on the DataExtract Main Menu to access the SETUP screen and re-create the configuration file.

主机配置文件 config.txt 不正确或已损坏。使用 DataExtract 主菜单上的“设置”选项访问“SETUP”屏幕并重新创建配置文件。

-26209 API error: Configuration file is too long.

The host configuration file, config.txt, is incorrect or corrupt. Use the Setup option on the DataExtract Main Menu to access the SETUP screen and re-create the configuration file.

主机配置文件 config.txt 不正确或已损坏。使用 DataExtract 主菜单上的“设置”选项访问“SETUP”屏幕并重新创建配置文件。

-26210 API error: Error reading configuration file.

The host configuration file, config.txt, does not have the correct permissions or is corrupt. Verify that the file has the correct permissions. Check that the file is in the directory that the ANSAPI environment variable specifies, or in the current directory if ANSAPI is not set. If the file is corrupt, use the Setup option on the DataExtract Main Menu to access the SETUP screen and re-create the configuration file.

主机配置文件 config.txt 没有正确的权限或已损坏。验证该文件是否具有正确的权限。

检查文件是否在 ANSAPI 环境变量指定的目录中，或者在当前目录中是否未设置 ANSAPI。

如果文件已损坏，请使用 DataExtract 主菜单上的“设置”选项访问“设置”屏幕并重新创建配置文件。

-26211 API error: Invalid SQLCA structure.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26212 API error: Communications board not present.

The hardware that is required for communicating to the host computer is not installed or is not functioning properly. Verify that the communications board is installed and configured properly.

与主机通信所需的硬件未安装或无法正常运行。验证是否已正确安装和配置通信板。

-26217 API error: Inconsistent driver scan code file.

The controller instructions file, driver.dsc, is invalid or corrupt.

Recopy the file from $GBS_HOME/etc to the directory that ANSAPI specifies or to the current directory if ANSAPI is not set.

控制器指令文件 driver.dsc 无效或已损坏。将文件从 $GBS_HOME/etc 重新复制到ANSAPI 指定的目录，如果未设置 ANSAPI，则重新复制到当前目录。

-26224 API error: Host session busy.

The emulation software is unavailable, or the host session that is specified in the Host Session parameter on the SETUP screen is currently in use.

仿真软件不可用，或者当前正在使用SETUP屏幕上的Host Session参数中指定的主机会话。

Verify that the emulation software is available. If it is, change the Host Session parameter on the SETUP screen to a different host session.

Change any configuration file that your emulation software requires accordingly.

验证仿真软件是否可用。如果是，请将 SETUP 屏幕上的 Host Session 参数更改为其他主机会话。更改仿真软件所需的任何配置文件。

-26225 API error: Host session does not exist.

The host-session name that is specified in the Host Session parameter on the SETUP screen is invalid. Correct the host-session name. Change any configuration file that your communications software requires accordingly.

在 SETUP 屏幕上的 Host Session 参数中指定的主机会话名称无效。更正主机会话名称。

更改通信软件相应所需的任何配置文件。

-26230 API error: Session cannot be set up as model 5 terminal.

DataExtract does not support model 5 terminals. Reconfigure your 3270 emulator software to a model 2 terminal and restart DataExtract.

DataExtract 不支持 5 型终端。将 3270 仿真器软件重新配置为模型 2 终端并重新启动DataExtract。

-26231 API error: Keyboard permanently locked.

The Keyboard Inhibit signal on the host session did not clear within the timeout period set in the Lock Time parameter. This situation might have occurred for the following reasons:主机会话上的键盘禁止信号在锁定时间参数中设置的超时时间内未清除。出现这种情况的原因如下：* The time that the Lock Time parameter specifies is too short.

锁定时间参数指定的时间太短。

* The host session went down.

主机会话失败。

* The host session is very slow.

主机会话很慢。

Exit DataExtract. Use your 3270 emulator software (for example, te3278)to verify that the host session is available. If the host session is available, manually exit the session to the starting point that your connect script specifies. Restart DataExtract. If the host session is very slow, increase the Lock Time parameter.

退出 DataExtract。使用 3270 仿真器软件（例如，te3278）验证主机会话是否可用。

如果主机会话可用，请手动将会话退出到连接脚本指定的起始点。重新启动 DataExtract。

如果主机会话非常慢，请增加“Lock Time”参数。

-26233 API error: Invalid character.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26234 API error: Invalid script.

The connect or disconnect script is invalid. Use the Scripter utility to re-create your connect or disconnect script. Check that the scripts are in the directory that the ANSAPI environment variable specifies.

连接或断开连接脚本无效。使用 Scripter 实用程序重新创建连接或断开连接脚本。

检查脚本是否位于 ANSAPI 环境变量指定的目录中。

-26235 API error: Invalid script password.

The password for the connect or disconnect script is incorrect. Verify your connect or disconnect script password on the SETUP screen.

连接或断开连接脚本的密码不正确。在 SETUP 屏幕上验证您的连接或断开连接脚本密码。

-26236 API error: Input beyond end of screen.

Your 3270 emulator session is not at the terminal session screen that the connect script expects. Exit DataExtract and confirm that your connect script is correct. Use the 3270 emulator software to make sure that it is at the screen that the connect script expects.

您的 3270 模拟器会话不在连接脚本所需的终端会话屏幕上。退出 DataExtract 并确认您的连接脚本是否正确。使用 3270 模拟器软件确保它位于连接脚本所需的屏幕上。

-26237 API error: Input too long for field.

Your 3270 emulator session is not at the terminal session screen that the connect script expects. Exit DataExtract and confirm that your connect script is correct. Use the 3270 emulator software to check that it is at the screen that the connect script expects.

您的 3270 模拟器会话不在连接脚本所需的终端会话屏幕上。退出 DataExtract 并确认您的连接脚本是否正确。使用 3270 模拟器软件确保它位于连接脚本所需的屏幕-26238 API error: Lock Time limit expired while waiting for host response.

The host did not respond within the time limit that is set in the Lock Time parameter in the SETUP screen. The host is either not available at the moment or is busy. Use the Setup option on the Main Menu to access the SETUP screen. If the error recurs, resubmit your request.

主机在 SETUP 屏幕的 Lock Time 参数中设置的时间限制内没有响应。主机暂时不可用或正忙。

使用主菜单上的“SETUP”选项访问“SETUP”屏幕。如果错误再次出现，请重新提交您的请求。

-26239 API error: Invalid Host Environment parameter.

The specified host environment is invalid. Correct the Host Environment parameter on the SETUP screen.

指定的主机环境无效。在 SETUP 屏幕上更正 Host Environment 参数。

-26240 API error: Invalid Answer/DB Password parameter.

The specified Answer/Extractor password is invalid. Verify the Answer/DB Password parameter on the SETUP screen.

指定的 Answer/Extractor 密码无效。

请验证 SETUP 屏幕上的 Answer/DB Password 参数。

-26241 API error: Invalid Answer/DB Profile Name parameter.

The specified Answer/Extractor profile name is invalid. Verify the Answer/DB Profile Name parameter on the SETUP screen.

指定的 Answer/Extractor 程序配置文件名称无效。

在 SETUP 屏幕上验证 Answer/DB Profile Name 参数。

-26242 API error: Unintelligible response.

Your 3270 emulator session is not at the terminal session that the connect script expects. Exit DataExtract and confirm that your connect script is correct. Use the 3270 emulator software to check that it is at the terminal that the connect script expects.

您的 3270 模拟器会话不是连接脚本所期望的终端会话。退出 DataExtract 并确认您的连接脚本是否正确。使用 3270 模拟器软件检查它是否位于连接脚本所期望的终端上。

-26245 API error: Answer/DB invocation failed.

-26246 API error: Cannot open script.

The connect or disconnect script cannot be opened. Verify that the connect or disconnect script file has the correct permissions.

无法打开连接或断开连接脚本。验证 connect 或 disconnect 脚本文件是否具有正确的权限。

-26247 API error: Invalid SQLEA structure.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26248 API error: SQLDA size below minimum.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26249 API error: SQLST size below minimum.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26250 API error: Invalid query name.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26251 API error: Invalid SQLDA structure.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26252 API error: Invalid SQLST structure.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26253 API error: SQLDA structure too small.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26254 API error: SQLST structure too small.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26255 API error: SQLDA does not contain field name.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26256 API error: SELECT not found.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26257 API error: FROM not found.

The SELECT clause in the current EXTRACT statement is missing the FROM clause. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句中的 SELECT 子句缺少 FROM 子句。更正并重新运行 EXTRACT 语句。

-26258 API error: Invalid SELECT reference.

The SELECT clause in the current EXTRACT statement is invalid. Correct the EXTRACT statement and rerun it.

当前 EXTRACT 语句中的 SELECT 子句无效。更正并重新运行 EXTRACT 语句。

-26259 API error: Invalid FROM reference.

The SELECT clause in the current EXTRACT statement has an invalid FROM reference. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句中的 SELECT 子句具有无效的 FROM 引用。更正并重新运行 EXTRACT 语句。

-26260 API error: Invalid range variable.

The SELECT clause in the current EXTRACT statement contains an invalid range variable. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句中的 SELECT 子句包含无效范围变量。更正并重新运行 EXTRACT 语句。

-26262 API error: Invalid comparison in WHERE clause.

The WHERE clause in the current EXTRACT statement contains an invalid comparison. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句中的 WHERE 子句包含无效比较。更正并重新运行EXTRACT语句。

-26263 API error: Invalid function reference.

The function that is referenced in the SELECT clause in the current EXTRACT statement is invalid. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句中 SELECT 子句中引用的函数无效。更正并重新运行 EXTRACT 语句。

-26265 API error: ORDER BY contains fields not selected.

Some of the fields that are specified in the ORDER BY clause in the EXTRACT statement have not been selected. Modify the SELECT clause to select the fields and rerun the EXTRACT statement.

在 EXTRACT 语句中的 ORDER BY 子句中指定的某些字段尚未被选中。

修改 SELECT 子句以选择字段并重新运行 EXTRACT 语句。

-26267 API error: Invalid wildcard.

The wildcard in the SELECT clause of the current EXTRACT statement is invalid. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句的 SELECT 子句中的通配符无效。更正并重新运行 EXTRACT 语句。

-26268 API error: Invalid substitution.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26269 API error: Unintelligible keyword.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26270 API error: Invalid predefined query.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26271 API error: Host connection not established.

The connection to Answer/Extractor on the host cannot be established at the moment. Exit DataExtract and resubmit the request.

目前无法建立与主机上的 Answer/Extractor 的连接。退出 DataExtract 并重新提交请求。

-26272 API error: Host connection not terminated.

The connection to Answer/Extractor on the host cannot be terminated.

The host session has probably been disconnected unexpectedly. Use the emulator software, for example te3278, to verify that the host connection is terminated. The session might need to be terminated manually.

无法终止与主机上的 Answer/Extractor 的连接。主机会话可能已意外断开连接。

使用模拟器软件（例如 te3278）验证主机连接是否已终止。可能需要手动终止会话。

-26273 API error: Invalid class number.

The value that is set in the Class parameter is invalid. Consult your Answer/Extractor DBA to determine the valid class numbers. Correct the class number on the SETUP screen and rerun the EXTRACT statement.

Class 参数中设置的值无效。请咨询您的 Answer/Extractor DBA 以确定有效的类编号。

在 SETUP 屏幕上更正类编号，然后重新运行 EXTRACT 语句。

-26274 API error: Invalid item count.

The value that is set in the Max Records to Process parameter is invalid. Correct the parameter on the SETUP screen and rerun the EXTRACT statement.

Max Records to Process 参数中设置的值无效。更正 SETUP 屏幕上的参数，然后重新运行 EXTRACT 语句。

-26275 API error: Invalid record count.

The value that is set in the Max Records to Retrieve parameter is invalid. Correct the parameter on the SETUP screen and rerun the EXTRACT statement.

Max Records to Retrieve 参数中设置的值无效。更正 SETUP 屏幕上的参数，然后重新运行 EXTRACT 语句。

-26276 API error: Invalid query in SQLST.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26277 API error: Table does not exist on the host.

The host table that the current EXTRACT statement specifies does not exist, although it is listed in your glossary. The host-table glossary is probably out of date. Refresh the entire host-table glossary.

当前 EXTRACT 语句指定的主机表不存在，尽管它是在术语表中列出的。

主机表术语表可能已经过时了。刷新整个主机表术语表。

-26278 API error: Field does not exist on the host.

One of the host fields that the current EXTRACT statement specifies does not exist on the host, although it is listed in your host-table glossary. Your host-table glossary is probably out of date. Refresh the host-table information for the problem host table.

当前 EXTRACT 语句指定的主机字段在主机上不存在，尽管它在主机表词汇表中列出。

您的主机表术语表可能已经过时了。刷新整个主机表术语表。

-26279 API error: Query too large for Answer/Extractor.

The SELECT clause in the current EXTRACT statement is too long.

EXTRACT 语句中的 SELECT 子句太长。

-26280 API error: CICS Paging Code parameter is missing.

The CICS paging code is missing. Use the SETUP screen to set the CICS Paging Code parameter.

缺少 CICS 分页代码。使用 SETUP 屏幕设置 CICS Paging Code 参数。

-26281 API error: Cannot find message text.

An expected message was not received from the mainframe when DataExtract tried to retrieve host data or check the status of a job.

Exit DataExtract and retry the option.

当 DataExtract 尝试检索主机数据或检查作业状态时，未从大型机收到预期的消息。

退出 DataExtract 并重试该选项。

-26282 API error: Invalid SQLCR structure.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26283 API error: Environment already has open cursor.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26284 API error: SQLCR structure already open.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26285 API error: Query data not available at host.

The result for the SELECT clause of the current EXTRACT statement is not available at the host. Rerun the EXTRACT statement.

当前 EXTRACT 语句的 SELECT 子句的结果在主机上不可用。重新运行 EXTRACT 语句。

-26286 API error: SQLCR structure not open.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26287 API error: ORDER BY field duplicated.

The host fields in the ORDER BY clause in the current EXTRACT statement are duplicated. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句中 ORDER BY 子句中的主机字段是重复的。更正并重新运行 EXTRACT 语句。

-26288 API error: GROUP BY field duplicated.

The host fields in the GROUP BY clause in the current EXTRACT statement are duplicated. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句中 GROUP BY 子句中的主机字段是重复的。更正并重新运行 EXTRACT 语句。

-26289 API error: Expression element too long.

The expression in the SELECT clause in the current EXTRACT statement is too long. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句中 SELECT 子句中的表达式太长。更正并重新运行 EXTRACT 语句。

-26290 API error: Cannot recognize expression element.

The expression in the SELECT clause in the current EXTRACT statement is invalid. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句中 SELECT 子句中的表达式无效。更正并重新运行 EXTRACT 语句。

-26291 API error: Missing connector between expressions.

The SELECT clause in the current EXTRACT statement is missing the connector between expressions. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句中的 SELECT 子句缺少表达式之间的连接器。更正并重新运行 EXTRACT 语句。

-26292 API error: Missing close parenthesis.

The SELECT clause in the current EXTRACT statement is missing a matching parenthesis. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句中的 SELECT 子句缺少匹配的括号。更正并重新运行 EXTRACT 语句。

-26293 API error: Data type incorrect for context.

The SELECT clause in the current EXTRACT statement contains an item of an incorrect data type. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句中的 SELECT 子句包含不正确数据类型的项。更正并重新运行 EXTRACT 语句。

-26294 API error: Missing open parenthesis.

The SELECT clause in the current EXTRACT statement is missing an open parenthesis. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句中的 SELECT 子句缺少一个左括号。更正并重新运行 EXTRACT 语句。

-26295 API error: ESCAPE value must be single character.

The SELECT clause in the current EXTRACT statement contains an invalid ESCAPE value. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句中的 SELECT 子句包含无效的 ESCAPE 值。更正并重新运行 EXTRACT 语句。

-26296 API error: Field name required.

The SELECT clause in the current EXTRACT statement requires at least one host-field name. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句中的 SELECT 子句至少需要一个主机字段名称。

更正并重新运行 EXTRACT 语句。

-26297 API error: Query contains extra text.

The SELECT clause in the current EXTRACT statement contains extra text. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句中的 SELECT 子句包含额外的文本。更正并重新运行 EXTRACT 语句。

-26298 API error: Internal query parser error.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26299 API error: Must select at least one field or function value.

The SELECT clause of the current EXTRACT statement does not contain any host field or function value references. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句的 SELECT 子句不包含任何主机字段或函数值引用。

更正并重新运行 EXTRACT 语句。

-26300 API error: DISTINCT not supported.

The SELECT clause of the current EXTRACT statement contains the keyword DISTINCT, which is not supported. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句的 SELECT 子句包含关键字 DISTINCT，不支持该关键字。

更正并重新运行 EXTRACT 语句。

-26301 API error: Cannot use ALL in this context.

The ALL keyword is misused in the SELECT clause of the current EXTRACT statement. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句的 SELECT 子句中误用了 ALL 关键字。更正并重新运行 EXTRACT 语句。

-26302 API error: Invalid summary function.

The aggregate function in the SELECT clause of the current EXTRACT statement is invalid. Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句的 SELECT 子句中的聚集函数无效。更正并重新运行 EXTRACT 语句。

-26303 API error: Bad GROUP BY clause.

The GROUP BY clause in the current EXTRACT statement is invalid.

Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句中的 GROUP BY 子句无效。更正并重新运行 EXTRACT 语句。

-26304 API error: Bad ORDER BY clause.

The ORDER BY clause in the current EXTRACT statement is invalid.

Correct and rerun the EXTRACT statement.

当前 EXTRACT 语句中的 ORDER BY 子句无效。更正并重新运行 EXTRACT 语句。

-26305 API error: Cannot initialize NULL SQLDA.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26306 API error: Cannot initialize NULL SQLCA.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26307 API error: Cannot initialize NULL SQLEA.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26308 API error: Cannot initialize NULL SQLST.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26309 API error: Cannot initialize NULL SQLCR.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26310 API error: SQLST not prepared.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26311 API error: Invalid predefined query.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26312 API error: Predefined query not implemented.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26313 API error: Invalid query name.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26314 API error: Cursor already in use and open.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26315 API error: Cursor not open.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26316 API error: No sessions available.

No host sessions are available at the moment. Resubmit your request.

Check that the prior session or previously started processes have been terminated.

目前没有可用的主机会话。重新提交您的请求。检查先前会话或先前启动的进程是否已终止。

-26317 API error: Driver scan code file not found.

The driver scan code file, driver.dsc, cannot be found. Verify that the driver.dsc file exists in the path that the ANSAPI environment variable specifies, or in the current directory if ANSAPI is not set. Copy the file from $GBS_HOME/etc, if necessary.

无法找到驱动程序扫描代码文件 driver.dsc。验证 driver.dsc 文件是否存在于 ANSAPI环境变量指定的路径中，或者在当前目录中是否存在（如果未设置 ANSAPI）。如有必要，从 $GBS_HOME/etc 复制文件。

-26318 API error: Invalid message file.

The message file, message.txt, is invalid or corrupted. Recopy the message file from $GBS_HOME/etc to the path that the ANSAPI environment variable specifies, or to the current directory if ANSAPI is not set.

消息文件 message.txt 无效或损坏。从 $GBS_HOME/etc 将消息文件重新赋值到 ANSAPI环境变量指定的路径，或者当前目录（如果没有设置 ANSAPI）。

-26319 API error: Message file too long.

The message file, message.txt, is invalid or corrupt. Recopy the message file from $GBS_DATA/conf to the path that the ANSAPI environment variable specifies, or to the current directory if ANSAPI is not set.

消息文件 message.txt 无效或损坏。从 $GBS_DATA/conf 将消息文件重新赋值到 ANSAPI环境变量指定的路径，或者当前目录（如果没有设置 ANSAPI）。

-26320 API error: Error while reading file.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26321 API error: Not enough memory to read file.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26322 API error: File not found.

The message.txt or config.txt files cannot be found. Confirm that they exist.

没有找到 message.txt 或 config.txt 文件。请确认它们是否存在。

-26323 API error: Bad option descriptor.

The entry in the message.txt file, config.txt file, or parameter string is invalid. Correct the error.

message.txt 文件、config.txt 文件或参数字符串中的条目无效。请更正此错误。

-26324 API error: Invalid parameter value.

The message.txt file, config.txt file, or parameter string contains an invalid parameter value. Correct the error.

message.txt 文件、config.txt 文件或参数字符串中包含无效参数值。请更正此错误。

-26325 API error: Invalid option keyword.

The message.txt file, config.txt file, or parameter string contains an invalid option keyword. Correct the error.

message.txt 文件、config.txt 文件或参数字符串中包含无效项关键字。请更正此错误。

-26326 API error: Stable Time parameter missing.

The Stable Time parameter is missing from the host configuration file.

Use the SETUP screen to set the Stable Time parameter.

主机配置文件中 Stable Time 参数丢失。使用 SETUP 屏幕设置 Stable Time 参数。

-26327 API error: Lock Time parameter missing.

The Lock Time parameter is missing from the host configuration file.

Use the SETUP screen to set the Lock Time parameter.

主机配置文件中 Lock Time 参数丢失。使用 SETUP 屏幕设置 Lock Time 参数。

-26328 API error: Host Environment parameter missing.

The Host Environment parameter is missing from the host configuration file. Use the SETUP screen to set the Host Environment parameter.

主机配置文件中缺少 Host Environment 参数。使用 SETUP 屏幕设置 Host Environment 参数。

-26329 API error: Answer/DB Invocation Code parameter missing.

The Answer/DB Invocation Code parameter is missing from the host configuration file. Use the SETUP screen to set the Answer/DB Invocation Code parameter. Consult your Answer/Extractor DBA to determine the Answer/Extractor invocation code.

主机配置文件中缺少 Answer/DB 调用代码参数。使用 SETUP 屏幕设置Answer/DB Invocation Code 参数。请咨询您的 Answer/Extractor DBA以确定 Answer/Extractor 调用代码。

-26330 API error: Answer/DB Profile Name parameter missing.

The Answer/DB Profile Name parameter is missing from the host configuration file. Use the SETUP screen to set the Answer/DB Profile Name parameter. Consult your Answer/Extractor DBA to determine your Answer/Extractor profile name.

主机配置文件中缺少 Answer/DB Profile Name 参数。使用“SETUP”屏幕设置“Answer/DB Profile Name”参数。请咨询 Answer/Extractor DBA 以确定您的Answer/Extractor 配置文件名称。

-26331 API error: CICS Paging Code parameter missing.

The CICS Paging Code parameter is missing from the host configuration file. Use the SETUP screen to set the CICS Paging Code parameter.

Consult your Answer/Extractor DBA to determine the CICS paging code.

主机配置文件中缺少 CICS Paging Code 参数。使用 SETUP 屏幕设置 CICS Paging Code 参数。请咨询您的 Answer/Extractor DBA 以确定 CICS分页代码。

-26332 API error: CICS Termination Code parameter missing.

The CICS Termination Code parameter is missing from the host configuration file. Use the SETUP screen to set the CICS Termination Code parameter. Consult your Answer/Extractor DBA to determine the CICS termination code.

主机配置文件中缺少 CICS Paging Code 参数。使用 SETUP 屏幕设置 CICS Paging Code 参数。请咨询您的 Answer/Extractor DBA 以确定 CICS分页代码。

-26337 API error: No more data in report.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26338 API error: Invalid timer number.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26339 API error: Help file does not exist.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26341 API error: Parameter is wrong type.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26342 API error: Not enough parameter values.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26343 API error: Host table does not contain field.

This message indicates an internal error. Either the host table does not contain the field that the SELECT clause lists, or the table does not contain any fields.

此消息表示内部错误。主机表不包含 SELECT 子句列出的字段，或者表不包含任何字段。

-26344 API error: Class value out of range.

The value set in the Class parameter is out of range. Use the SETUP screen to correct the Class parameter.

Class 参数中设置的值超出范围。使用 SETUP 屏幕更正 Class 参数。

-26345 API error: Max value out of range.

The value in the Max Records to Process parameter or the Max Records to Retrieve parameter is out of range. Use the SETUP screen to correct the parameter.

Max Records to Process 参数或 Max Records to Retrieve 参数中的值超出范围。

使用“SETUP”屏幕更正参数。

-26346 API error: No more data in report.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26347 API error: Report contains incomplete data.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26348 API error: Report size exceeded; no data.

The result data that is selected by the SELECT clause in the current EXTRACT statement exceeds the allowed size on the host. Modify the EXTRACT statement to select less data. Rerun the EXTRACT statement.

当前 EXTRACT 语句中 SELECT 子句选择的结果数据超出了主机上允许的大小。

修改 EXTRACT 语句以选择较少的数据。重新运行 EXTRACT 语句。

-26349 API error: Report buffer too small.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26350 API error: Summary variable conflicts with host.

This message indicates an internal error. Exit DataExtract and retry the option.

此消息表示内部错误。退出 DataExtract 并重试该选项。

-26351 API error: Script file could not be read.

The connect or disconnect script file cannot be read. Verify that the connect or disconnect script file has the correct permissions. Use the Scripter utility to re-create it, if necessary.

无法读取连接或断开连接脚本文件。验证 connect 或 disconnect 脚本文件是否具有正确的权限。如有必要，请使用 Scripter 实用程序重新创建它。

-26352 API error: Not enough memory for script file.

This message indicates a memory-allocation error. Exit DataExtract and retry the option.

此消息表示内存分配错误。退出 DataExtract 并重试该选项。

-26360 Invalid bucket size specified for FOT index.

The bucket size for the forest of trees (FOT) index must range from 2 to the number of available index pages per dbspace.

森林（FOT）索引的桶大小必须从 2 到每个 dbspace 的可用索引页数。

-26361 Invalid 'hash on' list specified for FOT index.

The 'hash on' list for the forest of trees (FOT) index must be a prefix list of the index columns.

森林（FOT）索引的 'hash on' 列表必须是索引列的前缀列表。

-26362 Invalid data type for 'hash on' columns specified for FOT index.

The 'hash on' columns for the forest of trees (FOT) index must be built-in data types.

森林（FOT）索引的 'hash on' 列必须是内置数据类型。

-26363 FOT indexes cannot be functional indexes.

The 'hash on' columns for the forest of trees (FOT) index must be built-in data types.

森林（FOT）索引的 'hash on' 列必须是内置数据类型。

-26364 Attached FOT indexes are not supported.

FOT indexes must be detached indexes.

FOT 索引必须是已声明的索引。

-26365 Clustered FOT indexes are not supported.

FOT indexes must be non-clustered indexes.

FOT 索引必须是非集群索引。

-26371 Only the DBSSO can drop the audit property of the table.

The audit property can only be dropped by a DBSSO.

审计属性只能由 DBSSO 删除。

-26453 %s is not supported in this edition of IDS.

To use that functionality you must have IDS Ultimate Edition.

要使用该功能，您必须拥有 IDS Ultimate Edition。

-26811 Can not create temp table with replcheck columns It is not possible to create a temp table with REPLCHECK columns无法使用 REPLCHECK 列创建临时表。

-26812 Illegal usage of REPLCHECK columns You can not directly update REPLCHECK columns无法直接更新 REPLCHECK 列。

-26813 Can not add REPLCHECK when the table already has REPLCHECK columns The table already has REPLCHECK columns.

该表已有 REPLCHECK 列。

-26814 Can not drop REPLCHECK when table does not have REPLCHECK columns The table that you were attempting to alter does not have REPLCHECK columns.

您尝试更改的表没有 REPLCHECK 列。

-26815 Can not perform this operation on a table with REPLCHECK columns The operation that you attempted to perform can not be executed on a table containing REPLCHECK columns.

您尝试执行的操作无法在包含 REPLCHECK 列的表上执行。

-26910 The statement failed because it referenced a rolling window table.

The REFERENCES clause in a FOREIGN KEY definition cannot specify a rolling window table.

FOREIGN KEY 定义中的 REFERENCES 子句不能指定滚动窗口表。

-26911 The statement failed because each constraint on a rolling window table requires a supporting index.

You cannot add a PRIMARY KEY, FOREIGN KEY or UNIQUE constraint on a rolling window table unless an index on the table has the same RANGE INTERVAL fragmentation strategy as the table.

除非表上的索引具有与表相同的 RANGE INTERVAL 分片策略，否则无法在滚动窗口表上添加 PRIMARY KEY、FOREIGN KEY 或 UNIQUE 约束。

Explicitly create an index on the table (with no storage option for the index) before you add the PRIMARY KEY, FOREIGN KEY, or UNIQUE constraint.

在添加 PRIMARY KEY、FOREIGN KEY 或 UNIQUE 约束之前，请在表上显式创建索引（没有索引的存储选项）。

-26912 The statement failed because rowids are not allowed with rolling window tables.

Use the ALTER TABLE statement to remove the ROWID column and then define a RANGE INTERVAL fragmentation strategy with a purge policy clause.

使用 ALTER TABLE 语句删除 ROWID 列，然后使用 purge policy 子句定义RANGE INTERVAL 分片策略。

-26913 Cannot enable a rolling window because the table is referenced by other tables.

The table Ccannot be a rolling window table because it is referenced by an enabled FOREIGN KEY constraint on another table. Drop or disable that referential constraint, or else change your storage management strategy for the table.

表 C 不能是滚动窗口表，因为它由另一个表上的启用 FOREIGN KEY 约束引用。

删除或禁用该参考约束，或者更改表的存储管理策略。

-26914 The index was not created, because its storage differs from that of its rolling window table.

Rolling window tables require a RANGE INTERVAL fragmentation strategy.

The database server automatically applies the same storage strategy to each index that is subsequently defined on the table, but it returns this error if any storage option is specified for the index,or if the ALTER FRAGMENT statement references an index on a rolling window table.

滚动窗口表需要 RANGE INTERVAL 分片策略。数据库服务器会自动将相同的存储策略应用于随后在表上定义的每个索引，但如果为索引指定了任何存储选项，或者如果 ALTER FRAGMENT语句引用滚动窗口表上的索引，则会返回此错误。

To create an index on a rolling window table, use the CREATE INDEX statement with no storage option.

要在滚动窗口表上创建索引，请使用不带存储选项的 CREATE INDEX 语句。

-26915 The statement failed because the ROLLING FRAGMENTS and LIMIT TO clauses require positive integers.

In the CREATE TABLE and ALTER FRAGMENT MODIFY statements, make sure that iny literal value or expressio immediately following the ROLLING keyword or the LIMIT TO keywords evaluates to a positive integer.

在 CREATE TABLE 和 ALTER FRAGMENT MODIFY 语句中，确保紧跟 ROLLING 关键字或LIMIT TO 关键字的 iny 文字值或 expressio 计算为正整数。

-26916 The statement failed because the new table size would exceed the threshold set by the LIMIT TO clause.

The table referenced in this statement has a maximum storage size limit.

This statement would allocate more storage space for range fragments and index fragments than is allowed. No space would be available for new interval fragments.

You can increase the maximum table size by using the LIMIT TO clause.

Otherwise, if the CREATE TABLE or CREATE INDEX statement failed, specify a lower EXTENT SIZE value.

此语句中引用的表具有最大存储大小限制。此语句将为范围分片和索引分片分配比允许的更多存储空间。

没有空间可用于新的间隔分片。您可以使用 LIMIT TO 子句增加最大表大小。否则，如果 CREATE TABLE或 CREATE INDEX 语句失败，请指定较小的 EXTENT SIZE 值。

-26917 The statement failed because a UDR specifies the dbspace for the next interval fragment of this table or index.

You cannot change th elist of dbspaces for interval fragments when a UDR returns the dbspace names for storing new interval fragments. You can use the STORE IN clause of the ALTER FRAGMENT MODIFY statement to replace the user-defined function with a list of dbspaces in which to create system-generated interval fragments.

当 UDR 返回用于存储新间隔片段的 dbspace 名称时，您无法更改间隔分片的数据库空间。您可以使用ALTER FRAGMENT MODIFY 语句的 STORE IN 子句将用户定义的函数替换为 dbspace 列表，在该列表中可以创建系统生成的间隔分片。

-27000 Cannot support multiple connections over shared memory.

An application cannot use the CONNECT statement to make more than one connection that uses shared-memory communication (IPC).

应用程序无法使用 CONNECT 语句创建多个使用共享内存通信（IPC）的连接。

Ensure that the application makes only one shared-memory connection at a time. If the application must use concurrent connections, the database server administrator might need to change the connection type(as specified in the nettype field of the sqlhosts file) from a shared-memory connection to a network connection.

确保应用程序一次只创建一个共享内存连接。如果应用程序必须使用并发连接，则数据库服务器管理员可能需要将共享内存连接中的连接类型（在 sqlhosts 文件的 nettype 字段中指定）更改为网络连接。

-27001 Read error occurred during connection attempt.

This error can occur on either the client or database server side.

客户端或数据库服务器端可能会发生此错误。

When you encounter this error on the client side, it indicates that a network I/O error occurred when the client tried to connect to a database server. Probably the connection attempt timed out because the database server or the network was very busy, too many clients were attempting to connect to the database server simultaneously, or the database server was taken off-line during the connection attempt.

当您在客户端遇到此错误时，它表示客户端尝试连接到数据库服务器时发生网络 I/O 错误。

可能连接尝试超时，因为数据库服务器或网络非常繁忙，太多客户端试图同时连接到数据库服务器，或者数据库服务器在连接尝试期间脱机。

If you are using GBase 8s Dynamic Server, GBase 8s Universal Server,or GBase 8s OnLine Dynamic Server, verify that the database server is still online. If you are using GBase 8s SE, verify that the sqlexecd daemon for the database server is still running. Use either or both of the environment variables GBASEDBTCONTIME and GBASEDBTCONRETRY on the client side to increase the connection time and number of retry attempts.

如果您使用的是 GBase 8s Dynamic Server、GBase 8s Universal Server 或 GBase 8s OnLine Dynamic Server，请验证数据库服务器是否仍在联机状态。如果您使用的是 GBase 8s SE，请验证数据库服务器的 sqlexecd 守护程序是否仍在运行。在客户端使用环境变量 GBASEDBTCONTIME和 GBASEDBTCONRETRY 中的一个或两者来增加连接时间和重试次数。

When you encounter this error on the database server side, it is a warning that a network I/O error is detected while the database server is accepting a connection request from a client. This error usually occurs when the database server or the network is very busy or when too many clients are trying to connect to the database server at once. The database server might be taking so long to respond to a client that the client's connection request timed out before the connection is complete. Or possibly a client terminated its connection attempt before the connection is completely established.

当您在数据库服务器端遇到此错误时，警告在数据库服务器接受来自客户端的连接请求时检测到网络 I/O 错误。当数据库服务器或网络非常繁忙或者有太多客户端尝试一次连接到数据库服务器时，通常会发生此错误。数据库服务器可能需要很长时间才能响应客户端，即客户端的连接请求在连接完成之前超时。或者可能客户端在连接完全建立之前终止其连接尝试。

If this error is seen only occasionally in the server message log, it is just a warning. No corrective action is required on the server side.

如果仅在服务器消息日志中偶尔看到此错误，则只是一个警告。服务器端不需要采取纠正措施。

If this error occurs frequently on a database server that runs on a host with multiple processors, you might want to tune the database server by increasing the number of poll threads and/or listener threads.

如果在具有多个处理器的主机上运行的数据库服务器上经常发生此错误，则可能需要通过增加轮询线程和/或监听器线程的数量来调整数据库服务器。

-27002 No connections are allowed in quiescent mode.

You are attempting to connect to a database server that is in quiescent mode. Verify that your GBASEDBTSERVER environment variable is set correctly. Ask the database server administrator to bring the appropriate database servers to online mode.

您正在尝试连接到处于静默模式的数据库服务器。验证是否正确设置了 GBASEDBTSERVER环境变量。请数据库服务器管理员将相应的数据库服务器置于联机模式。

-27003 Internal Communications Error: internal inconsistency detected.

The GBase 8s client/server communication system has detected an internal inconsistency. Typically, a client application reports this error. This error might be a memory-corruption error due to a programming bug. If the database server or a utility reported the error, it is an GBase 8s internal error. When an GBase 8s internal error occurs, note all circumstances and contact GBase Technical Support.

GBase 8s 客户机/服务器通信系统检测到内部不一致。通常，客户端应用程序报告此错误。

此错误可能是由于编程错误导致的内存损坏错误。如果数据库服务器或实用程序报告了错误，则为 GBase 8s 内部错误。当发生 GBase 8s 内部错误时，请记录所有情况并与G Base 技术支持部门联系。

-27004 Illegal sqlhosts file option/parameter, parameter, for dbservername,servername.

You specified an invalid option or parameter in your sqlhosts file.

Check the option ID and parameter associated with servername in the sqlhosts file.

在 sqlhosts 文件中指定了无效的选项或参数。检查 sqlhosts 文件中与 servername 关联的选项 ID 和参数。

Linux,UNIX: If you use either the IPC stream pipe (onipcstr) protocol or the IPC shared memory (onipcshm) protocol, ensure that the communications file directory (cfd option) is shorter than or equal to 70 bytes. If the directory is a relative path, the length includes the $GBS_HOME directory.

Linux、UNIX：如果使用 IPC 流管道（onipcstr）协议或 IPC 共享内存（onipcshm）协议，请确保通信文件目录（cfd 选项）小于或等于 70 个字节。如果目录是相对路径，则长度包括$GBS_HOME 目录。

-27005 Illegal sqlexecd daemon option, option_value.

You specified an invalid sqlexecd daemon option. Check the option option_value and its parameter.

指定了一个无效的 sqlexecd 守护程序选项。请检查选项 option_value 及其参数。

-27006 Network driver cannot establish listen endpoint.

You specified stream pipe (ipcstr) as the network-communication type for this database server. The database server is not able to create the stream pipe. The most common cause of this error is that another database server on your network is already using the service name for this database server.

您指定了流管道（ipcstr）作为此数据库服务器的网络通信类型。数据库服务器无法创建流管道。

此错误的最常见原因是网络上的另一个数据库服务器已在使用此数据库服务器的服务名称。

Check that the servicename value in the $GBS_DATA/conf/sqlhosts file or in the SQLHOSTS registry information is unique across all database servers on your network. If the servicename is unique, check the accompanying ISAM code for additional error information.

检查 $GBS_DATA/conf/sqlhosts 文件或 SQLHOSTS 注册表信息中的 servicename 值是否在网络上的所有数据库服务器上都是唯一的。如果 servicename 是唯一的，请检查附带的 ISAM 代码以获取其他错误信息。

If a previously created stream pipe with the same name is not released by an aborted online server, you need to manually remove the stream pipe files /GBASEDBTTMP/.str and /GBASEDBTTMP/.exp.

如果先前创建的同名流管道没有被中止的联机服务器释放，则需要手动删除流管道文件/GBASEDBTTMP/.str 和 /GBASEDBTTMP/.exp。

-27007 Invalid file descriptor opened for the user thread.

An internal GBase 8s network error has occurred in the TLITCP poll thread. Note all circumstances and contact GBase Technical Support.

TLITCP 轮询线程中发生内部 GBase 8s 网络错误。请注意所有情况并联系 GBase 技术支持。

-27010 Only an administrative user can connect in administrative user mode.

The database server is in administrative user mode. You must set the ADMIN_USER_MODE_WITH_DBSA parameter to '1' to allow any administrative user to connect. If the ADMIN_USER_MODE_WITH_DBSA parameter is set to '0', then only user "gbasedbt" or the non-root server owner can connect.

数据库服务器处于管理用户模式。必须将 ADMIN_USER_MODE_WITH_DBSA 参数设置为“1”以允许任何管理用户进行连接。如果 ADMIN_USER_MODE_WITH_DBSA 参数设置为“0”，则只有“gbasedbt”用户或非根服务器所有者才能连接。

-27009 Connection to HDR secondary not allowed using group name Your SERVERNUM setting specifies a group entry for an HDR pair.

HDR primary server is currently not available, and HDR secondary server is still in secondary mode.

To connect to HDR secondary server in read-only mode, set SERVERNUM to the explicit SERVERNUM of the secondary server.

To be able to process transactions, either bring up your HDR primary server,or convert your HDR seconadry server to standard mode.

SERVERNUM 设置指定 HDR 对的组条目。HDR 主服务器当前不可用，HDR 辅助服务器仍处于辅助模式。要以只读模式连接到 HDR 辅助服务器，请将 SERVERNUM 设置为辅助服务器的显式 SERVERNUM。为了能够处理事务，请启动 HDR 主服务器，或将 HDR 辅助服务器转换为标准模式。

-27100 Internal Communications Error: NSF subsystem error.

This error message can appear if there is an internal NSF subsystem failure.

Please contact GBase Technical Support.

如果存在内部 NSF 子系统故障，则会出现此错误消息。请与 GBase 技术支持部门联系。

-27151 Internal error: No Communications Support Module specification string defined in the sqlhosts file.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-27152 Internal error: Communication Support Services context already exists;cannot create another one.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-27153 Internal error: Communication Support Services contact is NULL.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-27154 Internal error: invalid ASF_TIMEOUT semantics; same input buffer expected.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-27155 Internal error: Communication Support Services returned an undefined css_status.state code.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-27156 Internal error: invalid ASF- Communication Support Services state.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-27157 Internal error: no receiving buffer available.

If this internal error recurs, note all circumstances and contact GBase Technical Support.

如果此错误再次发生，请注意所有情况，并联系 GBase 技术支持。

-28014 Secure Sockets Layer error.

An error occurred during a Secure Socket Layer operation. For more information,refer to the accompanying Global Security Kit (GSKit) error message.

在安全套接字层操作期间发生错误。有关更多信息，请参阅附带的 Global Security Kit (GSKit)错误消息。

-28015 Secure Sockets Layer configuration error.

An error occurred while reading the Secure Sockets Layer configuration file (conssl.cfg).

读取安全套接字层配置文件(conssl.cfg)时出错。

-28016 GBase Global Security Kit (GSKit) or higher is not installed.

The GBase Global Security Kit (GSKit) is either not installed or the version that is installed is too old. The GSKit provides APIs for the Secure Sockets Layer (SSL) communication and encryption functionality. If you want to set up SSL connections or use encryption functionality, you must install the GSKit.

For instructions on installing GSKit, refer to the $GBS_HOME/gskit/README file.

GBase 全局安全工具包（GSKit）未安装或安装的版本太旧。GSKit 为安全套接字层（SSL）通信和加密功能提供 API。如果要设置 SSL 连接或使用加密功能，则必须安装GSKit。有关安装 GSKit 的说明，请参阅 $GBS_HOME/gskit/README 文件。

-28021 A trusted connection was not established because a trusted context is not defined or not enabled for the specified authorization ID.

Ensure that the trusted context is correctly defined and enabled, and then establish a trusted connection.

确保正确定义并启用了可信上下文，然后建立可信连接。

-28022 A trusted connection was not established because the encryption requirement for the connection was not met.

Ensure that the encryption requirement for the trusted context is correctly defined and that the port is correctly encrypted.

确保正确定义了可信上下文的加密要求，并确保端口已正确加密。

-29000 Application server error (server_error_number).

A generic application-server error occurred. Examine the original foreign SQLCODE. You can find it in either SQLERRD[1] or as part of SQLERRM. Look up the explanation for this SQLCODE in the documentation for the foreign server product. Apply the tokens, if any, that are returned in the SQLERRM field to the explanation.

发生了一个通用应用程序服务器错误。检查原始的外部 SQLCODE。您可以在 SQLERRD[1]中找到它，也可以在 SQLERRM 中找到它。在外部服务器产品的文档中查找此 SQLCODE的说明。将 SQLERRM 字段中返回的标记（如果有）应用于说明。

-29002 Supplied real-RDB-name does not match the real-RDB-name in sqlhosts.

A mismatch was detected between the user-supplied real-RDB-name and the real-RDB-name that was derived from the user-supplied alias-RDB-name using the sqlhosts file.

用户提供的 real-RDB-name 和使用 sqlhosts 文件从用户提供的 alias-RDB-name 派生的real-RDB-name 之间检测到不匹配。

Check the spelling of the user-supplied real-RDB-name. Ensure that the user-supplied alias-RDB-name is the correct one.

检查用户提供的 real-RDB-name 的拼写。确保用户提供的 alias-RDB-name 正确。

If SNA network protocol is used to connect to the application server,check the real-RDB-name column (the "hostname" field) in the "sqlhosts" file for the alias-RDB-name entry, and check that it is spelled correctly.

如果使用 SNA 网络协议连接到应用程序服务器，请在“sqlhosts”文件中检查 alias-RDB-name条目的 real-RDB-name 列（“hostname”字段），并检查它是否拼写正确。

If TCP/IP network protocol is used to connect to the application server,check the "RDB=real-RDB-name" option (in the "options" field) in the"sqlhosts" file for the alias-RDB-name entry, and check that it is spelled correctly.

如果使用 TCP/IP 网络协议连接到应用程序服务器，请检查 alias-RDB-name 条目的“sqlhosts”文件中的“RDB =real-RDB-name”选项（在“options”字段中），并检查拼写是否正确。

-29003 RDB real-RDB-name not found at the application server.

Although a communication conversation was allocated, the application server refused to connect because it has a real-RDB-name that is different from that to which the application would like to connect.

虽然已经分配了通信对话，但应用程序服务器拒绝连接，因为它的 real-RDB-name 与应用程序要连接的名称不同。

Examine the sqlhosts file on the Gateway computer. Identify the entry with the alias-RDB-name to which the application is referring.

检查 Gateway 计算机上的 sqlhosts 文件。使用应用程序引用的 alias-RDB-name 标识条目。

If SNA network protocol is used to connect to the application server,ensure that the "hostname" field contains a correct value.

如果使用 SNA 网络协议连接到应用程序服务器，请确保“hostname”字段包含正确的值。

If TCP/IP network protocol is used to connect to the application server,ensure that the "RDB=real-RDB-name" option in the "options" field contains a correct value.

如果使用 TCP/IP 网络协议连接到应用程序服务器，请确保“options”字段中的“RDB=real-RDB-name”选项包含正确的值。

-29004 DRDA protocol error. ReplyMsg[,sub-code]

,sub-code

A DRDA protocol error prevents the successful execution of the current SQL statement. This error will not affect the successful execution of subsequent SQL statements.

DRDA 协议错误会阻止成功执行当前 SQL 语句。此错误不会影响后续 SQL 语句的成功执行。

A DRDA internal Distributed Data Management (DDM) reply message (RM)was received from the application server. That message indicates that an error has occurred. The application server or possibly the application requestor (AR) detected an error.

从应用程序服务器接收 DRDA 内部分布式数据管理（DDM）回复消息（RM）。

该消息表明发生了错误。应用程序服务器或应用程序请求程序（AR）检测到错误。

A hexadecimal codepoint and possibly a hexadecimal sub-code are returned as a token in SQLERRM.

在 SQLERRM 中，返回一个十六进制代码点，可能还返回一个十六进制子代码作为令牌。

To interpret the hexadecimal codepoint and the hexadecimal sub-code,you need DDM knowledge.

要解释十六进制代码点和十六进制子代码，您需要了解 DDM 知识。

The hexadecimal codepoint is the 2-byte hexadecimal codepoint for the DDM reply message that represents the error and is one of the following:十六进制码点是表示错误的 DDM 回复消息的 2 字节十六进制编码点，它是以下内容之一：* X'220A' -- DSCINVRM* X'124C' -- SYNTAXRM* X'1245' -- PRCCNVRM* X'1254' -- CMDCHKRM* X'220E' -- DTAMCHRM* X'2202' -- QRYNOPRM* X'220F' -- QRYPOPRM* X'2207' -- RDBACCRM* X'2204' -- RDBNACRM The first three reason codes (DSCINVRM, SYNTAXRM, and PRCCNVRM)accompany a 2-byte hexadecimal sub-code. In all other cases, the sub-code is zero.

前三个原因代码（DSCINVRM、SYNTAXRM 和 PRCCNVRM）伴随着一个 2 字节的十六进制子代码。

在所有其他情况下，子代码为零。

When nonzero, the high-order byte of the sub-code indicates the site at which the error was detected. If the AR detects the error, it is X'01.

If the application server detects the error, it is X'02'. The lower-order byte is as follows:当为非零时，子代码的高位字节表示检测到错误的站点。如果 AR 检测到错误，则为X'01。

如果应用程序服务器检测到错误，则为 X'02'。低位字节如下：* Description Error Code (DSCERRCD) if reason code = DSCINVRM如果原因代码 = DSCINVRM 则是错误编码的描述（DSCERRCD）* Syntax Error Code (SYNERRCD) if reason code = SYNTAXRM如果原因代码 = SYN TAXRM 则是语法错误代码（SYNERRCD）* Conversational Protocol Error Code (PRCCVNCD) if reason code =PRCCNVRM如果原因代码 = PRCCNVRM 则是会话协议错误代码（PRCCVNCD）Contact the DBA for assistance in analyzing the SQL statement that yielded this SQLCODE. If the error recurs, note all circumstances and contact GBase Technical Support.

请联系 DBA 以获取有关分析产生此 SQLCODE 的 SQL 语句的帮助。

如果错误再次出现，请注意所有情况并联系 GBase 技术支持。

-29005 Hard DRDA protocol error. ReplyMsg[,sub-code]

,sub-code

A DRDA protocol error caused deallocation of the conversation.

DRDA 协议错误导致会话取消分配。

A DRDA internal Distributed Data Management (DDM) reply message (RM)was received from the application server. The message indicates that an error has occurred. The application server or possibly the application requestor (AR) detected an error.

从应用程序服务器接收 DRDA 内部分布式数据管理（DDM）回复消息（RM）。

该消息表明发生了错误。应用程序服务器或应用程序请求程序（AR）检测到错误。

A hexadecimal codepoint and possibly a hexadecimal sub-code are returned as a token in SQLERRM.

在 SQLERRM 中，返回一个十六进制代码点，可能还返回一个十六进制子代码作为令牌。

To interpret the hexadecimal codepoint and the hexadecimal sub-code requires DDM knowledge.

要解释十六进制代码点和十六进制子代码，您需要了解 DDM 知识。

The hexadecimal codepoint is the 2-byte hexadecimal codepoint for the DDM reply message that represents the error and is one of the following:十六进制码点是表示错误的 DDM 回复消息的 2 字节十六进制编码点，它是以下内容之一：* X'220A' -- DSCINVRM* X'124C' -- SYNTAXRM* X'1245' -- PRCCNVRM* X'1218' -- MGRDEPRM* X'1232' -- AGNPRMRM* X'1254' -- CMDCHKRM* X'220E' -- DTAMCHRM* X'2202' -- QRYNOPRM* X'220F' -- QRYPOPRM* X'2207' -- RDBACCRM* X'2204' -- RDBNACRM A 2-byte hexadecimal sub-code is accompanied with the first four reason codes (DSCINVRM, SYNTAXRM, PRCCNVRM, and MGRDEPRM). In all other cases,the sub-code is zero.

2字节的十六进制子代码附带前四个原因代码（DSCINVRM，SYNTAXRM，PRCCNVRM和MGRDEPRM）。

在所有其他情况下，子代码为零。

When nonzero, the high-order byte of the sub-code indicates the site at which the error was detected. If the AR detects the error, it is X'01.

如果应用程序服务器检测到错误，则为 X'02'。低位字节如下：* Description Error Code (DSCERRCD) if reason code = DSCINVRM如果原因代码 = DSCINVRM 则是错误编码的描述（DSCERRCD）* Syntax Error Code (SYNERRCD) if reason code = SYNTAXRM如果原因代码 = SYN TAXRM 则是语法错误代码（SYNERRCD）* Conversational Protocol Error Code (PRCCVNCD) if reason code =PRCCNVRM如果原因代码 = PRCCNVRM 则是会话协议错误代码（PRCCVNCD）* Manager Dependency Error Code (DEPERRCD) if reason code =MGRDEPRM如果原因代码 = MGRDEPRM 则是管理员依赖性错误代码（DEPERRCD）Notify the DBA for assistance in analyzing the SQL statement that yielded this SQLCODE. If the error recurs, note all circumstances and contact GBase Technical Support.

通知 DBA 以帮助分析产生此 SQLCODE 的 SQL 语句。

如果错误再次出现，请注意所有情况并联系 GBase 技术支持。

-29006 DRDA connect protocol error. Manager,level: (manager,level) not supported.

The connect process failed.

连接进程失败。

The application server cannot support a DRDA manager level that was requested by the AR (application requester) during the DRDA connection process.

应用程序服务器无法支持在 DRDA 连接过程中 AR（应用程序请求者）请求的 DRDA 管理器级别。

The hexadecimal codepoint of the manager (MGRLVL) and the hexadecimal codepoint of the level requested are returned as a token in SQLERRM.

在 SQLERRM 中，管理器的十六进制编码点(MGRLVL)和请求级别的十六进制编码点作为令牌返回。

Attempt to connect to the application server again. If the problem persists, notify the DBA for assistance. If the error recurs,note all circumstances and contact GBase Technical Support.

尝试再次连接到应用程序服务器。如果问题仍然存在，请通知 DBA 以获取帮助。

如果错误再次出现，请注意所有情况并联系 GBase 技术支持。

-29007 RDB authorization failure. RDB-userID,RDB: RDB-userID,RDB-name.

The user is not authorized to access the target RDB. The request is rejected.

用户无权访问目标 RDB。该请求被拒绝。

Contact the DBA of the RDB side if necessary. Correct the authorization problem and rerun the application program.

如有必要，请联系 RDB 方面的 DBA。更正授权问题并重新运行应用程序。

-29008 DDM parameter (parameter-codepoint) not supported error. Disconnected from AS.

An unsupported DDM parameter is encountered.

遇到不受支持的 DDM 参数。

The remote RDB received an unsupported/unrecognized DDM parameter. The current SQL statement is terminated. The application is disconnected from the application server.

远程 RDB 收到不支持/无法识别的 DDM 参数。当前的 SQL 语句已终止。

应用程序与应用程序服务器断开连接。

The hexadecimal codepoint of the DDM parameter in question is returned as a token in SQLERRM.

在 SQLERRM 中，有问题的 DDM 参数的十六进制代码点作为标记返回。

To interpret the hexadecimal codepoint of the DDM parameter requires DDM knowledge.

要解释 DDM 参数的十六进制代码点，需要 DDM 知识。

Attempt to rerun the application. If the problem persists, notify the DBA for assistance in analyzing the SQL statement that yields this SQLCODE. If the error recurs, note all circumstances and contact GBase Technical Support.

尝试重新运行该应用程序。如果问题仍然存在，请通知 DBA 以帮助分析产生此 SQLCODE 的 SQL 语句。

如果错误再次出现，请注意所有情况并联系 GBase 技术支持。

-29009 DDM parameter value (parameter,parameter-value) not supported.

Disconnected from AS.

The remote RDB received an unsupported/unrecognized parameter value for a DDM parameter. The current SQL statement is terminated. The application is disconnected from the application server.

远程 RDB 收到不支持/无法识别的 DDM 参数。当前的 SQL 语句已终止。

应用程序与应用程序服务器断开连接。

The hexadecimal codepoints of the DDM parameter and the parameter value in question are returned as a token in SQLERRM.

在 SQLERRM 中，DDM 参数和参数值的十六进制代码点已作为标记返回。

To interpret the hexadecimal codepoints of the DDM parameter and the parameter value requires DDM knowledge.

要解释 DDM 参数和参数值的十六进制代码点，需要 DDM 知识。

尝试重新运行该应用程序。如果问题仍然存在，请通知 DBA 以帮助分析产生此 SQLCODE的 SQL 语句。如果错误再次出现，请注意所有情况并联系 GBase 技术支持。

-29010 AS reply message (codepoint=codepoint) not supported by Gateway.

The Gateway received an unsupported/unrecognized DDM reply message.

The current SQL statement is terminated. The application is disconnected from the application server.

Gateway 接收到不支持/无法识别的 DDM 回应消息。当前 SQL 语句已经终止。

应用程序与应用程序服务器断开连接。

The hexadecimal codepoint for the received DDM reply message is returned as a token in the SQLERRM.

在 SQLERRM 中，接收的 DDM 的十六进制代码点已作为标记返回。

To interpret the hexadecimal codepoint of the DDM reply message requires DDM knowledge.

要解释 DDM 参数和参数值的十六进制代码点，需要 DDM 知识。

-29011 SNA communication error. GBase 8s-SQLCODE,native-SNA-rc:GBase 8s-communication-SQLCODE,native-SNA-return-code.

An GBase 8s communication-related SQLCODE and a hexadecimal native SNA service return code are returned as a token in SQLERRM.

在 SQLERRM 中，与 GBase 8s 通信相关的 SQLCODE 和十六进制本地 SNA服务返回代码作为令牌返回。

The GBase 8s communication-related SQLCODE is a platform-independent return code that the GBase 8s communication adaptation service generates. Refer to the explanation of this SQLCODE for a more specific description of the error.

与 GBase 8s 通信相关的 SQLCODE 是 GBase 8s 通信适配服务生成的与平台无关的返回码。

有关错误的更具体描述，请参阅此 SQLCODE 的说明。

The native SNA service return code is a return code generated by the local SNA service that provides the SNA support on each particular platform. Refer to the manufacturer's documentation for the SNA support that provides the underlying communication service for an explanation of this return code.

本机 SNA 服务返回代码是由本地 SNA 服务生成的返回代码，该服务在每个特定平台上提供 SNA 支持。

有关 SNA 支持的信息，请参阅制造商的文档，该支持提供底层通信服务以解释此返回代码。

Ensure that the native SNA/APPC service is installed correctly. Check that all the required SNA daemon processes (if any) are running. Also check that the connection file for the target RDB is set up correctly.

In a Sun environment, also check that the Sun APPC Gateway is set up correctly.

确保正确安装了本机 SNA/APPC 服务。检查所有必需的 SNA 守护程序进程（如果有）是否正在运行。还要检查是否正确设置了目标 RDB 的连接文件。在 Sun 环境中，还要检查是否正确设置了 Sun APPC 网关。

-29012 One or more tables have been dropped, altered, or renamed.

A prepared statement is no longer valid because the schema of the tables that it references has changed. You must prepare the statement again.

预准备语句不再有效，因为它引用的表的模式已更改。您必须再次准备语句。

-29013 AS resource not available. Reason,Type, Name,PrdID,RDB:Reason,ResourceType,ResourceName,ProductID,RDBname.

The resource is not available at the remote RDB. The current SQL statement is terminated.

远程 RDB 上的资源不可用。当前的 SQL 语句已终止。

Reason, ResourceType, ResourceName, ProductID, and RDBname are returned as a token in SQLERRM.

Reason、ResourceType、ResourceName、ProductID 和 RDBname 在 SQLERRM 中作为标记返回。

Verify the identity of the resource that was not available. Ensure that the application server has the needed resource.

验证不可用的资源的标识。确保应用程序服务器具有所需的资源。

-29014 Hard AS resource not available. Reason,Type, Name,PrdID,RDB: Reason,ResourceType,ResourceName,ProductID,RDBname.

The resource is not available at the remote RDB. The application is disconnected from the application server.

远程 RDB 上的资源不可用。应用程序与应用程序服务器断开连接。

Reason, ResourceType, ResourceName, ProductID, and RDBname are returned as a token in SQLERRM.

Reason、ResourceType、ResourceName、ProductID 和 RDBname 在 SQLERRM 中作为标记返回。

Verify the identity of the resource that was not available. Ensure that the application server has the resource needed. Rerun the application.

验证不可用的资源的标识。确保应用程序服务器具有所需的资源。重新运行应用程序。

-29015 Non-bind related DDM command (codepoint=codepoint) attempted during bind.

A remote execution of SQL statement or a remote command was attempted while a remote bind was in progress. During bind, only Bind, End Bind,ROLLBACK, or COMMIT are allowed.

在进行远程绑定时，尝试远程执行 SQL 语句或远程命令。

在绑定期间，只允许 Bind、End Bind、ROLLBACK 或 COMMIT。

This message indicates a Gateway internal logic error. The DDM command in question is returned as a token in SQLERRM.

该消息表示 Gateway 内部逻辑错误。出问题 DDM 命令作为令牌在 SQLERRM 中返回。

Applications from end users should not go into bind mode. The only time a package bind should occur is the package-bind process in the gwdba utility. Rerun the application. If the error recurs, note all circumstances and contact GBase Technical Support.

来自最终用户的应用程序不应进入绑定模式。包绑定应该发生的唯一时间是 gwdba 实用程序中的包绑定过程。重新运行应用程序。如果错误再次发生，请注意所有情况，并与 GBase 技术支持部门联系。

-29016 Bind related command (codepoint=codepoint) encountered when bind not active.

Binding of a statement or End Bind was attempted with a specific package name and consistency token while the package was not undergoing bind process.

在程序包未进行绑定过程时，尝试使用特定程序包名称和一致性标记绑定语句或 End Bind。

This message indicates a Gateway internal logic error. Try the application again. If the error recurs, note all circumstances and contact GBase Technical Support.

此消息表示网关内部逻辑错误。再次尝试该应用程序。

如果错误再次出现，请注意所有情况并联系 GBase 技术支持。

-29018 AS does not support the DDM command: command-codepoint.

The application server does not support the DDM command. This error causes termination of processing of the command. The application is also disconnected from the application server.

应用程序服务器不支持DDM命令。此错误导致终止命令处理。

应用程序也与应用程序服务器断开连接。

The SQLERRM contains the hex codepoint of the DDM command in question.

SQLERRM 包含出现问题的 DDM 命令的十六进制代码点。

Rerun the application. If the problem persists, notify the DBA for assistance in analyzing the SQL statement that yielded this SQLCODE. If the error recurs, note all circumstance and contact GBase Technical Support.

重新运行该应用程序。如果问题仍然存在，请通知 DBA 以帮助分析产生此 SQLCODE 的 SQL 语句。

如果错误再次出现，请注意所有情况并联系 GBase 技术支持。

-29019 AS does not support the DDM object type: object-codepoint.

The application server does not support the DDM object. The processing of the current SQL statement is terminated. The application is disconnected from the application server.

应用程序服务器不支持 DDM 对象。终止处理当前 SQL 语句。应用程序与应用程序服务器断开连接。

The SQLERRM contains the hex DDM codepoint of the object type in question.

SQLERRM 包含对象类型是出现问题的十六进制 DDM 代码点。

Attempt to run the application again. If the problem persists, notify the DBA for assistance in analyzing the SQL statement that yielded this SQLCODE. If the error recurs, note all circumstances and contact GBase Technical Support.

尝试再次运行该应用程序。如果问题仍然存在，请通知 DBA 以帮助分析产生此 SQLCODE 的 SQL 语句。

如果错误再次出现，请记录所有情况并联系 GBase 技术支持。

-29030 Feature feature-name not supported by the Gateway.

The Gateway product does not support this feature. (For example, it does not support GBase 8s-specific SQL statements or GBase 8s-specific data types.) The feature that is not supported is returned as a token in SQLERRM.

Gateway 产品不支持此功能。（例如，它不支持特定于 GBase 8s 的 SQL 语句或特定于GBase 8s 的数据类型。）不支持的功能在 SQLERRM 中作为标记返回。

Correct the application and do not use any feature that the Gateway cannot support on SQL statements that will go through the Gateway during execution.

更正应用程序，并且不要使用网关在执行期间将通过网关的 SQL 语句不支持的任何功能。

-29031 Table or view name objname has an invalid format The Add-table and Purge-table options of the gwdba utility for adding and purging tables and views from the GBase 8s catalog on an application server require a file of table and view names as input. The listed table or view name (objname) has an invalid format. The format of table and view names in the file must be in the following format:gwdba 实用程序的 Add-table 和 Purge-table 选项用于在应用程序服务器上添加和清除GBase 8s 目录中的表和视图，需要使用表和视图名称文件作为输入。列出的表或视图名称（objname）格式无效。文件中表和视图名称的格式必须采用以下格式：owner.tabname-29032 Application Server CCSIDs could not be determined.

The Gateway is required to perform outbound character code-set conversion for this client operating-system locale, but the Gateway could not determine the CCSIDs of the application server.

网关需要为此客户端操作系统语言环境设置执行出站字符代码集转换，但网关无法确定应用程序服务器的 CCSID。

Notify the administrator of the Gateway. The administrator must set the GWASCCSID environment variable to match the single-byte CCSID of the application server. If network mode is being used, the Gateway administrator must stop and restart the Gateway daemon after setting the GWASCCSID environment variable. The Gateway administrator must then connect to the application server using either a CONNECT statement or a DATABASE statement. This connection captures all the CCSIDs in the cache file $GBS_HOME/gw/sysinfo/prnccsid.dat.

通知网关的管理员。管理员必须设置 GWASCCSID 环境变量以匹配应用程序服务器的单字节 CCSID。

如果正在使用网络模式，则网关管理员必须在设置 GWASCCSID 环境变量后停止并重新启动 Gateway 守护程序。然后，网关管理员必须使用 CONNECT 语句或 DATABASE 语句连接到应用程序服务器。

此连接捕获缓存文件 $GBS_HOME/gw/sysinfo/prnccsid.dat 中的所有 CCSID。

-29033 GBase 8s GLS locale could not be loaded: localename, errno,locale-file-name.

localename The name of the GBase 8s GLS locale that could not be loaded. The value for localename must be of the format language_territory.codeset.

不能加载的 GBase 8s GLS 语言环境的名称。此 localename 的值必须是 language_territory.codeset 格式。

errno A number that indicates the specific reason that the GBase 8s GLS locale could not be loaded.

指示不能加载 GBase 8s GLS 语言环境的原因的编号。

locale-file-name The subdirectory and filename (for example, /en_US/0333.lco)of the GBase 8s GLS locale file that could not be loaded.

不能加载 GBase 8s GLS 语言环境的子目录和文件名（例如，/en_US/0333.lco）。

language A two-letter lowercase abbreviation for the languagename.

该语言名称的两个字母小写缩写。

territory A two-letter uppercase abbreviation for the territory name.

地区名称的两个字母大写缩写。

codeset The name of the character code set for the locale.

本地语言环境字符代码集名称。

Valid values for the codeset field are registered in the$GBS_HOME/gls/cm/REGISTRY file. The values are character strings that describe the code set. However, if a codeset field value is an integer in the range from 1 to 65,535, it is an acceptable value even if it is not in the REGISTRY file.

codeset 字段的有效值在 $GBS_HOME/gls/cm/ 注册表文件中注册。这些值是描述代码集的字符串。但是，如果代码集字段值是介于 1 到 65，535 之间的整数，则即使它不在注册表文件中，也是一个可接受的值。

An attempt to load the GBase 8s GLS locale that localename specified failed for the reason that errno indicates, as follows:尝试加载 GBase 8s GLS 语言环境，指出 localename 因 errno 指示的原因而失败，如下所示：6- The locale specification localename is in a bad format.

6- 语言环境规范localename格式错误。

The Gateway administrator must correct this specification.

网关管理员必须更正此规范。

7- The locale file that locale-file-name specified does not exist.

7- locale-file-name 指定的语言环境文件不存在。

If the appropriate directory (see the following paragraph) does not contain the locale file that the subdirectory and filename that locale-file-name specified, this GBase 8s GLS locale is not available.

Read your GBase 8s product documentation to ensure that you specified the GBase 8s GLS localename correctly (using environment variables or other mechanisms that the documentation describes). The GBase 8s GLS localename might be incorrectly specified or might be equivalent to another GBase 8s GLS locale that is available.

如果相应的目录（请参阅以下段落）不包含 locale-file-name 指定的子目录和文件名的语言环境文件，则此 GBase 8s GLS 语言环境不可用。阅读 GBase 8s产品文档以确保正确指定了 GBase 8s GLS 语言环境名称（使用环境变量或文档中描述的其他机制）。GBase 8s GLS 语言环境名称可能未正确指定，或者可能与另一个可用的 GBase 8s GLS 语言环境等效。

If the subdirectory and filename that locale-file-name specified exist,verify that your product was installed correctly so that the GBase 8s GLS locale file can be located. Specifically, ensure that the GL_PATH environment variable is set (or not set) according to the Gateway installation instructions:如果指定的子目录和文件名存在，请验证产品安装是否正确，以便 GBase 8s GLS语言环境文件能够被定位。具体而言，确保根据 Gateway 安装说明设置(或不设置) GL_PATH 环境变量：* If GL_PATH is not set, verify that the subdirectory and file that locale-file-name specifies are in the $GBS_HOME/gls/lc directory.

如果未设置 GL_PATH ，则请验证 locale-file-name 指定的子目录和文件是否在 $GBS_HOME/gls/lc 目录中。

* If GL_PATH is set, verify that the subdirectory and filename that locale-file-name specifies are in one of the directories that the GL_PATH environment variable specifies.

如果设置了 GL_PATH ，则请验证 locale-file-name 指定的子目录和文件是否在 GL_PATH 环境变量指定的目录中。

10- The locale file that locale-file-name specified is not a locale file.

locale-file-name 指定语言环境文件不是语言环境文件。

The locale file that locale-file-name specified is not an GBase 8s GLS locale file, or it has been corrupted. Check that you are using the locale file that your GBase 8s product supplier provided. Refresh the file from the original installation file if it has been corrupted.

locale-file-name 指定的 local 文件不是一个 GBase 8s GLS locale 文件，或者它已损坏。检查您使用的是 GBase 8s 产品供应商提供的 local 文件。如果它已损坏，请从原始安装文件重新刷新该文件。

11- The locale object is inconsistent.

语言环境对象不一致。

The locale object is not consistent. For example, the same code set is not being used in each locale category. Contact your GBase 8s product supplier for assistance.

语言环境对象不一致。例如，没有在每个语言环境类别中使用相同的代码集。联系您的GBase 8s 产品供应商以获得帮助。

For any other errno value, contact your GBase 8s product supplier for assistance.

对于其它 errno 值，请联系 GBase 8s 产品供应商获取帮助。

-29034 Character code-set conversion error. Tokens: from-cs-num, to-cs-num,cftype, objtype, position.

The character code-set conversion failed while converting a character string from the code set that from-cs-num identifies to the code set that to-cs-num identifies.

将字符串 from-cs-num 标识的代码集转换为 to-cs-num 标识的代码集时，字符代码集转换失败。

cftype The conversion failure type.

转换失败类型。

from_cs_num The code-set number for the input code set. Check your GBase 8s product documentation for a description of the code set that this code-set number identifies.

输入代码集的代码集编号。检查 GBase 8s 产品文档，以获取此代码集编号标识的代码集的说明。

objtype The type of object that is being converted.

正在转换的对象类型。

position The ordinal position of the value that is being converted.

正在转换的值的序号位置。

to_cs_num The code-set number for the output code set. Check GBase 8s product documentation for a description of the code set that this code-set number identifies.

输出代码集的代码集编号。查看 GBbase 8s 产品文档，了解此代码集编号标识的代码集的说明。

The following are the possible cftype values:以下是可能的 cftype 值：* If cftype is "unmapped input char" (cpstring), the input character did not exist in the output code set, and the conversion table did not define a substitute output character for the input character. The cpstring value shows the input character string for a length of up to 4 bytes, starting with the codepoint that could not be converted. The binary value of the codepoint bytes is represented by cpstring as a hexadecimal string (for example, 'c1c3d1f0').

如果 cftype 是“unmap input char”(cpstring)，则输出代码集中不存在输入字符，并且转换表没有为输入字符定义替代输出字符。cpstring 值显示最长为 4 个字节的输入字符串，从无法转换的代码点开始。代码点字节的二进制值由 cpstring 表示为十六进制字符串(例如:‘c1c3d1f0’)。

This failure type has two possible causes:此故障类型有两个可能的原因：1. The character data that is being converted is bad. Correct the character data that is being converted.

正在转换的字符数据是错误的。更正正在转换的字符数据。

The code-set conversion table is incorrect or incomplete.

Contact your GBase 8s software distributor for assistance.

代码集转换表不正确或不完整。请与您的 GBase 8s 软件分发服务器联系以获得帮助。

* If cftype is "bad form," the input character string was badly formed with respect to the shift-out and shift-in codepoints that delimit the internal code sets that are contained within the code set that code-set number from_cs_num identifies.

如果 cftype 是“bad form”，则输入字符串的格式与 shift-out 和shift-in 代码点有关，这些代码点分隔了包含在代码集中的内部代码集from_cs_num 标识。

For this failure type, correct the form of character data that is being converted.

对此错误类型，更正正在转换的字符数据的格式。

* If cftype is "too long," the length of the output string was longer than the internal buffers that are allocated to hold the output string. If the objtype is "output," the output value was longer than the maximum length of a CHAR data type.

如果 cftype 为“too long”，输出字符串的长度超出了分配保存此输出字符串的内部缓冲区长度。如果 objtype 是"output"，则 output 值大于CHAR 数据类型的最大长度。

For this failure type, shorten the input character data that is being converted.

对此错误类型，缩短正在转换的字符数据的长度。

The following are the possible objtype values:objtype 可能是以下值：* If objtype is "input," an input value from the application,such as an SQL statement or an input host variable value, was being converted.

如果 objtype 是"input",则正在转换来自应用程序的输入值。例如 SQL语句或输入的主机变量值。

* If objtype is "output," an output value from the database, such as a field or expression from the select list of a SELECT statement, was being converted.

如果 objtype 是“output”，则正在转换数据库的输出值，例如 SELECT 语句的 SELECT 列表中的字段或表达式。

* If objtype is "sqlda," an sqlname field in the output SQLDA was being converted.

如果 objtype 为“sqlda”，则正在转换输出 SQLDA 中的 sqlname 字段。

* If objtype is "sqlca," a character field in the SQLCA was being converted.

如果 objtype 为“sqlca”，则正在转换输出 SQLDA 中的字符字段。

The following possible meanings of position depend on the value of objtype:以下可能的位置含义取决于 objtype 的值：* If objtype is "input" and position is 0, the text of the input SQL statement could not be converted.

如果 objtype 为“input”且位置为 0，则无法转换输入 SQL 语句的文本。

* If objtype is "input" and position is not 0, position refers to the ordinal position of the input host variable value that could not be converted. For example, 2 means that the value of the second input host variable could not be converted.

如果obj类型是“input”而位置不是 0，则位置是指无法转换的输入主机变量值的序号位置。例如，2 表示无法转换第二个输入主机变量的值。

* If objtype is "output" and position is any value, position is the ordinal position of the output value that could not be converted, such as the third value in the select list of a SELECT statement.

如果 objtype 是“output”，而位置是任意值，则位置是无法转换的输出值的序号位置，例如 SELECT 语句的 SELECT 列表中的第三个值。

* If objtype is "sqlda" and position is any value, position is the ordinal position of the sqlname field in the SQLDA that could not be converted.

如果 objtype 为“sqlda”且位置为任意值，则位置是 SQLDA 中 sqlname字段中无法转换的序号位置。

* If objtype is "sqlca," position names the specific SQLCA field that could not be converted: sqlerrp, sqlwarn, sqlerrmc, or sqlstate.

如果 objtype 为“sqlca”，则位置将指定无法转换的特定 SQLCA 字段：sqlerrp、sqlwarn、sqlerrmc 或 sqlstate。

-29035 An incompatible data type was received by the Gateway.

The received data type is not compatible with or supported by the Gateway.

(For GBase 8s Enterprise Gateway with DRDA, the application requestor does not support the data type that was received from the application server.)接收的数据类型与网关不兼容或不受网关支持。（对于带有 DRDA 的 GBase 8s Enterprise Gateway，应用程序请求者不支持从应用程序服务器接收的数据类型。）Some examples of unsupported data types are 1-byte integer and 16-byte float. These data types are not supported.

不支持的数据类型是 1 字节整数和 16 字节浮点数。不支持这些数据类型。

Do not retrieve data from the columns that have data types that the Gateway cannot support.

不要从具有 Gateway 无法支持的数据类型的列中检索数据。

-29036 Character codeset conversion file not found from, to, filename:from_cs_num, to_cs_num, filename.

filename The filename of the code-set conversion file that could not be found.

未找到的代码集转换文件的文件名。

from_cs_num The code-set number for the source code set.

源代码集的代码集编号。

to_cs_num The code-set number for the target code set.

目标代码及的代码集编号。

A code-set conversion table to convert from the code set that from_cs_num identifies to the code set that to_cs_num identifies was not found. Consult your GBase 8s product documentation to find descriptions for the code sets that these code-set numbers identify.

找不到 from_cs_num 标识的代码集转换为 to_cs_num 标识的代码集转换表。

查阅您的 GBase 8s 产品文档，查找这些代码集编号标识的代码集的说明。

If the appropriate directory (see next paragraph) does not contain the code-set conversion file named filename, this code-set conversion cannot be performed. Check your GBase 8s product documentation to make sure that the code sets that the client and server products use have been specified correctly (using environment variables or other mechanisms that are described in the documentation). Perhaps the code-set numbers have been incorrectly specified or are equivalent to other code-set numbers that are supported.

如果相应的目录（请参阅下一段）不包含名为 filename 的代码集转换文件，则无法执行此代码集转换。检查 GBase 8s 产品文档以确保已正确指定客户端和服务器产品使用的代码集（使用环境变量或文档中描述的其他机制）。可能未正确指定代码集编号或与支持的其他代码集编号等效。

If the code-set conversion table exists, verify that your product was installed correctly so that the conversion table file can be located.

Specifically, ensure that the GL_PATH environment variable is set or not set according to the installation instructions.

如果存在代码集转换表，请验证您的产品是否已正确安装，以便可以找到转换表文件。

具体来说，请确保根据安装说明设置或不设置 GL_PATH 环境变量。

* If GL_PATH is not set, verify that the conversion table file is in the $GBS_HOME/gls/cv directory.

如果未设置 GL_PATH，请验证转换表文件是否在 $GBS_HOME /gls/cv 目录中。

* If GL_PATH is set, verify that the conversion table file is in one of the directories that the GL_PATH environment variable specifies.

如果设置了 GL_PATH，请验证转换表文件是否位于 GL_PATH 环境变量指定的其中的目录中。

If the code-set conversion table does not exist, contact your GBase 8s software distributor for assistance in determining what code-set conversion tables are required for your configuration. If the required code-set conversion tables are available, place the tables in the appropriate directory.

如果代码集转换表不存在，请与 GBase 8s 软件分发服务商联系，以获取有关确定配置所需的代码集转换表的帮助。如果所需的代码集转换表可用，请将表放在适当的目录中。

-29037 There is no CCSID or GLS locale set for the FE OS locale localename.

The locale in question is returned as a token in SQLERRM.

有问题的语言环境在 SQLERRM 中作为标记返回。

Notify the Gateway administrator. The administrator can add an entry for the locale using the gwdba utility.

通知网关管理员。管理员可以使用 gwdba 实用程序为语言环境添加条目。

-29039 Cannot have more than one SQL statement in PREPARE/EXECUTE IMMEDIATE.

Modify the application so that it does not include more than one SQL statement in a PREPARE or EXECUTE IMMEDIATE statement.

修改应用程序，使其在 PREPARE 或 EXECUTE IMMEDIATE 语句中不包含多个SQL语句。

-29040 Cannot translate MATCHES pattern to LIKE pattern.

The Gateway does not support and cannot translate one or more characters in the MATCHES condition of your SQL statement. Try to rewrite the statement to use LIKE instead of MATCHES condition syntax or to not include MATCHES wildcard characters such as [ ] and ? or *.

Check also that you did not try to include a non-CHAR or VARCHAR column with MATCHES in the WHERE clause.

Gateway 不支持也不能在 SQL 语句的 MATCHES 条件中转换一个或多个字符。尝试重写语句以使用LIKE 而不是 MATCHES 条件语法或不包括 MATCHES 通配符，如 [ ] 和 ? 或 *。还要检查是否在WHERE 子句中的 MATCHES 中包含了非 CHAR 或 VARCHAR列。

-29042 Package info for RDB rdbname not found. Use gwdba to bind.

The Gateway package information for the target RDB is not found. It appears that the necessary Gateway packages on the RDB have not been bound yet. The real_RDB_name of the target RDB is returned as a token in SQLERRM.

找不到目标 RDB 的网关包信息。似乎 RDB 上的必要网关包尚未绑定。

目标 RDB 的 real_RDB_name 作为 SQLERRM 中的标记返回。

The end user should contact the DBA. If desirable, the DBA can use the gwdba utility to bind the needed Gateway packages on the target RDB.

最终用户应该联系 DBA。如果需要，DBA 可以使用 gwdba 实用程序绑定目标 RDB上所需的 Gateway 包。

-29043 No more section-type sections left. Rebind Gateway packages with more sections.

All the available sections in the current package at the application server have been used up. The current SQL statement is terminated.

应用程序服务器上当前包中的所有可用部分都已用完。当前的 SQL 语句已终止。

Notify the DBA. The DBA can rebind the Gateway packages with more sections on the target RDB using the gwdba utility.

通知 DBA。DBA 可以使用 gwdba 实用程序在目标 RDB 上使用更多部分重新绑定网关包。

-29044 Gateway internal logic error [diagnostic-error-string].

An internal logic error has been encountered. Rerun the application. If the error recurs, note all circumstances and contact GBase Technical Support.

遇到内部逻辑错误。重新运行该应用程序。

如果错误再次出现，请记录所有情况并联系 GBase 技术支持。

-29045 Gateway internal logic error [diagnostic-error-string]. Disconnected from AS.

An internal logic error has been encountered. This error will cause deallocation of conversation.

遇到内部逻辑错误。此错误将导致对话的重新分配。

Rerun the application. If the error recurs, note all circumstances and contact GBase Technical Support.

重新运行该应用程序。如果错误再次出现，请记录所有情况并联系 GBase 技术支持。

-29046 SNA buffer size (size) is not valid.

The send buffer that the GBase 8s connectivity network module allocated is less than the minimum DRDA required size, which is 512 bytes, or more than the maximum size, which is 32,767 bytes.

GBase 8s 连接网络模块分配的发送缓冲区小于最小 DRDA 所需的大小，即 512 字节，或大于 32，767 字节的最大大小。

Check the sqlhosts file on the Gateway computer. If the send buffer size is configurable through the sqlhosts file, make sure that the send buffer size is configured to be from 512 bytes to 32,767 bytes,inclusive.

检查 Gateway 计算机上的 sqlhosts 文件。如果可以通过 sqlhosts 文件配置发送缓冲区大小，请确保将发送缓冲区大小配置为 512 字节到 32,767 字节（包括端点）。

-29048 ISAM Error: error message.

An ISAM error occurred while reading data from a Gateway ISAM setup file that the Gateway xxxdba utility manages. The name of the ISAM setup file in question and the ISAM error number are returned in SQLERRM.

从 Gateway xxxdba 实用程序管理的 Gateway ISAM 安装文件读取数据时发生 ISAM 错误。

在 SQLERRM 中返回有问题的 ISAM 安装文件的名称和 ISAM 错误号。

If the Gateway was spawned by way of IPC-pipe mode, you must ensure that the GBS_HOME environment variable was set correctly before the application starts. Otherwise, notify the DBA:如果通过 IPC 管道模式生成网关，则必须确保在应用程序启动之前正确设置了 GBS_HOME 环境变量。否则，通知 DBA：* The DBA for GBase 8s Enterprise Gateway must ensure that the$GBS_HOME/egw/sysinfo directory exists with the proper permissions and that the ISAM setup files are present in that directory. If an GBase 8s Enterprise Gateway setup file is missing or corrupted, run egwdba to create it, or run the bcheckegw utility to repair it.

GBase 8s Enterprise Gateway 的 DBA 必须确保$GBS_HOME/egw/sysinfo 目录具有适当的权限，并且 ISAM 安装文件存在于该目录中。如果一个 GBase 8s Enterprise Gateway 安装文件丢失或损坏，请运行 egwdba 来创建它，或者运行 bcheckkegw 实用程序来修复它。

If GBase 8s Enterprise Gateway was spawned by way of network mode (that is, by the daemon egwd), the DBA also must ensure that the GBS_HOME environment variable was set correctly in the root login when the egwd daemon was started.

如果 GBase 8s Enterprise Gateway 是以网络模式(即由守护进程 egwd 生成)生成的，则DBA 还必须确保启动 egwd 守护进程时在 root 登录中正确设置 GBS_HOME 环境变量。

* The DBA for GBase 8s Gateway with DRDA must ensure that the$GBS_HOME/gw/sysinfo directory exists with the proper permissions and the ISAM setup files are present in that directory. If a Gateway setup file is missing or corrupted,run gwdba to create it, or run the bcheckgw utility to repair it.

带有 DRDA 的 GBase 8s Gateway 的 DBA 必须确保$GBS_HOME/gw/sysinfo 目录具有适当的权限，并且该目录中存在 ISAM设置文件。如果一个 Gateway 安装文件丢失或损坏，请运行 gwdba 来创建它，或者运行 bcheckgw 实用程序来修复它。

If the Gateway was spawned by way of network mode (that is, by the daemon gwd), the GBase 8s Gateway with DRDA DBA also must ensure that the GBS_HOME environment variable was set correctly in the root login when the gwd daemon was started.

如果 Gateway 是以网络模式(即由守护进程 egwd 生成)生成的，则 DBA 还必须确保启动egwd 守护进程时在 root 登录中正确设置 GBS_HOME 环境变量。

* The DBA for GBase 8s Enterprise Gateway Manager must ensure that the$GBS_HOME/egm/sysinfo directory exists with the proper permissions and the ISAM setup files are present in that directory. If a Gateway setup file is missing or corrupted,run egmdba to create it, or run the bcheckegm utility to repair it.

GBase 8s Enterprise Gateway Manager 的 DBA 必须确保$GBS_HOME/egm/sysinfo 目录具有适当的权限，并且该目录中存在 ISAM设置文件。如果一个Gateway安装文件丢失或损坏，请运行 egmdba 来创建它，或者运行 bcheckkegm 实用程序来修复它。

If the Gateway was spawned by way of network mode (that is, by the daemon egmd), the GBase 8s Enterprise Gateway Manager DBA also must ensure that the GBS_HOME environment variable was set correctly in the root login when the egmd daemon was started.

如果 Gateway 是以网络模式(即由守护进程 egwd 生成)生成的，则 DBA 还必须确保启动 egwd守护进程时在 root 登录中正确设置 GBS_HOME 环境变量。

-29049 Unable to locate/open Gateway setup file filename.

If you are using IPC-pipe mode to start the Gateway process, you should ensure that the GBS_HOME environment variable was set correctly before the application starts.

如果使用 IPC 管道模式启动 Gateway 进程，则必须确保在应用程序启动前，正确设置了 GBS_HOME 环境变量。

* For GBase 8s Enterprise Gateway with DRDA:对于 GBase 8s Enterprise Gateway with DRDA：An error occurred while locating or opening a Gateway ISAM setup file that the gwdba utility manages. The name of the ISAM setup file that is causing the error is returned in SQLERRM.

在查找或打开 Gwdba 实用程序管理的 Gateway ISAM 安装文件时发生了错误。

导致错误的 ISAM 安装文件的名称在 SQLERRM 中返回。

If you are using network connections, the GBase 8s Enterprise Gateway with DRDA database administrator must ensure that the named file exists in the$GBS_HOME/gw/sysinfo directory. If the file is missing, run gwdba to create it. The DBA also must ensure that the GBS_HOME environment variable was set correctly at the time that the gwd daemon was started.

如果使用网络连接，GBase 8s Enterprise Gateway with DRDA 数据库管理员必须确保命名文件存在于 $GBS_HOME/GW/sysinfo 目录中。如果文件丢失，请运行 gwdba 来创建它。DBA 还必须确保在启动 GWD 守护进程时正确设置了 GBS_HOME 环境变量。

* For GBase 8s Enterprise Gateway:对于 GBase 8s Enterprise Gateway：An error occurred while locating or opening an GBase 8s Enterprise Gateway ISAM setup file that the egwdba utility manages. The name of the ISAM setup file that is causing the error is returned in SQLERRM.

在查找或打开 egwdba 实用程序管理的 GBase 8s Enterprise Gateway ISAM 安装文件时发生了错误。导致在 SQLERRM 中返回了错误的 ISAM 安装文件的名称。

If you are using network connections, the GBase 8s Enterprise Gateway DBA must ensure that the named file exists in the$GBS_HOME/egw/sysinfo directory. If the file is missing, run egwdba to create it. The DBA also must ensure that the GBS_HOME environment variable was set correctly at the time that the egwd daemon was started.

如果使用网络连接，GBase 8s Enterprise Gateway DBA 必须确保命名文件存在于$GBS_HOME/EGW/sysinfo 目录中。如果文件丢失，请运行 egwdba 来创建它。DBA还必须确保在启动 egwd 守护进程时正确设置了 GBS_HOME 环境变量。

* For GBase 8s Enterprise Gateway Manager:对于 GBase 8s Enterprise Gateway Manager：An error occurred while locating or opening a Gateway ISAM setup file that the egmdba utility manages. The name of the ISAM setup file that is causing the error is returned in SQLERRM.

在查找或打开 egmdba 实用程序管理的 Gateway ISAM 安装文件时发生了错误。

导致在SQLERRM中返回了错误的 ISAM 安装文件的名称。

If you are using network connections, the GBase 8s Enterprise Gateway Manager database administrator must ensure that the named file exists in the "$GBS_HOME/egm/sysinfo" directory. If the file is missing, run "egmdba" to create it. The DBA also must ensure that the GBS_HOME environment variable was set correctly at the time that the "egmd" daemon was started.

如果使用网络连接，8s Enterprise Gateway Manager 数据库管理员必须确保命名文件存在于“$GBS_HOME/EGM/sysinfo”目录中。如果文件丢失，请运行“egmdba”来创建它。

DBA 还必须确保在启动“egmd”守护进程时正确设置了 GBS_HOME 环境变量。

-29050 Error accessing schema information(Orig-Msg[Sub=Sub-code,Ifx=Orig-code,Obj=Object-name])The Gateway encountered an error while accessing catalog information for the object Object-name. The Gateway sends this catalog information to the coordinating database server while processing a distributed query.

网关在访问对象名称的目录信息时遇到错误。网关在处理分布式查询时将此目录信息发送到协调数据库服务器。

Several errors that might occur during catalog access can cause this message. Orig-code is the error code for the underlying error, and Orig-Msg is the message token that is associated with that error code.

Sub-code is an GBase 8s internal code in hexadecimal that indicates which catalog access query failed and in which stage of query processing it failed. This diagnostic information field is meant for Technical Support.

在目录访问期间可能发生的几个错误从而产生此消息。原始代码是基础错误的错误代码，Orig-MSG 是与该错误代码相关联的消息标记。Sub-code 是十六进制格式的 GBase 8s内部代码，它指示哪个目录访问查询失败，以及查询处理的哪个阶段失败。此诊断信息字段用于技术支持。

Although the error message token might be truncated through programmatic access, the entire message is logged in the Gateway log file gw.log in the directory $GBS_HOME/gw/log.

尽管错误消息令牌可能通过编程访问被截断，但整个消息被记录在目录 $GBS_HOME/gw/log中的 Gateway 日志文件 gw.log 中。

-29051 Only single-site updates allowed in a transaction.

This Gateway does not support two-phase commit. If any remote server that the Gateway accesses is an update site in a transaction, that site must be the only update site in the transaction. All other sites,including GBase 8s sites, must be read only. Change the application to update only one remote site per transaction. (However, if the sites in a transaction are all read only, any number of sites can be updated in the same transaction).

此网关不支持两阶段提交。如果网关访问的任何远程服务器是事务中的更新站点，则该站点必须是事务中唯一的更新站点。所有其他站点，包括 GBase 8s 站点，都必须是只读的。将应用程序更改为每个事务只更新一个远程站点。(但是，如果事务中的站点都是只读的，则可以在同一事务中更新任意数量的站点)。

-29052 Gateway cannot access the remote data source named data-source-name.

The token data-source-name has been used in a four-part object name.

For example:data-source-name 已在 four-part 对名中使用。例如：data-source-name@gwservername:own1.tab1 In addition, the gwservername in the previous example has been used earlier in your application in association with a different data-source-name. For example, it might have been used with data-source-name2:此外，前面示例中的 gwserverame 已经在您的应用程序中与不同的数据源名称关联使用。

例如，它可能与数据源名称2一起使用：data-source-name2@gwservername:own2.tab2 Within a single application, until a CLOSE DATABASE statement executes,each gwservername can be used to access only one data-source-name.

在单个应用程序中，在执行关闭数据库语句之前，每个 gwserverame 只能访问一个数据源名称。

To access more than one data-source-name within a single application,you must start a separate Gateway daemon (with a unique gwservername)for each remote data source. Then change your application so that each unique gwservername in your application is always used in association with the same data-source-name. For example, the following statements consistently associate data-source-name dsn1 with gwservername gw1, and dsn2 with gw2:若要在单个应用程序中访问多个数据源名称，必须为每个远程数据源启动一个单独的 Gateway守护进程(具有唯一的 gwserverame)。然后更改应用程序，以便应用程序中的每个唯一gwserverame 始终与相同的数据源名称关联使用。例如，以下语句始终将数据源 dsn1 与gwserverame gw1 相关联，dsn2 与 gw2相关联：SELECT col5 FROM dsn1@gw1:own1.tab1 WHERE col1 > 100;SELECT col2 FROM dsn2@gw2:own2.tab2 WHERE col4< 10;SELECT a.col1, b.col2 FROM dsn1@gw1:own3.tab3 a, dsn2@gw2:own4.tab4 b WHERE a.col2 = b.col3;The token data-source-name in the error message has different meanings,depending on the Gateway product:错误消息中的 data-source-name 具有不同的含义，这取决于 Gateway 产品：* For GBase 8s Enterprise Gateway Manager, data-source-name refers to the ODBC data-source name.

对于 GBase 8s Enterprise Gateway Manager，data-source-name 是指 ODBC数据源名称。

* For GBase 8s Gateway with DRDA, data-source-name refers to the alias-RDB-name. Each Gateway instance can connect to only one RDB (application server).

对于 GBase 8s Gateway with DRDA，data-source-name 是指alias-RDB-name。一个 Gateway 实例只能连接一个 RDB（应用程序服务器）。

* For GBase 8s Enterprise Gateway, data-source-name refers to the EDA-Server-name. Each Gateway instance can connect to only one remote server.

对于 GBase 8s Enterprise Gateway，data-source-name 是指EDA-Server-name。一个 Gateway 实例只能连接一个远程服务器。

-29053 Collection missing in the reference to object Object.

Any distributed query that references an OS/400 object must specify the OS/400 collection or library to which the object belongs. The collection or library name should be specified in the owner field of the complete object name database@dbservername:owner.object. The collection or library name is required to get catalog information for the specified Object in a given collection or library.

任何引用 OS/400 对象的分布式查询都必须指定该对象所属的 OS/400 集合或库。

集合或库名应在完整对象名称数据库 @dbserverame:owner.object 的所有者字段中指定。集合或库名称是获取给定集合或库中指定对象的目录信息所必需的。

-29055 DDL statements are not allowed on a remote object.

In a distributed query, the Gateway does not allow data definition statements and the data access statements GRANT and REVOKE on remote objects (such as objects at DRDA application server sites).

Applications can use these statements only when they use the Gateway in direct mode.

在分布式查询中，Gateway 不允许数据定义语句和数据访问语句 GRANT 和 REVOKE远程对象(例如 DRDA 应用服务器站点上的对象)。只有在直接模式下使用网关时，应用程序才能使用这些语句。

-29056 Gateway cannot rollback savepoint (error-message-info).

An error occurred while a remote distributed update was in progress.

Because the Gateway cannot undo the effects of the partial update, the application must terminate the current transaction with a ROLLBACK WORK statement. Any other statement in the current transaction will fail with this error code. If the application issues a COMMIT WORK statement, a ROLLBACK WORK statement is executed internally, and this error code is returned.

在进行远程分布式更新时发生了错误。由于 Gateway 无法撤消部分更新的影响，因此应用程序必须使用 ROLLBACK WORK 语句终止当前事务。当前事务中的任何其他语句都将在此错误代码中失败。如果应用程序发出 COMMIT WORK 语句，将在内部执行 ROLLBACK WORK语句，并返回此错误代码。

The error-message-info field contains the sqlcode of the original error and an optional error messages string if the error originated at the target data source. The format of this message string is documented in the appropriate Gateway user manual. If the error-message-info field is empty, the savepoint rollback is the result of a processing error at the coordinating database server.

error-message-info 字段包含原始错误的 sqlcode，如果错误起源于目标数据源，则包含一个可选的错误消息字符串。此消息字符串的格式记录在适当的 Gateway 用户手册中。如果error-message-info 字段为空，则 savepoint 回滚是协调数据库服务器处理错误的结果。

-29057 Gateway does not support remote aliases (remote-object-name).

The Gateway does not support access to DB2 remote aliases in distributed queries. A remote alias is defined for an object that is not on the same server where the alias is defined.

Gateway 不支持访问分布式查询中的 DB2 远程别名。远程别名是为定义别名的服务器上的对象定义的。

Remote-object-name is the three-part object name (in the format LOCATION.OWNER.OBJECT) to which the remote alias refers.

Remote-object-name 是远程别名所引用的第三方对象名称(格式为LOCATION.OWNER.OBJECT)。

-29060 EDA error (EDA_Error).

The SQL statement failed because of an EDA error. EDA_Error describes the EDA error that the EDA client or server returned.

由于 EDA 错误，SQL 语句失败。EDA_Error 描述了 EDA 客户端或服务器返回的 EDA 错误。

The format of the EDA_Error field is as follows:EDA_Error 字段的格式如下所示：[EDA_Error_Code EDA_command] EDA_message_text* EDA_Error_Code is the EDA numeric error code.

EDA_Error_Code 是 EDA 编码错误代码。

* EDA_command is the EDA API/SQL command that is issuing the error.

EDA_command 是发出此错误的 EDA API/SQL 命令。

* EDA_message_text is the EDA message text that is associated with the error.

EDA_message_text 是与此错误相关联的 EDA 消息文本。

Look up the error in your EDA documentation from Information Builders,Inc. and correct the problem.

从 Information Builders,Inc.查找 EDA 文档中的错误，并纠正问题。

-29062 An EDA Client or Server prompt was received.

The EDA client or server has prompted the Gateway to respond to a message. For example, an EDA Remote Procedure might prompt the user for input. The Gateway does not support EDA operations that require responses to prompt messages.

EDA 客户端或服务器已提示网关响应消息。例如，ED A远程过程可能会提示用户输入。

网关不支持需要响应提示消息的 EDA 操作。

-29063 Output data description changed between prepare and execute.

The description of the output data for the query that was returned at prepare time is different than the description that was returned at execute time. The description of the output data that was returned at prepare time is derived from the cataloged information about the objects (for example, tables or remote procedures) in the query. This error usually occurs because the cataloged information about the object is out of date.

在准备时返回的查询的输出数据的描述与在执行时返回的描述不同。在准备时返回的输出数据的描述来自查询中有关对象(例如表或远程过程)的编目信息。此错误通常发生是因为有关对象的编目信息已过时。

If the object is not cataloged, or if it has changed since it was last cataloged, the object must be cataloged (or recataloged) with the EDASAF or EDA/SQL Metadata Manager tools. If GBase 8s-style system catalog tables are being used at the EDA/SQL Server, and the object is a table and not a remote procedure, the GBase 8s-style system catalog tables also must be repopulated, with the egwdba utility, after the EDA system catalog tables have been updated with EDASAF or the EDA/SQL Metadata Manager.

果对象没有编目，或者对象自上次编目以来发生了更改，则必须使用 EDASAF 或 EDA/SQL元数据管理器工具对象进行编目(或重述)。如果在 EDA/SQL Server 上使用GBase 8s 样式的系统目录表，并且该对象是表而不是远程过程，则在使用 EDASAF 或 EDA/SQL 元数据管理器更新 EDA 系统目录表之后，还必须使用 egwdba 实用程序重新填充 GBase 8s 样式的系统目录表。

-29064 Unknown EDA datatype received.

The output EDA data type that the Gateway received is an unknown EDA type. The Gateway might receive an unknown data type if it is connected to an EDA/SQL Server at a release level that the Gateway does is not support. If the Gateway does support this release level, this message indicates an internal error either for the EDA products that are being used or for the Gateway.

网关接收的输出 EDA 数据类型是未知的 EDA 类型。如果网关以网关不支持的发布级别连接到EDA/SQL Server，则网关可能会接收未知的数据类型。如果 Gateway 确实支持此发布级别，则此消息表示正在使用的 EDA 产品或网关的内部错误。

-29065 Input host variables not allowed in EXECUTE PROCEDURE.

You used a parameter marker for at least one of the input parameter values in the dynamic EXECUTE PROCEDURE statement that is being prepared. Parameter markers are not supported for input parameters in EXECUTE PROCEDURE statements that the Gateway processes. Rewrite your application to avoid the use of input host variables as input parameters to the EXECUTE PROCEDURE statement.

您在正在准备的动态 EXECUTE PROCEDURE 语句中为至少一个输入参数值使用了参数标记。

网关处理的 EXECUTE PROCEDURE 语句中的输入参数不支持参数标记。重写应用程序，避免使用输入主机变量作为 EXECUTE PROCEDURE 语句的输入参数。

-29066 Password required in .netrc entry for 'userid'.

The .netrc file contains an entry that maps from the current user ID(userid) to a new user ID that will be sent to the remote server or data source. In this case, the new user ID is different from the current user ID, but no password is specified to be sent with the new user ID to the remote server or data source. This error occurs because the Gateway has not authenticated the new user ID, and the remote server or data source cannot authenticate the new user ID without a password. Sending the new user ID without a password implies to the remote server or data source that the Gateway has authenticated the new user ID (which the Gateway has not done).

.netrc 文件包含一个从当前用户 ID(Userid)映射到将发送到远程服务器或数据源的新用户 ID 的条目。在这种情况下，新的用户 ID 与当前的用户 ID 不同，但是没有指定密码将新的用户 ID 发送到远程服务器或数据源。发生此错误是因为网关尚未验证新的用户 ID，而且远程服务器或数据源无法在没有密码的情况下对新用户 ID 进行身份验证。

在没有密码的情况下发送新的用户 ID 意味着网关已经对新的用户 ID 进行了身份验证(网关没有这样做)，这意味着网关已经对远程服务器或数据源进行了身份验证。

-29067 Could not access EDALINK.CFG file (reason).

The EDALINK.CFG file could not be accessed for the reason that is stated. When reason is of the form name: number, number indicates the operating-system error while accessing a file or directory with the specified name. Usually, the failure occurs because the EDALINK.CFG file is not in the Gateway $GBS_HOME/etc directory. The EDALINK.CFG file is an EDA/Link configuration file that is required to connect to an EDA/SQL Server. Consult your EDA/Link documentation to determine the contents of the file.

由于所述原因，无法访问 EDALINK.CFG 文件。当 reason 的格式为 :number时，number 表示访问具有指定名称的文件或目录时的操作系统错误。通常，发生故障是因为EDALINK.CFG 文件不在 Gateway $GBS_HOME/etc 目录中 .CFG 文件是连接到EDA/SQL Server 所需的 EDA/Link 配置文件。请查阅 EDA/Link 文档，以确定文件的内容。

-29068 A field value received from the EDA Server could not be decoded.

In the row that is being fetched, a field value could not be decoded and converted into an GBase 8s data value. Usually this situation occurs because the EDA/SQL Server could not convert the field value from its actual value in the underlying data source to its specified Master File Description (MFD) usage format. For example, if the usage format in the table MFD is I2 (integer value with a maximum field length of 2 characters), and the value of the field is 300, then the EDA/SQL Server cannot fit 300 into the specified 2-character field length.

在正在获取的行中，字段值无法解码并转换为 GBase 8s 数据值。通常发生这种情况是因为EDA/SQL Server 无法将字段值从基础数据源中的实际值转换为其指定的主文件描述(MFD)使用格式。例如，如果表 MFD 中的使用格式为 I2(最大字段长度为 2 个字符的整数值)，且字段的值为 300，则 EDA/SQL Server 无法将 300 容纳到指定的2个字符字段长度中。

In this case, the Gateway issues the error because the EDA/SQL Server has sent a sentinel value in place of the real field value. Check that the usage format field-length specifications in the MFD are long enough to hold the actual field values that your data contains. If this action does not solve the problem, contact GBase Technical Support for assistance in tracing the data that is received from the EDA/SQL Server.

在这种情况下，Gateway 发出错误，因为 EDA/SQL Server 发送了一个 sentinel 值而不是真实的字段值。检查 MFD 中的使用格式字段长度规格是否足够长，以保存数据所包含的实际字段值。如果此操作不能解决问题，请与 GBase 技术支持联系，以帮助跟踪从EDA/SQL Server 接收的数据。

-29070 Package isolation level does not match for alias_rdbname,isolation_level The application-to-package mapping entry for the given alias_rdbname and isolation_level points to a package whose isolation level is different than isolation_level.

给定 alias_rdbname 和 isolation_level 的 application-to-package 映射条目指向隔离级别与 isolation_level 不同的包。

Make sure that the application-to-package entry is valid and that isolation_level matches the isolation level in the gwbind file for the mapped package.

确保 application-to-package 条目是有效的，并且 isolation_level 符合映射包的gwbind 文件中的隔离级别。

-29071 Gateway cannot find package information for package RDBName.CollectionID.PackageID Gateway package information for the specified package RDBName.CollectionID.PackageID is not found. Perhaps the specified package has not been bound, or the package mapped in the application-to-package mapping is incorrect.

找不到指定包 RDBName.CollectionID.PackageID 的网关包信息。

可能未绑定指定的包，或者在应用程序到包映射中映射的包不正确。

Contact the database administrator (DBA). The DBA can use the gwdba utility to bind the specified package or to ensure that the package to which the application-to-package mapping entry points is valid.

联系数据库管理员（DBA）。 DBA 可以使用 gwdba 实用程序绑定指定的包，或者确保应用程序到包映射条目指向的包有效。

-29080 Target DBMS Error (message_token).

The target DBMS (Database Management System) to which the Gateway is connected has reported the error that is contained in message_token.

Refer to the documentation for the target DBMS to correct the problem.

网关所连接的目标 DBMS（数据库管理系统）已报告 message_token 中包含的错误。

请参阅目标DBMS的文档以更正问题。

The format for message_token is as follows:message_token 的格式如下：[DBMS_Error_Code Sqlstate DBMS_Product_id] DBMS_Error_Message DBMS_Error_Code is the error code of the target DBMS.

目标 DBMS 的错误代码。

Sqlstate is the SQLSTATE that is associated with the error. For a list of SQLSTATE codes, see your ODBC documentation.

与错误小相公的 SQLSTATE。有关 SQLSTATE 代码列表，请参阅您的 ODBC 文档。

DBMS_Error_Code is the error code of the target DBMS.

目标 DBMS 的错误代码。

DBMS_Product_id is the product ID of the target DBMS.

目标 DBMS 的产品 ID。

DBMS_Error_Message is the error message that the target DBMS generates.

This message is truncated if the entire sqlerrm text is longer than 71 bytes.

目标 DBMS 生成的错误消息。如果整个 sqlerrm 文本大于 71 字节，则该消息会截断。

DBMS_Product_id in message_token has the following format:消息令牌中的 DBMS_Product_id 具有以下格式：Product_Name:Product_Version Product_Name is up to the first five characters of the name of the target DBMS product as reported by the ODBC Driver for the product (specifically, the SQL_DBMS_NAME returned by the SQLGetInfo ODBC function).

Product_Name 最多为产品的 ODBC 驱动程序报告的目标 DBMS 产品名称的前五个字符（特别是 SQLGetInfo ODBC 函数返回的 SQL_DBMS_NAME）。

Product_Version is the first 10 characters of the version of the target DBMS product as reported by the ODBC Driver for the product(specifically, the SQL_DBMS_VER returned by the ODBC SQLGetInfo function).

Product_Version 是产品的 ODBC 驱动程序报告的目标 DBMS 产品版本的前 10 个字符（特别是 ODBC SQLGetInfo 函数返回的 SQL_DBMS_VER）。

Product_Version is a character string of the form nn.nn.nnnn, where the first two digits are the major version of the target DBMS, the next two digits are its minor version, and the last four digits are its release version (for example, 03.01.0000). An Oracle7 DBMS_Product_id might be Oracl:07.01.0000.

Product_Version 是 nn.nn.nnnn 格式的字符串，其中前两位数是目标 DBMS 的主版本，接下来的两位数是它的小版本，最后四位数是它的发版版本（例如：03.01.0000）。

Oracle7 DBMS_Product_id 可能是：07.01.0000。

If the connection attempt to the target DBMS was not completely successful, then DBMS_Product_id will be :00.00.0000.

如果连接到目标 DBMS 的尝试没有完全成功，那么 Driver_Prod_id 将是：00.00.0000。

-29081 ODBC Error (message_token).

An ODBC (Open Database Connectivity) component that the Gateway uses to access the target DBMS has reported the error that message_token contained. Refer to your ODBC documentation to correct the problem.

网关用于访问目标 DBMS 的 ODBC（开放式数据库连接）组件报告了 message_token 包含的错误。

请参阅 ODBC 文档以更正此问题。

The format for message_token is as follows:message_token的格式如下：[ODBC_Error_Code Sqlstate Driver_Prod_id] ODBC_Error_Message ODBC_Error_Code is the error code of the ODBC component. (It can be 0.)ODBC 组件的错误代码。（它可以是 0。）Sqlstate is the SQLSTATE that is associated with the error. For a list of SQLSTATE codes, see your ODBC documentation.

与错误相关的 SQLSTATE。对于 SQLSTATE 代码列表，请参阅您的 ODBC 文档。

Driver_Prod_id is the product ID of the ODBC driver that is being used.

是使用的 ODBC 驱动器的产品 ID。

ODBC_Error_Message is the error message that the ODBC component provided.

This message is truncated if the entire sqlerrm text is longer than 71 bytes.

ODBC 组件提供的错误消息。如果整个 sqlerrm 文本大于 71 字节，则该消息被截断。

Driver_Prod_id has the following format:Driver_Prod_id 具有以下格式：Driver_Name:Driver_Version Driver_Name is up to the first 5 characters of the name of the file that contains the ODBC Driver that is being used for the connection (specifically, the SQL_DRIVER_NAME that the SQLGetInfo ODBC function returned). If the connection has not yet been established, Driver_Name is blank.

Driver_Name 最多包含文件名的前5个字符，该文件包含用于连接的 ODBC 驱动程序（特别是 SQLGetInfo ODBC 函数返回的SQL_DRIVER_NAME）。如果尚未建立连接，则 Driver_Name 为空。

Driver_Version is the first 10 characters of the version of the ODBC Driver (specifically, the SQL_DRIVER_VER that the ODBC SQLGetInfo function returned). The Driver_Version is a character string of the form nn.nn.nnnn, where the first 2 digits are the major version of ODBC Driver, the next 2 digits are its minor version, and the last 4 digits are its release version (for example, 02.00.0000). An Oracle7 Driver_Prod_id might be libor:01.02.0006.

Driver_Version 是 ODBC 驱动程序版本的前 10 个字符（特别是 ODBC SQLGetInfo 函数返回的 SQL_DRIVER_VER）。

Driver_Version 是 nn.nn.nnnn 形式的字符串，其中前 2 位是ODBC 驱动程序的主要版本，接下来的 2 位是其次要版本，最后4 位是其发布版本（例如，02.00.0000）。

Oracle7 Driver_Prod_id 可能是 libor：01.02.0006。

If the connection attempt to the target DBMS was not completely successful, then Driver_Prod_id will be:00.00.0000.

如果连接到目标 DBMS 的尝试没有完全成功，那么 Driver_Prod_id 将是：00.00.0000。

-29082 Could not decode field value for field number field-number.

In the row that is being fetched, the field value for the field that is numbered field-number could not be decoded and converted into an GBase 8s data value. The field number is the ordinal position of the field that could not be converted in the select list. This situation reflects an error in the ODBC Driver for the target DBMS. The field value that could not be decoded is written to the Gateway log file along with the Driver Name and Version information.

在正在提取的行中，无法解码编号为 field-number 的字段的字段值，并将其转换为GBase 8s 数据值。字段编号是无法在选择列表中转换的字段的序号位置。这种情况反映了目标 DBMS 的 ODBC 驱动程序中的错误。无法解码的字段值与驱动程序名称和版本信息一起写入网关日志文件。

Contact your ODBC Driver supplier for a solution to the problem.

请与 ODBC 驱动程序供应商联系以获取问题的解决方案。

-29083 Compatible isolation level not supported by the data source.

If you received this error code when you executed a SET ISOLATION TO statement, the attempt to set the isolation level at the data source to a level compatible with the level in the statement has failed. The current isolation level in your application remains in effect.

如果在执行 SET ISOLATION TO 语句时收到此错误代码，则尝试将数据源中的隔离级别设置为与语句中的级别兼容的级别失败。应用程序中的当前隔离级别仍然有效。

If you receive this error code when you are executing a distributed SQL statement, the statement has failed because the data source does not support an isolation level that is compatible to the current isolation level of your application. The current isolation level in your application remains in effect.

如果在执行分布式 SQL 语句时收到此错误代码，则语句失败，因为数据源不支持与应用程序当前隔离级别兼容的隔离级别。应用程序中的当前隔离级别仍然有效。

A compatible isolation level is equal to or higher than the requested(or current, if a distributed statement) isolation level. When the requested (or current) isolation level is supported at the data source,GBase Enterprise Gateway Manager sets the data-source isolation level to that level. When the requested or current isolation level is not supported at the data source, if any higher levels are supported,GBase Enterprise Gateway Manager sets the data-source isolation level to the next available higher level.

兼容的隔离级别等于或高于请求的（或当前的，如果是分布式语句）隔离级别。

当数据源支持请求的（或当前）隔离级别时，GBase Enterprise Gateway Manager将数据源隔离级别设置为该级别。当数据源不支持请求或当前隔离级别时，如果支持任何更高级别，GBase Enterprise Gateway Manager 会将数据源隔离级别设置为下一个可用的更高级别。

If a lower isolation level that the data source supports is acceptable to your application, set the isolation level to that lower level. If you are accessing GBase 8s Enterprise Gateway Manager in direct access mode, use the GWDIRECTMIL environment variable to set the isolation level. If you are accessing GBase 8s Enterprise Gateway Manager in distributed-access mode, issue the SQL statement SET ISOLATION TO before you execute the distributed statement that accesses the Gateway.

如果应用程序可以接受数据源支持的较低隔离级别，请将隔离级别设置为较低级别。

如果以直接访问模式访问 GBase Enterprise Gateway Manager，请使用 GWDIRECTMIL环境变量设置隔离级别。如果要以分布式访问模式访问 GBase Enterprise Gateway Manager，请在执行访问网关的分布式语句之前发出 SQL 语句 SET ISOLATION TO。

-29084 Write access is not permitted to data source.

Your application is connected to a database server that supports transactions, but the data source that is being accessed in the statement does not support transactions. In this configuration,non-SELECT SQL statements (that is, actual or potential write operations) cannot be issued to the data source.

您的应用程序连接到支持事务的数据库服务器，但在语句中访问的数据源不支持事务。

在此配置中，无法向数据源发出非 SELECT SQL 语句（即实际或潜在的写入操作）。

In this case, the data source does not have the capability to match the transaction characteristics of the coordinating database server. A write operation cannot be guaranteed to be atomic on the data source(for example, a write to a file might start successfully but eventually fail because of insufficient disk space, leaving the file partially modified). Also, a write operation cannot be rolled back after it has been performed on the data source. For these reasons, write operations are not permitted when the coordinating database server supports transactions (that is, has a log), and the data source does not support transactions.

在这种情况下，数据源不具备匹配协调数据库服务器的事务特征的能力。写入操作不能保证在数据源上是原子的（例如，对文件的写入可能会成功启动但最终会因磁盘空间不足而失败，导致文件被部分修改）。此外，在对数据源执行写操作后，无法回滚它。由于这些原因，当协调数据库服务器支持事务（即具有日志）并且数据源不支持事务时，不允许写入操作。

If distributed write access to the data source is required, access the data source from a non-ANSI database without logging (or that has logging turned off).

如果需要对数据源进行分布式写访问，则从非 ANSI 数据库访问数据源而不进行日志记录（或者已关闭日志记录）。

-29085 Cursor hold is not supported by the data source.

The data source does not support cursors that are declared WITH HOLD.

Either the target DBMS does not support cursors that remain open after a commit operation, or the ODBC Driver does not use cursors with this property. Cursors that are declared WITH HOLD cannot be used at the data source.

数据源不支持声明为 WITH HOLD 的游标。目标 DBMS 不支持在提交操作后保持打开的游标，或者 ODBC 驱动程序不使用具有此属性的游标。不能在数据源中使用声明为 WITH HOLD 的游标。

-29087 Network Protocol Communication error.

GBase 8s-SQLCODE,native-protocol-rc: code An GBase 8s communications-related SQLCODE value and a hexadecimal native-network protocol return code are returned as a token in SQLERRM.

在 SQLERRM 中,GBase 8s 通信相关的 SQLCODE 值和十六进制本机网络协议返回码作为标记返回。

GBase 8s-SQLCODE is a platform-independent return code that the GBase 8s communications adaptation service generates. For a more specific description of the error, refer to the explanation of this SQLCODE value.

GBase 8s-SQLCODE 是 GBase 8s 通信适配服务生成的独立于平台的返回码。有关错误的更具体描述，请参阅此 SQLCODE 值的说明。

The native-protocol-rc value is a return code generated by the local network communications service that provides the protocol support on each particular platform. For an explanation of this return code, refer to the manufacturer's documentation for the protocol support that provides the underlying communications service.

native-protocol-rc 值是由本地网络通信服务生成的返回码，它在每个特定平台上提供协议支持。

有关此返回代码的说明，请参阅制造商的文档以获取提供底层通信服务的协议支持。

Ensure that the native-network communications service is installed correctly and that the target AS is configured correctly and is currently running.

请确保正确安装了本地网络通信服务，并且目标 AS 配置正确，并正确运行。

Example: If the communications protocol is TCP/IP, then the native-protocol-rc value is the return code that the local TCP/IP service generates.

示例：如果通信协议是 TCP/IP，则 native-protocol-rc 值是本地 TCP/IP 服务生成的返回码。

-29088 Communication buffer size (size) is not valid.

The send buffer that the GBase 8s connectivity network module allocated is less than the minimum DRDA-required size, which is 512 bytes, or more than the maximum size, which is 32,767 bytes.

GBase 8s 连接网络模块分配的发送缓冲区小于最小 DRDA 所需的大小，即 512 字节，或大于最大大小，即 32,767 字节。

If the network protocol being used is TCP/IP, an additional 6 bytes are required by the GBase 8s connectivity network module. This means the user specifiable block size minimum is 518 bytes and maximum is 32,773 bytes.

如果使用的网络协议是 TCP/IP，则 GBase 8s 连接网络模块需要额外的 6 个字节。

这意味着用户可指定的块大小最小为 518 字节，最大为 32,773 字节。

-29089 RDB password required when client user('') is not authenticated by Gateway.

This error occurs when the Gateway has not authenticated the client user ID(gwd is started with the '-b' option) and the application does not specify a password with the user ID.

当网关未验证客户端用户 ID（gwd 以'-b'选项启动）并且应用程序未指定具有用户 ID的密码时，会发生此错误。

Regardless of the security configuration of the remote database server, the Gateway expects to receive a password along with the user ID for the remote server when gwd is started with the '-b' option. In this case, the Gateway delegates user ID authentication to the remote server entirely.

无论远程数据库服务器的安全配置如何，当使用“-b”选项启动 gwd 时，Gateway希望接收密码以及远程服务器的用户 ID。在这种情况下，网关完全将用户 ID身份验证委派给远程服务器。

Make sure that the password is supplied to the Gateway.

确保密码已提供给网关。

-32100 MAC check failed.

Your session sensitivity label does not permit you to perform the operation on the OnLine/Secure object that you are accessing because it violates the MAC policy of GBase 8s OnLine/Secure. Log in at the appropriate sensitivity label and retry the operation.

您的会话敏感性标签不允许您对正在访问的 OnLine/Secure 对象执行操作，因为它违反了GBase 8s OnLine/Secure 的 MAC 策略。使用适当的敏感度标签登录并重试该操作。

-32101 DAC check failed.

Your session identity does not permit you to perform the operation on the OnLine/Secure object that you are accessing because it violates the DAC policy of OnLine/Secure. Log in with the appropriate identity, or obtain the necessary privileges and retry the operation.

您的会话标识不允许对正在访问的 OnLine/Secure 对象执行操作，因为它违反了OnLine/Secure 的 DAC 策略。使用适当的标识登录，或获取必要的权限并重试该操作。

-32102 Bad label range.

The range that is specified for an operation that involves labels is incorrect. The situation could arise either due to bad user input or an internal error.

为涉及标签的操作指定的范围是不正确的。这种情况可能是由于用户输入错误或内部错误造成的。

-32103 Label comparison operation failed.

This internal error could arise because the labels to be compared are incomparable or illegal, or the comparison operation was not legal for the label data type.

可能会出现此内部错误，因为要比较的标签是无法比较的或非法的，或者比较操作对于标签数据类型不合法。

-32104 Internal error; no table descriptor.

The table descriptor for the specified table was not found in the core dictionary.

在核心字典中找不到指定表的表描述符。

-32110 Illegal session level for dropping a database.

Your session sensitivity label must equal the sensitivity level of the database.

会话敏感度标签必须等于数据库的敏感度级别。

-32112 No DBA privilege for creating a view schema.

Contact the database administrator and request DBA privilege.

联系数据库管理员并请求 DBA 权限。

-32113 No DBA privilege for creating a table schema.

Contact the database administrator and request DBA privilege.

联系数据库管理员并请求 DBA 权限。

-32114 Cannot drop system catalog tables.

System catalog tables are dropped only when the database is dropped.

仅在删除数据库时才删除系统目录表。

-32115 Cannot change ownership of a table.

It is not legal to change the ownership of a table.

更改表的所有权是不合法的。

-32116 Illegal session level for altering a constraint.

Your session sensitivity level must equal the sensitivity level of the table.

您的会话敏感度级别必须等于表的敏感级别。

-32117 Illegal session level for creating an index.

Your session sensitivity level must equal the sensitivity level of the table.

您的会话敏感度级别必须等于表的敏感级别。

-32118 No Index privilege for creating an index.

Privilege is not granted for you to create an index on the table.

您权限表上创建索引。

-32119 Illegal session level for altering an index.

Your session sensitivity level must equal the sensitivity level of the table.

您的会话敏感度级别必须等于表的敏感级别。

-32120 No Resource privilege.

The action that you are performing requires Resource privilege on the database. Contact the database administrator to request the privilege.

您正在执行的操作需要数据库的资源特权。请与数据库管理员联系以请求权限。

-32121 Illegal session level for dropping an index.

Your session sensitivity level must equal the sensitivity level of the table.

您的会话敏感度级别必须等于表的敏感级别。

-32122 Cannot modify system catalog tables.

It is not legal to change attributes other than the next-extent size for the system catalog tables.

更改系统目录表的下一个扩展区大小以外的属性是不合法的。

-32123 Not the owner of the index.

Only the owner of the index can perform the operation that you are attempting.

只有索引的所有者才能执行您尝试的操作。

-32124 Cannot modify an index on a temporary table.

It is illegal to alter indexes on temporary tables.

更改临时表上的索引是非法的。

-32125 Current database number out of range.

This internal error indicates that the number of concurrent database opens exceeds the limit that OnLine/Secure sets.

此内部错误表示并发数据库打开的数量超过了 OnLine/Secure 设置的限制。

-32126 Illegal label tag.

The tag value that you supplied is unknown to the operating system.

您提供的标记值对于操作系统是未知的。

-32127 Illegal session level for dropping a table.

Your session sensitivity level must equal the sensitivity level of the table.

您的会话敏感度级别必须等于表的敏感级别。

-32128 No privilege for changing a SERIAL column.

You need Insert or Alter privilege on the table, or Update privilege on the SERIAL column, to change the serial value.

您需要具有对表的 Insert 或 Alter 权限，或者 SERIAL 列 Update 权限才能更改序列值。

-32129 Table was not opened at required label.

This message is applicable only for multilevel secure applications. You are attempting an operation on a table at a level higher than or incomparable to the level at which you opened the table. Open the table at the appropriate level.

此消息仅适用于多级安全应用程序。您正在尝试对表的操作，该操作的级别高于或无法打开表的级别。在适当的级别打开表。

-32130 There is no record at the specified level.

This message is applicable only for multilevel secure applications. No records exist at the level that you are accessing.

此消息仅适用于多级安全应用程序。您正在访问的级别不存在任何记录。

-32131 Internal heap error.

This message indicates an internal error.

此消息表示内部错误。

-32132 Cannot order by label.

Ordering by label is illegal because labels are not ordered linearly.

按标签排序是非法的，因为标签不是线性排序的。

-32133 Illegal session level for granting table-level privileges.

Your session sensitivity level must equal the sensitivity level of the table.

您的会话敏感度级别必须等于表的敏感级别。

-32134 Illegal session level for granting database-level privileges.

Your session sensitivity level must equal the sensitivity level of the database.

您的会话敏感度级别必须等于数据库的敏感级别。

-32135 Illegal session level for revoking table-level privileges.

Your session sensitivity level must equal the sensitivity level of the table.

您的会话敏感度级别必须等于表的敏感级别。

-32136 Illegal session level for revoking database-level privileges.

Your session sensitivity level must equal the sensitivity level of the database.

您的会话敏感度级别必须等于数据库的敏感级别。

-32137 No Alter privilege to modify a constraint.

Alter privilege on the table is required to modify a constraint.

需要更改表的特权才能修改约束。

-32138 Cannot set the initial SERIAL value.

This message is applicable only for multilevel secure applications. The initial serial value was not set at table creation.

此消息仅适用于多级安全应用程序。在创建表时未设置初始序列值。

-32139 No initial value has been set for the SERIAL column.

This message is applicable only for multilevel secure applications. No initial serial value exists for the sensitivity level that you are accessing. The initial serial value must be set at table creation if a SERIAL column exists in the table.

此消息仅适用于多级安全应用程序。您正在访问的敏感度级别不存在初始序列值。如果表中存在 SERIAL 列，则必须在创建表时设置初始序列值。

-32140 File handle and tabid are not consistent.

This message indicates an internal error. The table handle that is provided to an ISAM function is not a legal handle for the table whose tabid is also provided as a function argument.

此消息表示内部错误。提供给 ISAM 函数的表句柄不是表的合法句柄，其 tabid 也作为函数参数提供。

-32154 Label.map file must be owned by DBSSO.

Ensure that no other user has created a label.map file in the$LABELMAPDIR directory. Check that the sensitivity label of the label.map file is ixdbssoL.

确保没有其他用户在 $LABELMAPDIR 目录中创建了 label.map 文件。检查 label.map文件的敏感性标签是否为 ixdbssoL。

-32155 tbload is locked. Remove label.lok file.

An old label.map file is in use. Update the label.map file if necessary and remove the label.lok file to indicate your concurrence that the label.map file is indeed okay.

旧的 label.map 文件正在使用中。如有必要，更新 label.map 文件并删除 label.lok文件以表明您确认 label.map 文件确实没问题。

-32156 Cannot open file.

Cannot open the label.map file or the label.lok file. Check the existence, permission, and sensitivity level of these files.

无法打开 label.map 文件或 label.lok 文件。检查这些文件的存在、权限和敏感级别。

-32157 Invalid data in label.map file.

Check the integrity and legality of entries in the label.map file according to the current operating system.

根据当前操作系统检查 label.map 文件中条目的完整性和合法性。

-32158 The mapped tag does not exist in system.

The translation tag for a tag on tape that is provided in the label.map file does not exist on the operating system. Check the integrity and legality of entries in the label.map file according to the current operating system.

操作系统上不存在 label.map 文件中提供的磁带上标记的转换标记。根据当前操作系统检查label.map 文件中条目的完整性和合法性。

-32159 The mapping tag does not exist in system.

A tag that is supplied in the label.map file does not exist on tape.

Ensure that you are providing mapping only for those tags that are on the tape.

label.map 文件中提供的标记在磁带上不存在。确保您仅为磁带上的那些标记提供映射。

-32160 Unable to sort label.map file.

An error occurred during sorting of the label.map file. Check the integrity of the label.map file.

在对 label.map 文件进行排序时发生错误。检查 label.map 文件的完整性。

-32162 Label tag are not unique.

Tags and their translation tags should have strictly one-to-one mapping. Check the label.map file for duplicate tag mappings.

标签和它们的翻译标签应该有严格的一对一的映射。检查 label.map 文件中是否有重复的标记映射。

-32163 Label tag are not valid.

Only the tag representation of labels should be stored in the label.map file. Check the integrity and legality of the tags that are stored in the label.map file.

只有标签的标签表示应存储在 label.map 文件中。检查 label.map 文件中存储的标记的完整性和合法性。

-32164 Error creating session shared memory.

This message indicates an internal error. Check the operating-system error message. If the cause of the error is the size of the shared memory, you or your DBSA might have set a high value for SM_ROWSIZE or SM_TOTALROWS in the session configuration file.

此消息表示内部错误。检查操作系统错误消息。如果错误的原因是共享内存的大小，则您或您的 DBSA 可能已在会话配置文件中为 SM_ROWSIZE 或 SM_TOTALROWS 设置了较高的值。

-32165 Error attaching to session shared memory.

This message indicates an internal error. Check the operating-system error message for further information.

此消息表示内部错误。有关详细信息，请查看操作系统错误消息。

-32166 RSAM could not be found or executed by the current user.

Check $GBS_HOME,$ SQLEXEC settings. Ensure that you are in the group ix_users, ix_dbsa, or ix_dbsso. Check that the ISAM executable in$GBS_HOME/lib is executable by your session.

检查 $GBS\_HOME、$ SQLEXEC 设置。确保您位于组 ix_users、ix_dbsa 或 ix_dbsso中。

检查 $GBS_HOME/lib 中的 ISAM 可执行文件是否可由您的会话执行。

-32167 Table label inconsistent.

This message indicates an internal error.

该消息指示内部错误。

-32168 Database label inconsistent.

This message indicates an internal error.

该消息指示内部错误。

-32169 Cannot convert label between internal and external forms.

This message indicates an internal error. The operating system cannot map between the internal and external forms of the label. Check the external or tag representations that you provided.

该消息指示内部错误。操作系统无法在标签的内部和外部形式之间进行映射。

检查您提供的外部或标记表示。

-32181 The number of estimated security labels must be greater than 0.

Check for the parameter setting in the ONCONFIG file or the input to ON-Monitor.

检查 ONCONFIG 文件中的参数设置或 ON-Monitor 的输入。

-32182 Invalid number of estimated security labels label-name.

Check for the parameter setting in the ONCONFIG file or the input to DB-Monitor to make sure that the number of estimated security labels is always greater than 0.

检查 ONCONFIG 文件中的参数设置或 DB-Monitor 的输入，以确保估计的安全标签数始终大于 0。

-32183 LUB computation failed.

Check the legality of inputs to the LABELLUB() function.

检查 LABELLUB() 函数输入的合法性。

-32184 GLB computation failed.

Check the legality of the inputs to the LABELGLB() function.

检查 LABELGLB() 函数输入的合法性。

-32190 Cannot aggregate label column.

Check if label column is supplied to an aggregate function.

检查标签列是否提供给聚合函数。

-32191 Cannot alter table.

Alter table failed; check the additional ISAM error message for further information.

更改表失败；检查其它 ISAM 错误消息以获取更多信息。

-32193 Cannot create audit tblspace.

The OnLine/Secure database server cannot be initialized. Note all circumstances and contact GBase Technical Support.

无法初始化 OnLine/Secure 数据库服务器。请注意所有情况并联系 GBase 技术支持。

-32194 Cannot create reserved tblspace.

The OnLine/Secure database server cannot be initialized. Note all circumstances and contact GBase Technical Support for assistance.

无法初始化 OnLine/Secure 数据库服务器。请注意所有情况并联系 GBase 技术支持。

-32197 Not an OnLine/Secure tape.

Use a tape that an OnLine/Secure database server generated.

使用 OnLine/Secure 数据库服务器生成的磁带。

-32198 Not an OnLine/Secure root chunk.

Modify the ONCONFIG file to refer to a rootdbs that an OnLine/Secure database server created.

修改 ONCONFIG 文件以引用 OnLine/Secure 数据库服务器创建的 rootdbs。

-32400 A Table_option has already been altered.

You can change only one table option (locking mode, extent size) for each ALTER TABLE session. If you have changed one table option and want to change another, you must first exit the ALTER TABLE Menu and build the modified table. Select the Exit option, then the Build-new-table option. Then select the Table_options option on the ALTER TABLE Menu,and make your next modification to the table.

您只能为每个 ALTER TABLE 会话更改一个表选项（锁定模式，扩展区大小）。如果您更改了一个表选项并想要更改另一个表选项，则必须先退出 ALTER TABLE 菜单并构建修改后的表。选择 Exit 选项，然后选择 Build-new-table 选项。然后在 ALTER TABLE 菜单上选择 Table_options 选项，并对表进行下一次修改。

-32401 The initial extent size cannot be changed when altering a table.

The initial-extent size is set when the table is first created. The next-extent size can be altered, but the initial-extent size cannot. To change the size of the initial extent, you must unload the data from the table, drop the table, re-create the table with the CREATE TABLE statement, and reload the data into the table.

初始-extent 大小是在第一次创建表时设置的。下一个-extent 大小可以更改，但初始extent 大小不能更改。若要更改初始 extent 的大小，必须从表中卸载数据，删除表，用 CREATE TABLE 语句重新创建表，并将数据重新加载到表中。

-32402 The user cannot change the dbspace name when altering an existing table.

You have specified the location in which to table is to be stored. You have explicitly specified a dbspace or the dbspace of the database has already been used. When you attempted to alter a table, you tried to change the dbspace in which the table is stored. This action is illegal. You can specify the dbspace only when you create the table.

您已经指定了要存储表的位置。您已经显式地指定了 dbspace，或者已经使用了数据库的dbspace。尝试更改表时，尝试更改存储表的 dbspace。这种行为是非法的。只有在创建表时才能指定 dbspace。

Download any data in the existing table. Drop that table. Create a new table. Specify the dbspace that you want to use and upload the data into the new table.

请下载现有表中的任何数据。删除表。创建一个新表。指定要使用的 dbspace，并将数据上载到新表中。

-32403 Illegal serial length has been used.

This error occurs when the user creates or alters a table and creates or alters a column of type serial but has specified that the starting number is less than or equal to zero (illegal) or has entered in a nonnumeric value. Enter a number equal to or greater than 1 for the starting number.

当用户创建或更改表，创建或更改类型为串行的列，但指定起始数小于或等于零(非法)或输入非数字值时，就会发生此错误。为起始号码输入一个等于或大于 1 的数字。

-32404 Invalid delimiter. Do not use '\', hex digits, tab or space.

The delimiter that is specified for the LOAD or UNLOAD statement is illegal. You cannot use the new-line character, hexadecimal digits (0 to 9, A to F, a to f), the tab character, or a space as a delimiter.

Check the statement and change the delimiter symbol.

为 LOAD 或 UNLOAD 语句指定的分隔符是非法的。不能使用新行字符、十六进制数字(0 至 9、A 至 F、a 至 f)、制表符字符或空格作为分隔符。检查语句并更改分隔符号。

-32405 Incorrectly formed hexadecimal value.

The hexadecimal file that is used to load a BYTE value into the table has an illegal character or an incorrectly formed hexadecimal value.

Check the file for any anomalies and try running your statement again.

用于将 BYTE 值加载到表中的十六进制文件具有非法字符或格式错误的十六进制值。检查文件中是否有异常，并尝试再次运行您的语句。

-32406 Value must be greater than zero.

You specified an extent size less than or equal to zero when you created or altered a table. Specify an extent size greater than zero.

在创建或更改表时，您指定了小于或等于零的区段大小。指定大于零的区域大小。

-32407 Trigger not found.

You specified an invalid trigger name. Enter the name of an existing trigger or correct your spelling.

您指定了一个无效的触发器名。输入现有触发器的名称或更正拼写。

-32408 Cannot create MODE ANSI database without specifying transaction log pathname.

You tried to create an ANSI-compliant database on GBase 8s SE but did not specify a pathname for the mandatory unbuffered transaction logging. Select the Mode_ansi option of DB-Access again, or revise your CREATE DATABASE statement and enter the full log pathname.

您尝试在 GBase 8s SE 上创建符合 ANSI 的数据库，但没有为强制的非缓冲事务日志指定路径名。再次选择 DB-Access 的 Mode_Ansi 选项，或者修改 CREATE DATABASE 语句并输入完整的日志路径名。

-32409 Data is unavailable, cannot open database sysmaster.

DB-Access cannot open the sysmaster database, from which you have requested information. Check that the sysmaster database was built properly and read the error log for the cause of the failure.

DB-Access 无法打开您请求信息的sysmaster 数据库。检查 sysmaster 数据库是否已正确构建，并读取错误日志以了解故障原因。

-32410 Syntax not supported by DB-Access.

DB-Access does not support the AS, WITH CURRENT TRANSACTION, or USER clause of the CONNECT statement, although the database server supports it. Use proper SQL statement syntax when you run your CONNECT statement in DB-Access.

DB-Access 不支持 CONNECT 语句的 AS、WITH CURRENT TRANSACTION 或 USER 子句，尽管数据库服务器支持它。在 DB-Access 中运行 CONNECT 语句时，请使用适当的 SQL 语句语法。

-32411 An Alter Table Option has already been altered.

You attempted to perform an ALTER TABLE option on a table option that you previously altered. You cannot alter a table option more than once.

您试图对以前更改的表选项执行 ALTER TABLE 选项。不能多次更改表选项。

-32412 USING clause unsupported. DB-Access will prompt you for a password.

DB-Access does not support the USING password clause in a CONNECT ...

USER statement when it violates security. For example, do not type a password on the screen where it can be seen or include it in a command file that someone other than the user can read. To maintain security,DB-Access prompts you to enter the password on the screen and uses echo suppression to hide it from view.

DB-Access 不支持连接中的“使用密码”子句.语句，当它违反安全性时。例如，不要在屏幕上键入可以看到密码的密码，也不要将密码包含在用户以外的其他人可以读取的命令文件中。为了维护安全性，DB-Access 提示您在屏幕上输入密码，并使用回波信号抑制将其隐藏在视图中。

-32500 User does not have discrete privilege to change session levels.

You must obtain the PRIV_CANSETLEVEL discrete privilege from the DBSSO before the start of a session in which you use the SET SESSION LEVEL statement.

必须在使用 SET SESSION LEVEL 语句的会话开始之前从 DBSSO 获取 PRIV_CANSETLEVEL离散特权。

-32501 Login session level not dominating the new session level.

You must log in at a session sensitivity level that dominates the session level that you specify.

您必须在主导指定的会话级别的会话敏感级别登录。

-32502 New session level not dominating the database level.

You cannot access the database at the new session sensitivity level.

Use a different level that dominates the database.

不能在新会话敏感级别访问数据库。使用主导数据库的不同级别。

-32503 User tables should be closed to change session attribute.

Close all tables and relinquish all cursors that remain open before you attempt to change session sensitivity levels.

在尝试更改会话敏感性级别之前，关闭所有表并放弃所有仍处于打开状态的游标。

-32504 Operations on remote objects are not allowed after session level set.

You cannot access objects in remote databases when your current session sensitivity level differs from that of your login session. Return to the sensitivity level of your login session to access remote data.

当当前会话敏感性级别与登录会话不同时，无法访问远程数据库中的对象。返回到登录会话的灵敏度级别以访问远程数据。

-32505 Cannot set session level.

For more information, refer to the accompanying error message.

有关更多信息，请参阅所附的错误消息。

-32506 Bad session label format.

The argument to the SET SESSION LEVEL statement was not a valid sensitivity label.

SET SESSION LEVEL 语句的参数不是有效的敏感度标签。

-32507 Cannot set session authorization.

You must be a DBA to change the session user unless you are changing to yourself.

您必须是一个 DBA 才能更改会话用户，除非您要更改为自己。

-32508 Statement is invalid within a transaction.

You attempted to execute a SET SESSION AUTHORIZATION, SET ROLE, or SET TRANSACTION statement from within an active transaction.

您试图在活动事务内执行SET会话授权、SET角色或SET TRANSACTION语句。

Issue the SET statement at the beginning of the transaction, before a DML statement, such as SELECT or INSERT, makes the transaction active. Otherwise,roll back or commit the transaction before you issue the SET statement.

在事务开始时，在 DML 语句(例如 SELECT 或 INSERT )使事务处于活动状态之前，发出SET语句。否则，在发出 SET 语句之前，回滚或提交事务。

-32509 Bad session authorization format.

The user name that is supplied as an argument to the SET SESSION AUTHORIZATION statement is invalid. Supply the user ID of a valid user.

作为参数提供给 SET SESSION AUTHORIZATION 语句的用户名无效。提供有效用户的用户ID。

-32510 User does not have discrete privilege to change session authorization.

You must obtain the PRIV_CANSETIDENTITY discrete privilege from the DBSSO before the start of a session in which you use the SET SESSION AUTHORIZATION statement.

必须在使用 SET SESSION AUTHORIZATION 语句的会话开始之前从 DBSSO 获取PRIV_CANSETIDENTITY 离散特权。

-32513 Cannot rename table or column.

Renaming of table or column failed. For more information, refer to the ISAM error message.

重命名表或列失败。有关详细信息，请参阅ISAM错误消息。

-32514 Session level is different from the level of the database object.

Your session sensitivity label does not permit you to perform the operation on the OnLine/Secure object that you are accessing because it violates the MAC policy of OnLine/Secure. Log in at the appropriate sensitivity label and retry the operation.

会话敏感性标签不允许您对要访问的联机/安全对象执行操作，因为它违反了联机/安全的MAC 策略。在适当的灵敏度标签上登录，然后重试操作。

-32520 Cannot create SL map tblspace.

This message indicates an internal error.

此消息表示内部错误。

-32521 Cannot create IL map tblspace.

This message indicates an internal error.

此消息表示内部错误。

-32522 Cannot create Datalo translation.

This message indicates an internal error.

此消息表示内部错误。

-32523 Cannot create Datahi translation.

This message indicates an internal error.

此消息表示内部错误。

-32524 Cannot create ixdataH translation.

This message indicates an internal error.

此消息表示内部错误。

-32525 Cannot create saved translations.

This message indicates an internal error.

此消息表示内部错误。

-32526 Saved and stored tags disagree.

This message indicates an internal error.

此消息表示内部错误。

-32528 Tag not found.

This message indicates an internal error.

此消息表示内部错误。

-32529 Cannot create ixdbsaL translation.

This message indicates an internal error.

此消息表示内部错误。

-32532 Illegal data type for VARIANCE or STDEV.

You cannot use the VARIANCE or STDEV function on string or DATETIME data types. Review the use of these functions.

不能对字符串或 DATETIME 数据类型使用 VARIANCE 或 STDEV 函数。检查这些功能的使用情况。

-32766 Unknown error message number.

The software product cannot find the error message text files. Either the GBS_HOME or DBLANG environment variable is set incorrectly.

软件产品找不到错误信息文本文件。GBS_HOME 或 DBLANG 环境变量设置错误。

-32792 The onutil EBR block command completed successfully.

The database server has been blocked successfully.

数据库服务器已被成功阻止。

You need to unblock the database server before normal processing can continue.

在继续正常处理之前，需要解除对数据库服务器的阻塞。

-32793 The onutil EBR unblock command completed successfully.

The database server has been unblocked successfully.

数据库服务器已成功解除阻塞。

No action is required.

不需要任何。

-33000 The keyword is a reserved ANSI keyword.

This message is a warning. If you want your code to be ANSI compliant,do not use the keyword that is shown as a variable name. Check the GBase 8s Guide to SQL: Syntax for alternative syntax.

这条信息是一种警告。如果希望代码符合 ANSI，请不要使用显示为变量名称的关键字。

查看 GBase 8s SQL 指南：语法，了解其他语法。

-33001 Environment variable variable-name has invalid value.

Reset the specified environment variable to a legal value and try again. See the GBase 8s Guide to SQL: Reference.

将指定的环境变量重置为法定值，然后重试。查看 GBase 8s SQL 指南：语法。

-33002 Syntax error in the ESQL INCLUDE statement.

The preprocessor cannot interpret this INCLUDE statement. Refer to your embedded-language manual for the correct syntax of the INCLUDE statement.

预处理器无法解释这个包含语句。有关 INCLUDE 语句的正确语法，请参阅嵌入式语言手册。

-33003 Bad label format.

The label on the current statement is incorrect in form. Refer to the embedded-language manual for accepted label formats.

当前语句上的标签在形式上不正确。关于可接受的标签格式，请参阅嵌入式语言手册。

-33004 Option option-name does not exist or has bad format.

This embedded-language product does not support the specified option from the preprocessor/compiler command line. Check that it is spelled as you intended. Refer to the embedded-language manual for supported options.

此嵌入式语言产品不支持预处理器/编译器命令行中指定的选项。检查它是否按您的意思拼写。有关支持的选项，请参阅嵌入式语言手册。

-33005 Incomplete string.

A character string is not correctly terminated according to the rules of the host language. For example, it might be missing an end quote,not have a continuation character, and so on. The preprocessor might not recognize the error until a number of source lines beyond the line where you intended the string to end.

根据主机语言的规则，字符串不能正确终止。例如，它可能缺少一个尾引号，没有连续字符，等等。预处理器可能无法识别错误，直到在您希望字符串结束的行之外有许多源行。

-33006 Type of variable-name is not appropriate for this use.

You cannot use the specified variable in the context of this statement.

Check that you specified the variable you intended and that you declared it with the proper type. Then refer to the embedded-language manual for variable usage in this type of statement.

不能在此语句的上下文中使用指定的变量。检查您是否指定了您想要的变量，并以正确的类型声明了它。然后，在这种类型的语句中，请参考嵌入式语言手册中的变量使用情况。

-33007 '$' assumed before variable-name.

The preprocessor has assumed that you intend the symbol variable-name in this statement as a host variable. (A host variable is normally indicated with '$' or ':' preceding it.) Check that you did intend this meaning.

预处理器假设您打算将此语句中的符号变量名作为宿主变量。(主机变量通常用‘$’或‘：’在它前面表示。)检查一下你是否有意要表达这个意思。

-33008 Record component component-name was not declared.

This statement uses the symbol component-name as if it were the name of a component of a record, but it was not declared as a component of the record name with which it is used. Check the spelling of both the component and the record name.

此语句使用符号组件-名称，就好像它是记录组件的名称一样，但它没有声明为与其一起使用的记录名称的组件。检查组件和记录名称的拼写。

-33009 The component name component-name has already been used.

The record component was declared twice in the same record/structure.

Check the spelling of component names and the syntax of the declaration.

在同一个记录/结构中，记录组件被声明了两次。检查组件名称的拼写和声明的语法。

-33010 Internal error: Preprocessor states corrupted.

Correct all other processing errors. If the error recurs, note all circumstances and contact GBase Technical Support.

纠正所有其他处理错误。如果错误再次发生，请注意所有情况，并与 GBase 技术支持部门联系。

-33011 Current declaration of variable-name hides previous declaration.

This message is a warning from the preprocessor. The specified variable was declared more than once in the current scope. Compilation continues using this latest declaration to the end of the current scope. If you did not intend to redeclare the indicated variable, check the spelling of variable names and the syntax of declarations. In GBase 8s ESQL/C,this warning can also be issued if the variable is used as function parameter. In this case, use the PARAMETER clause.

此消息是来自预处理器的警告。指定的变量在当前作用域中多次声明。编译将继续使用最新的声明，直到当前作用域结束为止。如果不打算重新声明指定的变量，请检查变量名的拼写和声明的语法。在 GBase 8s ESQL/C 中，如果变量用作函数参数，也可以发出此警告。在这种情况下，使用参数子句。

-33012 Number of digits must be 1 to 32.

You specified a precision or scale for a DECIMAL value that is out of range. A DECIMAL variable must have from 1 to 32 digits. Check the punctuation of the declarations in this statement.

您为超出范围的十进制值指定了精度或比例。十进制变量必须有 1 到 32 位数字。检查此语句中声明的标点符号。

-33013 END DECLARE SECTION with no BEGIN.

The preprocessor has found this EXEC SQL END DECLARE SECTION statement but has not seen a preceding EXEC SQL BEGIN DECLARE SECTION. Possibly it was omitted or not recognized due to another error. Check that each BEGIN DECLARE is paired with an END DECLARE.

预处理器已经找到了这个 EXEC SQL END DECLARE SECTION 语句，但还没有在前面看到一个 EXEC SQL BEGIN DECLARE SECTION。可能由于另一个错误而被省略或无法识别。检查每个开始声明是否与结束声明配对。

-33014 Illegal use of record/structure variable-name.

The indicated record was used where only a simple variable can be accepted. Review the declaration of variable-name and check that it is the variable you intended to use (possibly you need to qualify it with a component name). Refer to the embedded-language manual for the requirements of this statement.

在只能接受一个简单变量的情况下，使用了指定的记录。检查变量名称的声明，并检查它是否是您打算使用的变量（可能需要用组件名称限定它）。有关本声明的要求，请参阅嵌入式语言手册。

-33015 Input file name has invalid suffix suffix-text.

The name of the input file that is submitted to the preprocessor must have the correct suffix. Check the command syntax and rename the file if necessary. The following file suffixes are required:提交给预处理器的输入文件的名称必须具有正确的后缀。检查命令语法，必要时重命名文件。需要下列文件后缀：* .ec for GBase 8s ESQL/C* .eco for GBase 8s ESQL/COBOL* .ef for GBase 8s ESQL/FORTRAN-33016 Macro definition for macro-name is incomplete.

This preprocessor macro definition statement does not have the ESQL statement terminator. Add a semicolon(;) to the end of the statement.

此预处理器宏定义语句没有 ESQL 语句终止符。在语句末尾添加分号(；)。

-33017 Incomplete statement.

The preprocessor cannot recognize the end of the current statement.

Check the syntax of this and preceding lines. Look for omitted ending semicolons, omitted quote marks, or omitted end-of-comment symbols.

预处理器无法识别当前语句的结尾。检查此行和前面行的语法。查找省略的结束分号、省略的引号或省略的注释结束符号。

-33018 Indicator variables are not allowed in this clause.

This statement includes a specification of a host variable with an indicator variable, but no indicator variable is allowed in this context. Review each use of an indicator variable and remove the unnecessary ones.

此语句包括带有指示符变量的主机变量的规范，但在此上下文中不允许指示变量。检查指标变量的每次使用情况，并删除不必要的变量。

-33019 Label is too long.

This statement specifies a label that is longer than this embedded language allows. Check the spelling and punctuation of the statement.

Refer to the embedded-language manual for proper formation of label names.

此语句指定的标签长度超过此嵌入式语言所允许的长度。检查语句的拼写和标点符号。请参阅嵌入式语言手册，以正确地形成标签名称。

-33020 Line is too long.

This line is too long either for the host language or to fit into the internal buffers of the preprocessor. Refer to the embedded-language manual and to the host-language manual for rules on continuing long lines.

对于主机语言来说，这一行太长了，或者无法适应预处理器的内部缓冲区。关于连续长行的规则，请参阅嵌入式语言手册和主机语言手册。

-33021 The value of macro macro-name is too long.

The specified value for the macro is too long to fit in the internal buffer. Shorten the statement and try again.

宏的指定值太长，无法适应内部缓冲区。缩短语句，然后再试一次。

-33022 Include path name too long.

The pathname in this INCLUDE statement is too long to fit in the internal buffers. Check the punctuation of the statement; possibly an end-quote has been omitted. If not, you will have to find a way to specify the included file with a shorter pathname. Refer to the embedded-language manual for the rules of the preprocessor on searching for included files.

这个 INCLUDE 语句中的路径名太长，无法适应内部缓冲区。检查语句的标点符号；可能省略了一个尾引号。如果没有，您将必须找到一种方法来指定包含的文件的路径名更短。

有关预处理器搜索包含的文件的规则，请参阅嵌入式语言手册。

-33023 Quoted string too long for SQL.

The quoted string is too long to fit in the internal buffers. Check the statement for a missing end quote.

引用的字符串太长，无法容纳内部缓冲区。检查语句中缺少的结尾引号。

-33024 Macro name expected.

The macro name of the macro statement is missing. Specify the name and try again.

宏语句的宏名称丢失。指定名称，然后重试。

-33025 The name '' is too long.

The specified SQL identifier is too long. The maximum length for identifiers depends on the database server.

指定的 SQL 标识符太长。标识符的最大长度取决于数据库服务器。

Check the punctuation of the statement and the spelling of identifier. If the spelling and punctuation are as you intended, you need to change the declaration to use a shorter identifier.

检查语句的标点符号和标识符的拼写。如果拼写和标点符号符合您的要求，则需要更改声明以使用更短的标识符。

-33026 Blocks cannot be nested more than n levels.

The preprocessor limits the number of nested levels to the specified value. Review the program structure preceding this point; the punctuation or keywords that close a block might have been omitted or might not have been recognized due to an earlier error. If all is as you intended it, you will have to reorganize the code to use fewer nested blocks.

预处理器将嵌套级别的数量限制为指定的值。检查这一点之前的程序结构；关闭 chunk的标点符号或关键字可能被省略，或者由于早期的错误而无法识别。如果一切都如您所愿，您将不得不重新组织代码以使用更少的嵌套 chunk 。

-33027 Record nesting too deep. Maximum is n.

The preprocessor limits the number of levels to which records (data structures) can be nested. Work backward from this point and review the declaration of records. Possibly the punctuation or keywords that close a record have been omitted or have gone unrecognized due to an earlier error. If all is as you intended it, you will have to simplify the data structure.

预处理器限制可以嵌套记录（数据结构）的级别数。从这一点向后工作，检查记录的声明。可能关闭记录的标点符号或关键字已被省略或由于先前的错误而无法识别。如果一切都如您所愿，您将不得不简化数据结构。

-33028 Invalid compiler-name compiler type compiler-type-name.

The compiler type must be specified as a command-line option to this preprocessor. Refer to the embedded-language manual.

编译器类型必须指定为此预处理器的命令行选项。请参阅嵌入式语言手册。

-33029 No input file given.

No input file is named on the command line.

命令行上没有命名输入文件。

-33030 Cannot have a insert statement on a SCROLL cursor.

This DECLARE statement specifies the SCROLL keyword, but it goes on to specify an INSERT statement. Insert cursors cannot use the SCROLL keyword.

这个 DECLARE 语句指定 SCROLL 关键字，但是它继续指定 INSERT 语句。插入游标不能使用滚动关键字。

-33031 Statement label is not allowed in this statement.

This message is a warning only. You used a label on a statement that does not generate any real code in the output file. Refer to the embedded-language manual for the correct use of labels.

此消息仅为警告。在不生成输出文件中的任何真正代码的语句上使用了一个标签。要正确使用标签，请参阅嵌入式语言手册。

-33032 WITH NO LOG can only be specified for TEMP tables.

You used the WITH NO LOG option in the wrong context. Use it only when you create a TEMP table and you wish to exclude transaction log operations on it. See the GBase 8s Guide to SQL: Syntax for the SQL syntax and proper usage of the WITH NO LOG option.

您在错误的上下文中使用了无日志选项。仅在创建临时表并希望排除其上的事务日志操作时才使用它。请参阅 GBase 8s SQL 指南：语法中的 SQL 语法和 WITH NO LOG 选项的正确用法。

-33033 The field field-name is a GBase 8s extension to XPG3 X/Open standard.

This message is a warning only. You used the -xopen option, asking that the source file be checked for compliance with the XPG3 X/Open standard. The ITYPE, IDATA and ILENGTH field names are GBase 8s extensions to the standard.

此消息仅为警告。您使用了 -xopen 选项，要求检查源文件是否符合 XPG3 X/Open 标准。ITYPE、IDATA 和 ILENGTH 字段名是该标准的 GBase 8s 扩展。

-33034 POWER cursors not available.

POWER cursors are not supported. Refer to your embedded-language manual.

不支持 POWER 游标。请参阅您的嵌入式语言手册。

-33035 A qualifier has not been specified.

You attempted to use a DATETIME qualifier, but you did not specify a specific range of acceptable values for that qualifier. Define the ranges that you will use to qualify the DATETIME qualifier. The DATETIME qualifier must have a beginning and ending range (for instance, year to month, day to hour, and so on).

尝试使用 DATETIME 限定符，但没有为该限定符指定特定的可接受值范围。定义用于限定DATETIME 限定符的范围。 DATETIME 限定符必须有一个开始和结束范围（例如，年到月、天到小时，等等)。

-33036 This line does not conform to ANSI X3.135-1989.

This message is a warning only. You used the -ansi option, asking that the source file be checked for compliance with the current ANSI standard. This statement uses a GBase 8s extension to the ANSI standard.

此消息仅为警告。您使用了 -ansi 选项，要求检查源文件是否符合当前的 ANSI 标准。

此语句使用 ANSI 标准的 GBase 8s 扩展。

-33037 Name is not a component of record record-name.

Name is used as if it were a member of the record record-name, but no member of that name exists. Check the spelling of the two names, and review the declaration of record-name.

名称被用作记录名的成员，但不存在该名称的成员。检查两个名称的拼写，并检查记录名称的声明。

-33038 This statement does not conform to the X/Open standard.

This message is a warning only. You used the -xopen option, asking that the source file be checked for compliance with the XPG4 X/Open standard.

此消息仅为警告。您使用了 -xopen 选项，要求检查源文件是否符合 XPG4 X/Open 标准。

-33039 Updates are not allowed in singleton select.

You have an UPDATE statement in combination with a SELECT statement that returns only one row. The UPDATE statement requires a cursor that has been declared FOR UPDATE. See the DECLARE, SELECT, and UPDATE statements in the GBase 8s Guide to SQL: Syntax for more information about cursors.

您有一个 UPDATE 语句和一个只返回一行的 SELECT 语句。UPDATE 语句需要已声明为UPDATE 的游标。有关游标的更多信息，请参见 GBase 8s SQL 指南：语法中的DECLARE、SELECT 和 UPDATE 语句。

-33040 Object hostvar was not declared.

The host variable hostvar is either not declared, or it is misspelled.

If hostvar is not declared as a host variable, declare it. Otherwise,correct the misspelling.

主机变量 hostvar 要么未声明，要么拼写错误。如果 hostvar 未声明为主机变量，则声明它。否则，纠正拼写错误。

-33041 Cannot open output file outfile.

The preprocessor cannot open outfile because not enough disk space is available, or you do not have file-system permission to open the file.

If insufficient disk space is available, delete files or select another disk to make space available in the file system. If you do not have file-system permission to open outfile, specify another directory or login with the required permission.

由于可用磁盘空间不足，或者您没有打开文件的文件系统权限，预处理器无法打开外部文件。如果可用磁盘空间不足，请删除文件或选择另一个磁盘以使文件系统中的空间可用。

如果您没有打开外部文件的文件系统权限，请使用所需权限指定另一个目录或登录。

-33042 Cannot open input file inputfile.

The embedded-language preprocessor cannot locate the file that you are trying to include in your program with the -I option. Check that the file is in the location that you have specified and that you have specified the location correctly. Also check that you have permission to open inputfile; if you do not, specify another directory or login with the required permission.

嵌入式语言的预处理器无法使用 -I 选项定位您试图在程序中包含的文件。检查该文件是否位于您指定的位置，并且已正确指定该位置。还要检查您是否有打开 inputfile 的权限；如果没有，请指定另一个目录或使用所需权限登录。

-33043 Out of memory.

The preprocessor was unable to allocate more memory. If possible,reduce the number of processes that are running at the same time as the preprocessor, or reduce the size of the program. Check that adequate swap-disk space exists. On DOS systems, you will need to free some disk space.

预处理器无法分配更多内存。如果可能的话，减少与预处理器同时运行的进程数量，或者减少程序的大小。检查是否存在足够的交换磁盘空间。在 DOS 系统上，您需要释放一些磁盘空间。

-33044 Precision must be greater than 0 and less than the specified number of digits.

You specified the precision and/or the scale for a DECIMAL value incorrectly. See the GBase 8s Guide to SQL: Reference and the appropriate GBase 8s ESQL manual for proper usage.

您错误地为 DECIMAL 值指定了精度和/或小数位数。请参阅 GBase 8s SQL 指南：参考和相应的 GBase 8s ESQL 手册以确保正确使用。

-33045 Overriding the previous definition of macro macro-name.

This message is a warning only. You have defined the macro macro-name more than once. The preprocessor uses the latest occurrence of macro-name.

此消息仅为警告。您已经不止一次定义了宏名。预处理器使用宏名称的最新出现。

-33046 Indicator cannot be used with records.

This message is a warning only. You cannot specify an Indicator variable for input to a host record or data structure. The indicator is ignored. An indicator variable must be associated with a single data item. If you need to use an indicator with a particular member of this record, you must list all the record members.

此消息仅为警告。不能为主机记录或数据结构指定输入指示符变量。该指示器被忽略。指示符变量必须与单个数据项关联。如果需要对此记录的特定成员使用指示符，则必须列出所有记录成员。

-33047 Record record-name is not allowed in this clause.

In this statement, you use the specified record where only a simple variable is allowed. Check the spelling of names and rewrite the statement using a simple variable. See the embedded-language manual and the GBase 8s Guide to SQL: Syntax.

在此语句中，您将使用指定的记录，其中只允许一个简单变量。检查名称的拼写，并使用一个简单的变量重写语句。请参阅嵌入式语言手册和 GBase 8s SQL 指南：语法。

-33049 Field type field-name has been used out of context.

The specified field-name is used incorrectly in the GET/SET DESCRIPTOR statement. See the GET DESCRIPTOR and SET DESCRIPTOR statements in the GBase 8s Guide to SQL: Syntax for the correct syntax.

指定的字段名在 GET/SET 描述符语句中使用不当。有关正确的语法，请参阅 GBase 8s SQL 指南：语法中的 GET 描述符和 SET 描述符语句。

-33050 The type or subtype type-name has already been used.

The statement redefines a user-defined type or subtype that has already been defined. This action is not allowed. Review the declarations, and use a unique name for this type.

该语句重新定义已经定义的用户定义类型或子类型。此操作是不允许的。检查声明，并使用此类型的唯一名称。

-33051 Syntax error on identifier or symbol symbol-name.

An error in syntax was found at or near symbol-name. Check the GBase 8s Guide to SQL: Syntax for the proper use of identifiers and the appropriate embedded-language manual for the proper use of other symbols.

在符号名或附近发现语法错误。检查 GBase 8s SQL 指南：语法以正确使用标识符和适当的嵌入式语言手册以正确使用其他符号。

-33052 Unmatched ELSE.

A matching IFDEF or IFNDEF statement does not precede this ELSE statement. Review the source lines that precede this point; the preceding statement was omitted or might not have been recognized due to an earlier error.

匹配的 IFDEF 或 IFNDEF 语句不在此 ELSE 语句之前。检查这一点之前的源行；由于前面的错误，前面的语句被省略了，或者可能没有被识别。

-33053 Unmatched ENDIF.

An IFDEF or IFNDEF statement does not precede this ENDIF statement.

Review the source lines that precede this point; the preceding statement was omitted or might not have been recognized due to an earlier error.

IFDEF 或 IFNDEF 语句不在此 ENDIF 语句之前。检查这一点之前的源行；由于前面的错误，前面的语句被省略了，或者可能没有被识别。

-33054 Updates are not allowed on a scroll cursor.

This UPDATE statement refers to a cursor that was declared with the SCROLL keyword. The UPDATE statement requires a cursor that has been declared FOR UPDATE to ensure that the proper level of locking is applied to the rows that will be updated. See the DECLARE statement in the GBase 8s Guide to SQL: Syntax for more information on the correct use of cursors.

此 UPDATE 语句引用 SCROLL 关键字声明的游标。UPDATE 语句要求为 UPDATE 声明一个游标，以确保将正确的锁定级别应用于将要更新的行。有关正确使用游标的更多信息，请参见 GBase 8s SQL 指南：语法中的 DECLARE 语句。

-33055 The name id-name has already been used.

The SQL identifier id-name has already been declared. Check the spelling of names and the declarations in the current name scope.

SQL 标识符 id-name 已经声明。检查名称的拼写和当前名称范围中的声明。

-33056 Error errno during output.

The error errno occurred during output. Check that sufficient disk space is available for the output file and that you have the necessary file-system permissions for the file location. Look up errno in the host operating-system manual (or see the list that begins on page 3)for the specific cause of the problem and the appropriate corrective action.

在输出期间发生错误 errno 。检查输出文件是否有足够的磁盘空间，文件位置是否具有必要的文件系统权限。在主机操作系统手册中查找 errno （或查看第3页开始的列表），了解问题的具体原因和适当的纠正措施。

-33057 Cannot open error log file errorfile.

You specified the log preprocessor option to have error and warning messages sent to errorfile rather than to standard output. However, the preprocessor cannot open errorfile because not enough disk space is available, or you do not have file-system permission to open the file.

If insufficient disk space is available, delete files to make space available in the file system, or select another disk. If you do not have file-system permission to open errorfile, specify another directory or login with the required permission.

您指定了日志预处理器选项，以便将错误和警告消息发送到错误文件，而不是发送到标准输出。但是，由于可用磁盘空间不足，或者您没有打开文件的文件系统权限，预处理器无法打开错误文件。如果可用磁盘空间不足，请删除文件以使文件系统中的空间可用，或选择另一个磁盘。如果您没有打开错误文件的文件系统权限，请指定另一个目录或使用所需权限登录。

-33058 Option-name is not a valid default option for the column definition.

See the GBase 8s Guide to SQL: Syntax for the valid DEFAULT clause options in a column definition.

请参阅列定义中的有效 DEFAULT 子句选项的 GBase 8s SQL 指南：语法。

-33060 Invalid expression.

The specified expression is incorrect. Refer to the GBase 8s Guide to SQL: Syntax for the correct syntax and usage for this expression.

指定的表达式不正确。有关此表达式的正确语法和用法，请参阅 GBase 8s SQL 指南：语法。

-33061 Unable to expand recursive macro macro-name.

The preprocessor cannot fully expand the macro-name macro because a loop exists in the defined macros. Correct the macro and try again.

预处理器无法完全展开宏名宏，因为定义的宏中存在一个循环。更正宏，然后再试一次。

-33062 Missing ENDIF.

An IFDEF or IFNDEF statement has no matching ENDIF statement prior to the end of the source file. Work upward from the end of the file, and check that each IFDEF and IFNDEF statement is paired with a matching ENDIF. Possibly the ENDIF was not recognized due to another error.

IFDEF 或 IFNDEF 语句在源文件结束之前没有匹配的 ENDIF 语句。从文件末尾向上工作，检查每个 IFDEF 和 IFNDEF 语句是否与匹配的 ENDIF 配对。可能由于另一个错误而无法识别 ENDIF。

-33063 Already within BEGIN DECLARE SECTION.

This message is a warning only. An EXEC SQL BEGIN DECLARE SECTION statement is inside another BEGIN/END DECLARE block. This statement is ignored. However, the warning might indicate a mix-up in the structure of your program. Check that all the declaration sections are properly delimited.

此消息仅为警告。EXEC SQL BEGIN DELARE SECTION 语句位于另一个 BEGIN/END DECLARE块中。此语句将被忽略。但是，警告可能表示程序的结构出现了混淆。检查所有声明部分是否正确地分隔。

-33064 variable-name has appeared before with a different case.

ESQL/language-name is case-insensitive.

This message is a warning only. The specified variable appears more than once with different combinations of uppercase and lowercase letters. Because this product is not case sensitive, all these names are treated as one. If you intended these names to indicate different variables, change the name (not merely the case) of one of the variable declarations and recompile.

此消息仅为警告。指定的变量以大写字母和小写字母的不同组合多次出现。因为该产品不区分大小写，所以所有这些名称都被视为一个名称。如果您打算使用这些名称来指示不同的变量，请更改其中一个变量声明的名称（而不仅仅是情况）并重新编译。

-33065 Cursor/statement id '' is too long when prefixed by module name.

This message is only a warning. When you use the -local preprocessing option,cursor names and statement names are prefixed with a unique tag generated from the module name. (On UNIX, the inode number of the source program is used as the unique tag.) The combined length of the cursor or statement name and the unique tag should not exceed the maximum length for identifiers,which depends on the database server. In GBase 8s Dynamic Server 9.2 or later,the maximum length is 128 characters. In other GBase 8s database servers,the maximum length is 18 characters.

这个消息只是一个警告。当您使用 -local 预处理选项时，游标名和语句名以从模块名生成的唯一标记作为前缀。(在 UNIX 上，源程序的 inode 编号用作唯一标记。)游标或语句名称和唯一标记的组合长度不应超过标识符的最大长度，这取决于数据库服务器。在GBase 8s Dynamic Server 9.2 或更高版本中，最大长度为 128 个字符。在其他 GBase 8s 数据库服务器中，最大长度为 18 个字符。

In the case of , the combined length of the name and unique tag exceeds the maximum length for identifiers. As a result, if the same name is used in a different source module, the two names might not be distinct, as the -local option requests.

在的情况下，名称和唯一标记的组合长度超过标识符的最大长度。因此，如果在不同的源模块中使用相同的名称，则这两个名称可能不会像 -local 选项请求的那样是不同的。

-33066 Cursor/statement ids and are not unique in first 128 characters when prefixed by module name.

When you use the -local preprocessing option, cursor and statement names are prefixed with a unique tag that is generated from the module name. (On UNIX,the inode number of the source program is used as the unique tag.) In this case, and are at least 124 characters long, and their first 123 characters do not differ. As a result, they are the same when the tag is added and the result is trimmed to 128 characters.

当您使用 -local 预处理选项时，游标和语句名以从模块名生成的唯一标记作为前缀。

(在 UNIX 上，源程序的 inode 编号用作唯一标记。)在这种情况下，和至少有 124 个字符长，它们的前 123 个字符没有区别。因此，当添加标记并将结果裁剪为 128 个字符时，它们是相同的。

Change the two names to avoid name collision and try again.

更改这两个名称以避免名称冲突，然后再试一次。

-33066 Cursor/statement ids and are not unique in first 18 characters when prefixed by module name.

When you use the -local preprocessing option, cursor and statement names are prefixed with a unique tag that is generated from the module name. (On UNIX,the inode number of the source program is used as the unique tag.) In this case, and are at least 14 characters long, and their first 13 characters do not differ. As a result, they are the same when the tag is added and the result is trimmed to 18 characters.

当您使用 -local 预处理选项时，游标和语句名以从模块名生成的唯一标记作为前缀。

（在 UNIX 上，源程序的 inode 编号用作唯一标记。)在这种情况下，和至少有 14 个字符长，它们的前 13 个字符没有区别。因此，当添加标记并将结果裁剪为 18 个字符时，它们是相同的。

Change the two names to avoid name collision and try again.

请更改这两个名称以避免名称冲突，然后再试一次。

This message applies to GBase 8s Extended Parallel Server, GBase 8s Dynamic Server with Advanced Decision Support and Extended Parallel Options,GBase 8s OnLine XPS, GBase 8s Dynamic Server, GBase 8s Universal Server,GBase 8s OnLine Dynamic Server, and GBase 8s SE.

此消息适用于具有高级决策支持和扩展并行选项的 GBase 8s 扩展并行服务器、GBase 8s Online XPS、 GBase 8s Dynamix Dynamic Server、 GBase 8s Universal Server、GBase 8s Online Dynamic Server 和 GBase 8s SE。

-33067 ELIF without IFDEF.

An IFDEF or IFNDEF statement does not precede this ELIF statement.

Review the source lines that precede this point. The preceding statement was omitted, or it might not have been recognized due to an earlier error.

IFDEF 或 IFNDEF 语句不在此 ELIF 语句之前。检查这一点之前的源行。前面的语句被省略了，或者由于先前的错误而无法识别。

-33068 ELIF after ELSE.

The ESQL preprocessor ELSE statement indicates the last part of an IFDEF or IFNDEF statement; another ELIF part might not follow. Review the contents of this IFDEF or IFNDEF statement and put its parts in order.

ESQL 预处理器 ELSE 语句指示 IFDEF 或 IFNDEF 语句的最后一部分；另一个 ELIF 部分可能不跟随。检查 IFDEF 或 IFNDEF 语句的内容，并将其各部分排序。

-33070 Stack overflow occurred during statement parse.

This message, which indicates that the parser stack has overflowed,rarely occurs. It might occur, for example, if your embedded-language statement (SELECT, INSERT, UPDATE, DELETE, and so on) contains an extremely large or complicated clause (WHERE, MATCHES, LIKE, and so on)that the parser is trying to process. In that case, break up the clause and try again.

此消息表示解析器堆栈溢出，很少发生。例如，如果您的嵌入式语言语句（SELECT、INSERT、UPDATE、DELETE 等）包含解析器试图处理的非常大或复杂的子句（其中匹配等），则可能发生这种情况。在这种情况下，将该子句拆分，然后再试一次。

-33071 The statement id statement_ID has already been used.

This warning message indicates that you have used two PREPARE statement identifiers with the same name. For example:此警告消息表示您使用了两个名称相同的准备语句标识符。例如：exec sql prepare stmt_id from "select * from tab";exec sql prepare stmt_id from "insert into tab values(1)";-33074 Explicit cast, either with CAST keyword or (::) operator, is not allowed in client collections.

You cannot use explicit casts in client collections. For example, the following example is not allowed:不能在客户端集合中使用显式强制转换。例如，不允许使用以下示例： $client collection list(row( a udt_1, b list(int))) mylist;$ insert into table (:mylist) values (CAST(1 AS udt_1), list{1,2,3});$insert into table (:mylist) values (1::udt_1, list{1,2,3});When you enter esql -e client.ec, you get the following errors:您输入 esql -e client.ec 时，会得到以下错误：esqlc: "client.ec", line 2: Error -33074: Cannot use CAST in client collections.

esqlc：“client.ec”，第2行：Error-33074：无法在客户端集合中使用 CAST 。

esqlc: "client.ec", line 3: Error -33074: Cannot use CAST in client collections.

esqlc：“client.ec”，第3行：Error-33074：无法在客户端集合中使用 CAST 。

-33075 Cannot use user-defined routines in client collection/row constructors.

The user has tried to call a user-defined routine function in a ROW or COLLECTION constructor for a client collection or row host variable.

Check the syntax of the statement and change the statement so that it does not call a user-defined routine. User-defined routines can be executed only on the server.

用户试图为客户端集合或行宿主变量调用行或集合构造函数中的用户定义的例程函数。检查语句的语法并更改语句，使其不调用用户定义的例程。用户定义的例程只能在服务器上执行。

-33083 Cannot open file file_name because of too many open files.

The preprocessor cannot open the file because too many files are open. Check your system resources to see if you can increase the number of file handles (descriptors). Close unnecessary open files. Also check for mistakes that might cause recursive file inclusion.

由于打开的文件太多，预处理器无法打开该文件。检查系统资源，看看是否可以增加文件句柄（描述符）的数量。关闭不必要的打开文件。还检查可能导致递归文件包含的错误。

-33084 The lvarchar host variable('') should be an array or a pointer.

This message is only a warning; compilation continues. ESQL/C does not know the size of the lvarchar host variable. Although syntactically correct,this might cause a problem in your application.

此消息只是一个警告；编译仍在继续。ESQL/C 不知道 lvarchar 主机变量的大小。虽然语法正确，但这可能会在应用程序中造成问题。

Specify the variable as an array or a pointer.

请将变量指定为数组或指针。

-33085 The username or the password was not provided in a TRUSTED connection.

Both are required.

Any CONNECT statement that includes the TRUSTED keyword must also include the USER Authentication clause. To establish a trusted connection, this clause must include a valid username and a valid password for that username,as in this example:包含可信关键字的任何 CONNECT 语句也必须包括用户身份验证子句。若要建立受信任的连接，此子句必须包含该用户名的有效用户名和有效密码，如本例所示：EXEC SQL CONNECT TO "testdb1" AS "s1" USER 'zelaine' USING :var_zpass WITH CONCURRENT TRANSACTION TRUSTED;The USER Authentication Clause requires these syntax elements:USER Authentication 子句需要以下语法元素：* A quoted string (or a host variable) specifying a valid authorization identifier must immediately follow the USER keyword.

* 指定有效授权标识符的引号字符串(或主机变量)必须紧跟 USER 关键字。

* A host variable that evaluates to the password for that authorization identifier must immediately follow the USING keyword.

* 计算为该授权标识符的密码的主机变量必须立即跟随 USING 关键字。

CONNECT statements that do not include the USER Authentication clause cannot include the TRUSTED keyword.

不包含 USER Authentication 子句的 CONNECT 语句不能包含可信关键字。

-33200 Invalid statement on symbol variable-name.

The specified type was not defined or a $character was misplaced in a statement. Check for misspellings, misplaced$ characters, or undefined types.

指定的类型没有定义，或者语句中的 $字符被错误地放置。检查拼写错误、错误放置$ 字符或未定义类型。

-33201 Fixed character pointers are not allowed.

Fixchar character pointers are not allowed in this context. Replace the fixchar pointer with a character pointer.

在此上下文中不允许使用固定字符指针。用字符指针替换固定指针。

-33202 Incorrect dimension on array variable variable-name.

You referenced the array variable with an incorrect dimension. Correct the dimension and retry.

使用不正确的维度引用数组变量。修正维度并重试。

-33203 Incorrect levels of indirection on variable variable-name.

A pointer variable is used with the wrong number of level indirection.

Check the indirection levels in this statement.

指针变量与错误的级别间接数一起使用。检查此语句中的间接级别。

-33204 Right curly brace found with no matching left curly brace.

The code either includes a stray closing brace (}) or is missing an opening brace ({). Check the code for unmatched curly braces or other incorrect punctuation such as a missing end-quote or end-comment.

该代码要么包含一个散乱的结束大括号(})，要么缺少一个开口大括号({)。检查代码中不匹配的大括号或其他不正确的标点符号，例如缺少的尾引号或结束注释。

-33205 PARAMETER cannot be used inside of a C block.

The PARAMETER statement is allowed only in a function declaration block, not within a namely block that is nested in a function.

PARAMETER 语句只允许在函数声明块中，而不允许在嵌套在函数中的即块中。

-33206 Qualifiers for variable-name not initialized.

This message is a warning only. Due to the complexity of the specified DATETIME or INTERVAL variable, the qualifiers of its elements cannot be initialized properly. Compilation continues, but the variable might not be initialized.

此消息仅为警告。由于指定 DATETIME 或 INTERVAL 变量的复杂性，其元素的限定符无法正确初始化。编译仍在继续，但变量可能未被初始化。

-33207 Type typedef-name too complex for ESQL/C.

The definition of the typedef variable is too complex. ESQL/C does not support the use of multidimensional arrays or unions in a typdef.

Simplify the typedef.

typedef 变量的定义太复杂了。ESQL/C 不支持在 typdef 中使用多维数组或联合。简化typedef。

-33208 Runtime error is possible because size of host-variable-name is unknown.

This message is a warning only; compilation continues. ESQL/C does not know the size of the host character variable. If the variable is used in an INTO clause, memory might be overwritten. Specify the variable as a character array with a numeric size. The numeric size can be a literal value or an ESQL/C macro value.

此消息仅为警告；编译仍在继续。ESQL/C 不知道主机字符变量的大小。如果变量在 INTO子句中使用，则可能会覆盖内存。将变量指定为具有数字大小的字符数组。数值大小可以是文字值，也可以是 ESQL/C 宏值。

-33209 Statement must terminate with ';'.

This message is a warning. This statement does not have the necessary semicolon. Even though the preprocessor can proceed without any problems, you should add a semicolon to the statement. Then you can avoid future problems if code is added to this program.

这条信息是一种警告。此语句没有必要的分号。即使预处理程序可以顺利进行，您也应该在语句中添加一个分号。然后，如果将代码添加到此程序中，则可以避免将来的问题。

-33500 filename: Bad environment variable on line number.

The entry on the specified line in the specified environment configuration file is incorrect. Modify your entry in the file (the environment variable name and/or setting) and try again.

指定环境配置文件中指定行上的项不正确。修改文件中的条目（环境变量名称和/或设置），然后再试一次。

-33501 Mapping file for DBAPICODE is not found.

The SQL API cannot find the character-mapping file for the specified DBAPICODE environment variable setting and the standard code set. Check that the mapped code set exists in the message directory for your platform. In NLS-ready systems, the standard code set is defined in the LANG environment variable. In systems that are not NLS ready, the standard code set is the default 8-bit character set.

SQL API 找不到指定 DBAPICODE 环境变量设置和标准代码集的字符映射文件。检查平台的消息目录中是否存在映射的代码集。在 NLS 就绪系统中，标准代码集是在 LANG 环境变量中定义的。在未准备好 NLS 的系统中，标准代码集是缺省的8位字符集。

-33502 Mapping file does not have the correct format.

The mapping file for the specified DBAPICODE environment variable is formatted incorrectly. The text file for the character mapping table can consist of any number of lines. A line can be a comment, or a one-to-one character map of a DBAPICODE character code to the equivalent character in the target code set. The text file should be written in U.S. ASCII or the code set that has the equivalent representation of U.S. ASCII for the significant characters (#,parentheses, numeric characters).

指定的 DBAPICODE 环境变量的映射文件格式不正确。字符映射表的文本文件可以由任意数量的行组成。行可以是 DBAPICODE 字符代码的注释或一对一字符映射，也可以是目标代码集中的等效字符映射。文本文件应该用美国 ASCII 或对重要字符(#、括号、数字字符)的等效表示形式的代码集来编写。

-33988 External Space creation failed.

The server could not add the external space. Check the error returned with this failure.

服务器无法添加外部空间。检查此故障返回的错误。

-33990 External Space drop fails.

An attempt to drop the external space failed. Check the error associated with this failure.

试图删除外部空间的尝试失败。检查与此故障相关的错误。

-34380 Input stream contains an illegal multi-byte character.

The ESQL/C source has illegal multibyte characters. Review the source file.

ESQL/C 源具有非法的多字节字符。检查源文件。

-34381 Input stream ends in the middle of a valid character.

The ESQL/C source file ends in the middle of a valid multibyte character. The source file might be truncated. Review the source file.

ESQL/C 源文件以有效多字节字符的中间结束。源文件可能被截断。检查源文件。

-34382 A system error occurred while reading the input stream.

A system error num occurred while the ESQL/C preprocessor read the ESQL/C source file. Look for operating-system messages to determine the cause of the problem.

ESQL/C 预处理器读取 ESQL/C 源文件时出现系统错误 num。查找操作系统消息以确定问题的原因。

-34383 An unknown error num occurred while reading the input stream.

An unknown error num occurred while the ESQL/C preprocessor read the ESQL/C source file. Check that the source file is a valid ESQL/C source file.

ESQL/C 预处理程序读取 ESQL/C 源文件时出现未知错误 num。检查源文件是否为有效的ESQL/C 源文件。

-34388 Invalid character has been found. Cannot continue the processing.

An internal function, while parsing the elements in an SPL routine,has encountered an illegal character during multibyte processing. The following options are passed:内部函数在解析 SPL 例程中的元素时，在多字节处理过程中遇到了非法字符。通过下列选项：* database@dbserver;owner.procname* database;owner.procname* database;procname* database@dbserver;procname* owner.procname* procname Review these options for possible illegal characters.

检查这些选项是否可能存在非法字符。

-34389 Illegal character has been found in the input string.

The SQL script has illegal characters. Review the script file.

SQL 脚本具有非法字符。检查脚本文件。

-34390 Invalid delimiter; Don't use '\', SPACE, HEX or Multibyte chars.

The delimiter specified for the FILE statement is illegal. You cannot use a new- line character, backslash, space, tab, hexadecimal digit (0 to 9, A to F, a to f), or multibyte character as a delimiter. Check the statement and change the delimiter symbol.

为 FILE 语句指定的分隔符是非法的。不能使用新行字符、反斜杠、空格、制表符、十六进制数字（0 至 9、A 至 F、a 至 f）或多字节字符作为分隔符。检查语句并更改分隔符号。

-34393 GLS codeset conversion initialization failed.

The code-set conversion initialization failed during the session initialization. Not enough memory is available for the code-set conversion table.

在会话初始化期间，代码集转换初始化失败。没有足够的内存用于代码集转换表。

-34394 Session Initialization failed on bad locale name: locale-name The session initialization failed. An invalid locale name has been supplied for the locale initialization in the session initialization.

The environment variable to specify the locale name has an incorrect value. Check the value of the corresponding environment variable,CLIENT_LOCALE or DB_LOCALE.

会话初始化失败。已为会话初始化中的区域设置初始化提供了无效的区域设置名称。指定区域设置名称的环境变量的值不正确。检查相应的环境变量 CLIENT_LOCALE 或DB_LOCALE 的值。

-34395 Illegal multibyte character. Line# num An illegal multibyte character has been detected on the line of the loadable menu source file. Review the source file.

已在可加载菜单源文件的行中检测到非法多字节字符。检查源文件。

-34396 Illegal wide character. Line# num This internal error indicates that the conversion of internal wide-character formats to multibyte characters failed. Check the program logic.

此内部错误表示内部宽字符格式到多字节字符的转换失败。检查程序逻辑。

-35580 General Table Manager: No table allocated.

The table has not been created or was deleted.

表尚未创建或删除。

-35583 General Table Manager: Duplicate keys not allowed.

Table entries with the same key are not allowed.

不允许使用相同键的表条目。

-35584 General Table Manager: Table is full.

Table is full and cannot be extended.

表已满，无法扩展。

-35585 General Table Manager: Entry is locked.

Entry of a table is already locked.

表的条目已经锁定。

-35586 General Table Manager: Table is locked.

Table is already locked.

表的条目已经锁定。

-35587 General Table Manager: No entry.

The required entry does not exist.

不存在所需的条目。

-38000 Unknown throwable: (java.security.AccessControlException: access denied (java.security.SecurityPermission getPolicy)).

This error might occur if there is no gbasedbt.policy file in$GBS_HOME/extend/krakatoa.

如果在 $GBS_HOME/extend/krakatoa 中没有 gbasedbt.policy 文件，则可能发生此错误。

If you do not have particular security concerns, you can copy the file gbasedbt.policy.std to gbasedbt.policy.

如果您没有特殊的安全考虑，您可以将文件 gbasedbt.policy.std 复制到gbasedbt.policy 。

-38514 Set transport buffers size and count FAILED.

The transport buffer size has changed since the last backup.

Return code 120 displays.

自上次备份以来，传输缓冲区大小发生了更改。返回代码 120。

Set the transport buffer size in the ONCONFIG file back to its value at the time of the backup and try the restore again. You might have to refer to file-system backups of the ONCONFIG file to get the previous value.

将 ONCONFIG 文件中的传输缓冲区大小设置为备份时的值，然后再次尝试还原。您可能必须参考 ONCONFIG 文件的文件系统备份才能获得前面的值。

-38515 Free transport buffer FAILED.

An error occurred when the database server tried to free the transport buffers.

数据库服务器试图释放传输缓冲区时出错。

Note all circumstances, save a copy of the ON-Bar activity log and database server message log, and contact GBase Technical Support.

注意所有情况，保存 ON-Bar 活动日志和数据库服务器消息日志的副本，并与 GBase 8s技术支持联系。

-38516 Client process not registered.

The onbar-worker process is not registered with the GBase 8s database server.

onbar-worker 进程未在 GBase 8s 数据库服务器中注册。

Recommended corrective actions follow:建议的纠正措施如下：1. Use the onstat -g bus command to make sure that the onbar-worker process is running. Start a new onbar-worker process, if needed.

使用 onstat -g 总线命令确保 onbar 工作进程正在运行。如果需要，启动一个新的 onbar-worker 流程。
If an onbar-worker process is running, try ending it with the following command and starting a new onbar-worker process:2. 如果 onbar-worker 进程正在运行，请尝试使用以下命令结束它并启动一个新的onbar-worker 进程：kill -2 <worker_process_id>If this problem persists, contact GBase Technical Support.

如果此问题仍然存在，请与 GBase 技术支持部门联系。

-38573 Error: pointer is NULL ( ).

Internal error. A pointer variable unexpectedly is NULL.

内部错误指针变量意外为空。

Contact GBase Support for assistance.

请与 GBase 支持联系以获得帮助。

-38574 Creating pipes failed. errno = .

Cannot create output pipes. The 'errno' is the number of the operating system error returned.

无法创建输出管道。“errno”是返回的操作系统错误数。

Refer to your operating system documentation.

请参阅您的操作系统文档。

-38575 Creating a process failed. errno = .

The system call to create or fork a process failed. The 'errno' is the number of the operating system error returned.

创建或发送进程的系统调用失败。“errno”是返回的操作系统错误数。

Refer to your operating system documentation.

请参阅您的操作系统文档。

-38576 Closing the unused end of a pipe failed.

The system call to close the unused end of the filter pipe failed.

系统调用关闭未使用的过滤器管道端失败。

This error is internal. Retry the operation and if it continues to fail, contact GBase Support.

此错误为内部错误。重试操作，如果操作继续失败，请与 GBase 支持部门联系。

-38577 Duplicating the file descriptors failed. errno=.

The system call to duplicate file descriptors failed. The 'errno' is the number of the operating system error returned.

复制文件描述符的系统调用失败。“errno”是返回的操作系统错误数。

Refer to your operating system documentation.

请参阅您的操作系统文档。

-38578 Executing the backup and restore filter failed. errno = .

The system call to execute the backup and restore filter program failed.

The 'errno' is the number of the operating system error returned.

执行备份和还原筛选程序的系统调用失败。“errno”是返回的操作系统错误数。

Refer to your operating system documentation.

请参阅您的操作系统文档。

-38579 Writing to the backup and restore filter failed. errno = .

The system call to write to the backup and restore filter pipe failed. The 'errno' is the number of the operating system error returned.

系统调用写入备份和还原筛选管失败。“errno”是返回的操作系统错误数。

Refer to your operating system documentation.

请参阅您的操作系统文档。

-38580 Reading from the backup and restore filter failed. errno = .

The system call to read from the backup and restore filter pipe failed. The 'errno' is the number of the operating system error returned.

从备份和还原筛选管道读取的系统调用失败。“errno”是返回的操作系统错误数。

Refer to your operating system documentation.

请参阅您的操作系统文档。

-38581 The peek system call on input from the backup and restore filter failed. errno = .

The peek system call on input from the backup and restore filter pipe failed.

The 'errno' is the number of the operating system error returned.

从备份和恢复筛选管道输入的 peek 系统调用失败。“errno”是返回的操作系统错误数。

Refer to your operating system documentation.

请参阅您的操作系统文档。

-38584 Thread creation for reading from the backup and restore filter failed.

Creating a thread that reads input from the backup and restore filter program has failed.

创建从备份和还原筛选程序读取输入的线程失败。

Refer to your operating system documentation.

请参阅您的操作系统文档。

-38585 Create event failed.

Creating an event failed.

创建事件失败。

Refer to your operating system documentation.

请参阅您的操作系统文档。

-41000 Error in reading the [INET_CONNECTION] section of the GBASEDBT.INI file.

Check the [INET_CONNECTION] section of the GBASEDBT.INI file to make sure this section has the following section heading:请检查 GBASEDBT.INI 文件的 [INET_CONNECTION]部分，以确保该节有以下章节标题：[INET_CONNECTION]-41001 The GBASEDBT.INI file does not have a hostname or has a format error.

Check the GBASEDBT.INI file. If you did not define a host name variable in the InetLogin structure, the [INET_CONNECTION] section must have a host name. The host name must be defined in the [INET_CONNECTION]section with the following format:检查 GBASEDBT.INI 文件。如果您没有在 InetLogin 结构中定义主机名变量，[INET_CONNECTION] 部分必须具有主机名。主机名必须在 [INET_CONNECTION] 部分中定义，格式如下：host=hostname-41002 The GBASEDBT.INI file does not have a username or has a format error.

Check the GBASEDBT.INI file. If you did not define a user name variable in the InetLogin structure, the [INET_CONNECTION] section must have a user name. You must define the user name in the [INET_CONNECTION]section with the following format:检查 GBASEDBT.INI 文件。如果您没有在 InetLogin 结构中定义用户名变量，则[INET_CONNECTION] 部分必须具有用户名。必须使用下列格式在 [INET_CONNECTION] 部分中定义用户名：user=username-41004 The GBASEDBT.INI file does not have a protocolname or has a format error.

Check the GBASEDBT.INI file. If you did not define a protocol name variable in the InetLogin structure, the [INET_CONNECTION] section must have a protocol name. You must define the protocol name in the[INET_CONNECTION] section with the following format:检查 GBASEDBT.INI 文件。如果您没有在 InetLogin 结构中定义协议名变量，则[INET_CONNECTION] 部分必须具有协议名称。必须使用以下格式在 [INET_CONNECTION]部分中定义协议名称：protocol=protocolname-41005 Error in reading the [INET_PROTOCOL] section of the GBASEDBT.INI file.

Check the [INET_PROTOCOL] section of the GBASEDBT.INI file to make sure this section has the following section heading:请检查 GBASEDBT.INI 文件的 [INET_PROTOCOL] 部分，以确保本节有以下章节标题：[INET_PROTOCOL]-41006 Protocolname is not in the [INET_PROTOCOL] section of the GBASEDBT.INI file.

Check the GBASEDBT.INI file. The protocol name that is specified in the[INET_CONNECTION] section should match the protocol name that is specified in the [INET_PROTOCOL] section. The protocol name must define the correct .DLL module for that protocol. If you are using an IPX/SPX protocol, then ipx=INETIPX.DLL. If you are using a Windows Sockets 1.1-compliant TCP/IP protocol, then tcpip=INETWSOK.DLL.

检查 GBASEDBT.INI 文件。在[INET_CONNECTION]部分中指定的协议名称应该与[INET_PROTOCOL]节中指定的协议名称相匹配。协议名称必须为该协议定义正确的 .DLL模块。如果使用的是 IPX/SPX 协议，则 IPX=INETIPX.DLL，如果使用的是Windows Sockets 1.1-compliant TCP/IP 协议, 则 tcpip=INETWSOK.DLL.。

-41007 Error in loading GBase 8s NET for Windows library.

Check your path. If you are using a Windows Sockets 1.1-compliant TCP/IP protocol, the INETWSOK.DLL module must be in your path. If you are using the IPX/SPX protocol, the INETIPX.DLL module must be in your path. These modules must be in your path. In addition, you might not have enough memory to load the correct DLL module.

检查你的路径。如果使用 Windows Sockets 1.1-compliant TCP/IP 协议，则必须在您的路径中使用 INETWSOK.DLL 模块。如果使用的是 IPX/SPX 协议，则 INETIPX.DLL 模块必须位于您的路径中。这些模块必须在您的路径上。此外，您可能没有足够的内存来加载正确的 DLL 模块。

-41008 Number of protocols exceeds the number of protocols that are supported in this version.

You must use only one protocol at a time to communicate with your remote database server.

一次只能使用一个协议与远程数据库服务器通信。

-41009 Error in closing connection.

An error occurred when the connection was closed. No corrective action is provided.

当连接关闭时发生错误。没有提供纠正。

-41020 Connection error.

Too many applications are active under Windows. Close some of your applications and try again.

Windows 下有太多的应用程序处于活动状态。关闭一些应用程序，然后再试一次。

-41021 Connection Busy.

You are currently making a database server request. You cannot make another argument until the current request is finished.

您目前正在发出数据库服务器请求。在当前请求完成之前，您不能再进行另一个参数。

-42306 Could not set lock mode to wait.

The utility that you were running could not access the contents of a table because it could not wait for a table lock. Wait a while and retry running dbschema or dbexport.

正在运行的实用程序无法访问表的内容，因为它不能等待表锁。请稍等，然后重试运行dbschema 或 dbexport。

-43000 ON-Bar backup usage.

The backup command was entered incorrectly. For details, see the Backup and Restore Guide.

输入的备份命令不正确。有关详细信息，请参阅备份和还原指南。

Revise the command and try again.

修改命令再试一次。

-43001 ON-Bar restore usage.

The restore command was entered incorrectly. For details, see the Backup and Restore Guide.

restore 命令输入错误。有关详细信息，请参阅备份和还原指南。

Revise the command and try again.

修改命令再试一次。

-43002 ON-Bar session usage.

The session command was entered incorrectly. For details, see the Backup and Restore Guide.

session 命令输入错误。有关详细信息，请参阅备份和还原指南。

Revise the command and try again.

修改命令再试一次。

-43003 onbar_w usage.

The onbar_w command was entered incorrectly. For details, see the Backup and Restore Guide.

onbar_w 命令输入错误。有关详细信息，请参阅备份和还原指南。

Revise the command and try again.

修改命令再试一次。

-43004 The connection-address is determined by the XCC package.

A command was entered incorrectly. This message might indicate an error in ON-Bar, as this process should be started only by an onbar command-line process and rarely by hand.

输入的命令不正确。此消息可能表示 ON-Bar 中的错误，因为此进程只应由 onbar 命令行进程启动，很少由手动启动。

To start onbar_m by hand, use the ON-Bar activity log of the command-line process (BAR_ACT_LOG or /tmp/bar_act.log) to determine the correct value and try again. If this message was issued automatically, contact GBase Technical Support.

若要手动启动 onbar_m，请使用命令行进程（BAR_ACT_LOG 或/tmp/bar_act.log）的 ON-Bar 活动日志来确定正确的值，然后再试一次。如果此消息是自动发出的，请与 GBase技术支持部门联系。

-43005 The syntax will not be supported in future releases - use .

The command-line syntax for ON-Bar backup has changed. The current action will complete as requested.

ON-Bar 备份的命令行语法已更改。目前的将按要求完成。

In the future, use the new ON-Bar syntax. To use this new syntax, you might have to change scripts you have written.

在未来，使用新的 ON-Bar 语法。要使用这种新语法，您可能必须更改您编写的脚本。

-43006 onsmsync usage.

The onsmsync command was entered incorrectly. For details, see the Backup and Restore Guide.

onsmsync 命令输入错误。有关详细信息，请参阅备份和还原指南。

Revise the command and try again.

修改命令再试一次。

-43010 Bad option usage: -f option requires a filename.

The user entered the -f option and did not specify a filename. ON-Bar does not know which storage spaces to use in this command, so it cannot continue.

用户输入了 -f 选项，没有指定文件名。ON-Bar 不知道在此命令中使用哪些存储空间，因此不能继续。

Specify the name of a file that contains the list of storage spaces ON-Bar should act upon, after the -f option, and rerun the command.

在 -f 选项之后指定包含 ON-Bar 存储空间列表的文件名，并重新运行命令。

-43011 The -f command is ignored for whole system backup/restore and fake backup.

The user entered the command options -w -f or -F -f .

Because whole-system backup, whole-system restore, and fake backup affect all spaces, the backup and restore will continue and the -f option will be ignored.

用户输入命令选项 -w -f 或者 -F -f 。因为全系统备份、全系统还原和假备份会影响所有空间，所以备份和还原将继续进行，而 -f将继续执行。

-43012 Setting backup level to 0 for this command.

Only level-0 backup is supported for a fake backup or external backup.

对于假备份或外部备份，只支持 0 级备份。

No action is required.

不需要操作。

-43013 Unable to read backup level, defaulting to level .

The backup level entered on the command line is not valid. A level-0 backup is automatically performed instead.

在命令行中输入的备份级别无效。将自动执行 0 级备份。

-43014 Unable to read logical log ID.

The logical log ID entered on the command line is not valid.

在命令行中输入的逻辑日志 ID 无效。

Verify that the logical log ID is correct and retry the command.

验证逻辑日志 ID 是否正确，然后重试命令。

-43015 Restore cannot be restarted. No unfinished restartable restore found.

The restore cannot be restarted because no restore file exists in the$GBS_HOME/etc or %GBS_HOME%\etc directory. This means that no previous restore exists or that the restore succeeded.

无法重新启动还原，因为 $GBS_HOME/etc 或 %GBS_HOME%\etc 目录中不存在还原文件。这意味着以前的还原不存在，或者恢复成功。

Use 'onbar -r' for a first-time restore.

第一次恢复时使用‘onbar-r’。

-43016 Invalid Point In Time value specified: .

Contact GBase Technical Support.

与 GBase 技术支持部门联系。

-43017 A Point in Log restore is permitted only during a Full restore.

You cannot do a point-in-log restore when the database server is online.

数据库服务器联机时无法执行点日志还原。

Do a cold restore.

请执行冷还原。

-43018 A point-in-time restore is permitted only during a full restore.

You cannot do a point-in-time restore unless all spaces are restored.

除非恢复所有空间，否则不能执行 point-in-time 恢复。

Do not specify any spaces on the command line.

不要在命令行上指定任何空间。

-43019 Invalid serial number. Consult your installation instructions.

An error occurred during the installation of ON-Bar.

安装 ON-Bar 时发生错误。

Ask your database server administrator to reinstall ON-Bar.

请数据库服务器管理员重新安装 ON-Bar。

-43020 Storage space names ignored for fake backup, whole system backup/restore, log restore, or log salvage.

A fake backup or whole-system restore backs up and restores all storage spaces. Storage spaces are not included in the log restore or log salvage.

假备份或整个系统还原备份和恢复所有存储空间。日志恢复或日志挽救中不包括存储空间。

-43021 Expiration specification is invalid for the option.

The value given to the named command-line option is inappropriate for that option. Either the format is incorrect or the option is missing.

指定命令行选项的值不适合该选项。格式不正确或缺少该选项。

Compare the value of the option to the usage statement, revise the command,and try again.

请将该选项的值与使用语句进行比较，修改命令，然后再试一次。

-43022 Cannot expire all versions of all objects. Must give -g option a value > 0.

The onsmsync command will not remove all backup objects, which is the meaning of -g 0.

onsmsync 命令不会删除所有备份对象，这是 -g 0 的意思。

Try onsmsync again with a positive integer argument to -g.

再次尝试 onsmsync 使用正整数参数到 -g。

-43023 Bad option usage: -n option requires a log number.

The user entered the -n option and did not specify a log number. ON-Bar does not know which log to restore to in this command, so it cannot continue.

用户输入了 -n 选项，没有指定日志编号。ON-Bar 不知道在此命令中还原到哪个日志，因此无法继续。

Specify the log number, after the -n option, and rerun the command.

在 -n 选项之后指定日志编号，然后重新运行命令。

-43024 Chunk rename failed.

An error occurred while mapping old chunk location to new chunk location.

将旧 chunk 位置映射到新 chunk 位置时发生错误。

Check the rename options of your command line and the mapping, then retry.

If the error persists, refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

检查命令行的重命名选项和映射，然后重试。如果错误仍然存在，请参考数据库服务器消息日志以获得更多信息。如果错误的原因尚不清楚，请与 GBase 技术支持部门联系。

-43025 Chunk rename failed.

An error occurred while mapping old chunk location to new chunk location.

将旧 chunk 位置映射到新 chunk 位置时出错。

Refer to the database server message log for more information.

Check the rename options of your command line and retry the command.

If the error persists and the cause of the error is still unclear,contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。检查命令行的重命名选项，然后重试命令。如果错误仍然存在，并且错误原因仍不清楚，请与 GBase 技术支持部门联系。

-43035 You must be user root or gbasedbt to run ON-Bar.

Only users root and gbasedbt or members of the bargroup group are allowed to execute ON-Bar.

只允许 root 用户和 gbasedbt 用户或 bargroup 组的成员执行 ON-Bar 。

Log in as user root or gbasedbt, or have your system administrator add your login name to the bargroup group before you attempt the backup or restore.

以 root 用户或 gbasedbt 用户身份登录，或者让系统管理员在尝试备份或还原之前将登录名添加到 bargroup 组。

-43036 You must be a member of gbasedbt-admin group to run ON-Bar.

Only users listed in the gbasedbt-admin group are allowed to execute ON-Bar.

只允许在 Gbasedbt-admin 组中列出的用户执行 ON-Bar。

Ask your Database System Administrator to add your username to the gbasedbt-admin Group.

请数据库系统管理员将您的用户名添加到 Gbasedbt-admin 组。

-43037 You must be user gbasedbt to run ON-Bar.

Only users are allowed to execute ON-Bar.

只允许 Gbasedbt 用户执行 ON-Bar。

在尝试备份或还原之前作为 Gbasedbt 用户登录。

-43038 The ON-Bar log file cannot be a symbolic link.

The ON-Bar log file that ON-Bar is attempting to open is a symbolic link. For security reasons, this is not permissible.

ON-Bar 试图打开的 ON-Bar 日志文件是一个符号链接。出于安全原因，这是不允许的。

Remove the symbolic link or change the onconfig file so that the ON-Bar parameters BAR_DEBUG_LOG and/or BAR_ACT_LOG in your ONCONFIG file point to non-symbolic linked files.

删除符号链接或更改 onconfig 文件，以便 ONCONFIG 文件中的 ON-Bar 参数BAR_DEBUG_LOG 和/或 BAR_ACT_LOG 指向非符号链接文件。

-43039 The ON-Bar log file must be owned by user gbasedbt.

The log file that ON-Bar is attempting to open is owned by a user other than user gbasedbt.

ON-Bar 试图打开的日志文件由 Gbasedbt 用户以外的用户拥有。

Change the ownership of the log file to user gbasedbt, or change the BAR_ACT_LOG and/or BAR_DEBUG_LOG values in the ONCONFIG file to point to different log files.

将日志文件的所有权更改为 Gbasedbt 用户，或将 ONCONFIG 文件中的 BAR_ACT_LOG和/或 BAR_DEBUG_LOG 值更改为指向不同的日志文件。

-43040 Supplied point in time later than latest log - using latest logfile .

The point in time specified on the command line is later than the last logged transaction. The time of the latest logged transaction will be used instead.

命令行上指定的时间点比上次记录的事务要晚。将使用最新记录的事务的时间。

-43041 There were partial logfiles - timestamp 0x pit 0x.

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43042 All logfiles complete - timestamp 0x pit 0x.

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43043 All logfiles complete - timestamp 0x rolling forward.

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43044 Consistent global timestamp not found - recovery is not possible.

ON-Bar was unable to find the correct log to restore in the emergency boot file.

ON-Bar 无法在紧急启动文件中找到要还原的正确日志。

Verify that all log files have been either backed up or salvaged and that each has an entry in the emergency boot file. If everything appears to be correct, contact GBase Technical Support.

验证所有日志文件是否已备份或挽救，并且每个日志文件中都有紧急启动文件中的一个条目。如果一切看起来都是正确的，请与 GBase 技术支持部门联系。

-43045 There are no storage space backups before the specified point in time - recovery is not possible.

The specified point-in-time value is earlier than the earliest backup entry in the emergency boot file.

指定的时间点值早于紧急引导文件中最早的备份项。

Verify that the point-in-time value entered on the command line is correct. If it is, the emergency boot file might have been corrupted or is missing and needs to be restored.

请验证在命令行中输入的时间点值是否正确。如果是，则紧急引导文件可能已损坏或丢失，需要还原。

-43046 boot_find_first_logs failed .

ON-Bar failed to find the correct log files to restore in the emergency boot file. This could happen if your system has run out of memory or if the emergency boot file is missing or corrupted.

在紧急启动文件中 ON-Bar 找不到要还原的正确日志文件。如果系统内存不足，或者紧急引导文件丢失或损坏，则可能发生这种情况。

Verify that there is sufficient memory in your system to complete a restore. If there is, the emergency boot file might need to be restored.

验证系统中是否有足够的内存来完成还原。如果存在，则可能需要还原紧急引导文件。

-43047 Send bootfile....

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43048 Error received from node "".

On-Bar attempted to communicate with and failed.

On-Bar 试图与通信，但失败。

Verify that all coservers on all nodes are running properly. Try the restore again. If it still fails, contact GBase Technical Support.

请验证所有节点上的所有协同服务器是否运行正常。再试一次还原。如果仍然失败，请与GBase 技术支持部门联系。

-43049 Error writing to the ON-Bar emergency boot file. Before attempting a restore, insert the following into :.

An error occurred when ON-Bar attempted to write information to the ON-Bar emergency boot file. The backup of this object succeeded;however, the object will not be included in a cold restore unless the specified information is added to the emergency boot file.

当 ON-Bar 试图将信息写入开机启动文件时发生错误。此对象的备份成功；但是，除非将指定的信息添加到紧急引导文件中，否则该对象将不会包含在冷还原中。

To include the object in a cold restore, ask your database server administrator to insert the specified data into the ON-Bar emergency boot file or try running onsmsync -b. (The emergency boot file is $GBS_HOME/etc/Bixbar\_<hostname>.<dbservernum> for GBase 8s Extended Parallel Server,$ GBS_HOME/etc/ixbar. for GBase 8s Dynamic Server on UNIX, or %GBS_HOME%\etc\ixbar.for Dynamic Server 9.2 or later on Windows.)若要将对象包含在冷还原中，请要求数据库服务器管理员将指定的数据插入 ON-Bar 紧急启动文件中，或尝试运行 onsmsync -b。（ GBase 8s Extended Parallel Server 的紧急引导文件为 $GBS_HOME/etc/Bixbar\_<hostname>.<dbservernum> UNIX上 GBase 8s 的紧急引导文件为$ GBS_HOME/etc/ixbar. 或者 Windows 上 Dynamic Server 9.2或更新的版本的紧急引导文件为 %GBS_HOME%\etc\ixbar.）-43050 Copy of old emergency bootfile saved in .

Before regenerating the emergency boot file, onsmsync makes a copy of the previous version. In case of catastrophic failure, this message tells you the name of this copy so you can put it back in place before running onsmsync again or starting a cold restore.

在重新生成紧急引导文件之前，onsmsync 会复制上一个版本。如果发生灾难性故障，此消息将告诉您此副本的名称，以便您可以在再次运行 onsmsync 或启动冷还原之前将其放回原处。

You cannot take any corrective action unless onsmsync fails. If onsmsync fails to finish writing the new boot file, copy the named file back to the original location.

除非 onsmsync 失败，否则不能采取任何纠正措施。如果 onsmsync 未能完成新启动文件的编写，请将命名的文件复制回原来的位置。

-43051 Copy of old emergency bootfile failed.

Before regenerating the emergency boot file, onsmsync makes a copy of the previous version. If this copying process fails, then this message is produced. An operating-system error should be written in the activity log.

在重新生成紧急引导文件之前，onsmsync 会复制上一个版本。如果此复制过程失败，则生成此消息。应在活动日志中写入操作系统错误。

Try to correct the operating-system error. ON-Bar will continue to regenerate the new emergency boot file.

尝试纠正操作系统错误。ON-Bar 将继续重新生成新的紧急启动文件。

-43052 Error parsing the emergency bootfile .

ON-Bar and onsmsync read information about backups from the emergency boot file for various reasons. The emergency boot file might be corrupt.

ON-Bar 和 onsmsync 出于各种原因从紧急引导文件中读取有关备份的信息。紧急启动文件可能已损坏。

ON-Bar and onsmsync will ignore corrupted backup entries while parsing the emergency boot file. Contact GBase Technical Support.

在解析紧急引导文件时，ON-Bar 和 onsmsync 将忽略损坏的备份条目。与 GBase 技术支持部门联系。

-43060 The buffer exceeded maximum allowed limit. Changing buffer size to .

Transport buffer size is limited by the X/Open Backup Services API specification. ON-Bar is changing the buffer size to the maximum allowed value.

传输缓冲区大小受到 X/Open Backup Services API 规范的限制。ON-Bar 正在将缓冲区大小更改为最大允许值。

-43061 BAR_MAX_BACKUP has been reduced to to avoid allocating more than SHMTOTAL KB.

The value of BAR_MAX_BACKUP multiplied by BAR_XFER_BUF_SIZE and BAR_NB_XPORT_COUNT will exceed the amount of shared memory reserved by the SHMTOTAL parameter in the ONCONFIG file. This ON-Bar process will use a lower BAR_MAX_BACKUP value to avoid exceeding this boundary.

BAR_MAX_BACKUP 的值乘以 BAR_XFER_BUF_SIZE 和 BAR_NB_XPORT_COUNT 的值将超过ONCONFIG 文件中 SHMTOTAL 参数所保留的共享内存量。此 ON-Bar 进程将使用较低的BAR_MAX_BACKUP 值，以避免超出此边界。

Either raise the amount of shared memory the database server is allowed to use by increasing SHMTOTAL or lower the value of BAR_MAX_BACKUP,BAR_XFER_BUF_SIZE, or BAR_NB_XPORT_COUNT.

要么通过增加 SHMTOTAL 来提高数据库服务器允许使用的共享内存量，要么降低BAR_MAX_BACKUP、BAR_XFER_BUF_SIZE 或 BAR_NB_XPORT_COUNT 的值。

-43062 Unable to read parameters from $GBS_DATA/conf/onconfig(UNIX) or %GBS_HOME%\etc%ONCONFIG% (Windows).

The ONCONFIG file is inaccessible. It might be missing or have incorrect permission values, or the file contents might be corrupted.

无法访问 ONCONFIG 文件。它可能丢失或具有不正确的权限值，或者文件内容可能已损坏。

Verify that an ONCONFIG file exists and that the permissions for it are correct. For details, see the Administrator's Reference.

验证是否存在 ONCONFIG 文件，以及该文件的权限是否正确。有关详细信息，请参阅管理员的参考资料。

-43075 Unable to open file .

The file or its directory permissions prevent it from being created or opened.

该文件或其目录权限阻止它被创建或打开。

Verify the permissions on the file and its directory.

请验证该文件及其目录的权限。

-43076 Error while reading data from the file.

An error occurred while data was read from the file. The file might be corrupted.

从文件读取数据时发生错误。文件可能已损坏。

-43077 Unable to create . There may not be enough space.

Not enough disk space is available for chunk creation.

没有足够的磁盘空间用于 chunk 创建。

Free some disk space or create a file for this chunk.

请为该 chunk 释放一些磁盘空间或创建一个文件。

-43078 Open or close failed on file , errno = .

An operating-system error prevents the file from being created or opened.

操作系统错误阻止文件被创建或打开。

Correct the error and retry your command.

更正错误并重试命令。

-43079 Unable to open file .

The file or its directory permissions prevent it from being created or opened.

文件或其目录权限阻止创建或打开该文件。

Verify the permissions on the file and its directory.

验证文件及其目录的权限。

-43080 Process received signal .

Process will exit after cleanup.

An ON-Bar process received a signal. Someone might have intentionally terminated the ON-Bar process with signal 2 (SIGINT), 3 (SIGQUIT), 9(SIGKILL), or 15 (SIGTERM). ON-Bar is attempting to exit gracefully.

ON-Bar 进程收到信号。有人可能故意用信号2(SIGINT)、3(SIGQUIT)、9(SIGKILL)或 15(SIGTERM)终止 ON-Bar 进程。ON-Bar 正试图优雅地退出。

If the signal that terminated the ON-Bar process is not one of the signals listed above, contact GBase Technical Support.

如果终止 ON-Bar 进程的信号不是上面列出的信号之一，请与 GBase 技术支持部门联系。

-43081 Closing unused end of pipe failed.

The system call to close the unused end of the backup and restore filter pipe failed.

系统调用关闭备份和恢复筛选管的未使用的末端失败。

This error is internal. Retry the operation and if it continues to fail,contact GBase Support.

此错误为内部错误。重试操作，如果操作继续失败，请与 GBase 支持部门联系。

-43082 Writing to the backup and restore filter failed with error .

Writing data to the backup and restore filter pipe failed with the given error.

由于给定的错误，将数据写入备份和恢复筛选器管道失败。

Check the log of the filter program for possible errors.

If the cause of the error is still unclear, contact technical support for your filter or GBase Support.

请检查过滤程序的日志中是否存在可能的错误。如果错误的原因仍不清楚，请与过滤器或GBase 技术支持部门联系。

-43090 Out of memory.

ON-Bar was unable to allocate more memory.

ON-Bar 无法分配更多内存。

Reduce the number of processes that are running at the same time as ON-Bar,if possible, or ask your system administrator either to increase your swap space or to install more memory in your system.

如果可能的话，减少在同一时间运行的进程数量，或者要求系统管理员增加交换空间或在系统中安装更多内存。

-43091 Unable to attach to shared memory.

Unable to initialize a shared-memory connection to the database server.

无法初始化到数据库服务器的共享内存连接。

Either the database shared memory has not been initialized or the maximum number of users are already using the system.

数据库共享内存尚未初始化或最大用户数已在使用该系统。

-43092 Unable to set process group id.

If you are doing a parallel backup or restore, ON-Bar tries to use setpgid() to group together all the processes. This error occurs if setpgid() fails.

如果您正在进行并行备份或还原，ON-Bar 尝试使用 setpgid() 将所有进程分组。如果setpgid() 失败，则会发生此错误。

Retry the backup or restore. If it fails again, contact GBase Technical Support.

重试备份或还原。如果再次失败，请与 GBase 技术支持部门联系。

-43100 No Storage Manager instances were defined in ONCONFIG.

The list of available storage-manager instances has not been defined in the ONCONFIG file. Backup and restore operations will be queued until a storage manager is defined.

在 ONCONFIG 文件中没有定义可用存储管理器实例的列表。备份和恢复操作将排队，直到定义了存储管理器。

Define storage-manager instances in your ONCONFIG file.

请在 ONCONFIG 文件中定义存储管理器实例。

-43101 Unable to create a session: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43102 Unable to destroy a session: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43103 Session complete.

The specified backup and restore session has completed.

指定的备份和还原会话已经完成。

-43104 Session complete with error .

The specified backup and restore session has completed with an error.

指定的备份和还原会话已完成，但有错误。

-43105 Unable to register a new worker process: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43106 Unable to deregister a new worker process: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43107 Unable to get the next event: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43108 Received an invalid event from the database server:.

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43109 Unable to create the logstream backup session: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43110 Unable to start the logical log backup: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43111 Unable to get logical log backup data from the database server: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43112 Unable to close the logical log backup: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43113 Unable to commit the logical log backup: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43114 Unable to create the storage space backup session:.

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43115 Unable to start the storage space backup: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43116 Unable to get storage space backup data from the database server: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43117 Unable to close the storage space backup: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43118 Unable to commit the storage space backup: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43119 Unable to create the storage space restore session:.

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43120 Unable to start the storage space restore: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43121 Unable to write storage space restore data to the database server: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43122 Unable to close the storage space restore: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43123 Unable to commit the storage space restore: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43124 Unable to create the logical log restore session:.

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43125 Unable to start the logical log restore: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43126 Unable to write logical log restore data to the database server: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43127 Unable to close the logical log restore: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43128 Unable to commit the logical log restore: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43129 Unable to create the salvage logs session: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43130 Unable to start logical log salvage: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43131 Unable to get logical log salvage data from disk: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43132 Unable to commit the logical log salvage: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, GBase contact Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43133 Unable to open logical log placement: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43134 Unable to close logical log placement: .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43135 Error suspending session : .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43136 Error resuming session : .

An error occurred in the database server.

数据库服务器发生错误。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43137 The log backup may have made at least 1 blobspace unrestorable.

A log was backed up when a blobspace was down. The transactions in the logs(transactions that involve TEXT or BYTE data) might not be restorable.

当一个 blobspace 关闭时，会备份一个日志。日志中的事务（涉及 TEXT 或 BYTE 数据的事务）可能无法恢复。

You might have to re-create the TEXT or BYTE data after the restore is complete.

还原完成后，您可能必须重新创建文本或字节数据。

-43138 Unable to allocate the transport buffer: .

An error occurred when the database server tried to allocate the transport buffers.

数据库服务器试图分配传输缓冲区时出错。

Note all circumstances, save a copy of the ON-Bar activity log and database server message log, and contact GBase Technical Support.

请注意所有情况，保存 ON-Bar 活动日志和数据库服务器消息日志的副本，并与 GBase技术支持部门联系。

-43139 Unable to free the transport buffer: .

An error occurred when the database server tried to free the transport buffers. This error might occur in onbar workers if the database server is brought down.

数据库服务器试图释放传输缓冲区时出错。如果关闭数据库服务器，onbar workers 可能会发生此错误。

In all other cases, note the circumstances, save a copy of the ON-Bar activity log and database server message log, and contact GBase Technical Support.

在所有其他情况下，请注意情况，保存 ON-Bar 活动日志和数据库服务器消息日志的副本，并与 GBase 技术支持部门联系。

-43140 Due to the previous error, logical restore will not be attempted.

An error occurred in the physical restore. ON-Bar does not attempt a logical restore to give the user a chance to fix the problem. If the physical restore was cold, the database server is left in fast recovery mode.

物理还原中发生错误。ON-Bar 不尝试进行逻辑恢复以给用户一个修复问题的机会。如果物理恢复是冷的，则数据库服务器将保持快速恢复模式。

You have the following two choices:你有如下两种选择：1. Fix the problem and finish the restore with onbar -r or onbar -r <failed_space>. ON-Bar re-attempts to restore the failed storage space.

1）修复此问题，并使用 onbar -r 或 onbar -r <failed_space>。 ON-Bar 重新尝试恢复失败的存储空间来完成还原。

Finish the restore with onbar -r -l. ON-Bar performs a logical restore but leaves off-line any storage spaces that are not yet physically restored.

2）用 onbar -r -l 完成恢复。ON-Bar 执行逻辑恢复，但保留任何尚未物理恢复的存储空间。

-43143 WARNING: Storage space is being dropped and cannot be backed up.

On-Bar found that the storage space is in the process of being dropped.

On-Bar 发现存储空间正在被删除的过程中。

Verify that the storage space has been dropped or is in the process of being dropped.

请验证存储空间是否已被删除或正在被删除。

-43150 Must restore logical logs from or later.

The user wants to stop the restore at too early a logical log. A storage-space backup occurred after the log that the user specified.

用户希望在逻辑日志太早时停止还原。在用户指定的日志后发生存储空间备份。

Retry the restore up to the specified logical log or later.

请重新尝试还原到指定的逻辑日志或更高版本。

-43151 Cannot warm restore critical media: . Skipped restore of this space.

Critical media (root dbspace or any dbspace that contains a logical or physical log) cannot be restored if the database server is online. This space will be skipped.

如果数据库服务器处于联机状态，则无法还原关键媒体（root dbspace 或包含逻辑或物理日志的 dbspace）。这个空间将被跳过。

-43152 Begin cold level restore (Storage Manager copy ID: ).

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43153 Completed cold level restore .

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43154 Begin fake backup.

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43155 Completed fake backup.

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43156 Fake backup failed. Contact GBase Technical Support.

请与 GBase 技术支持部门联系。

-43157 Begin level backup .

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43158 Completed level backup (Storage Manager copy ID: ).

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43159 Begin salvage for log .

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43160 Completed salvage of logical log (Storage Manager copy ID: ).

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43161 off-line blobspaces () were found while salvaging logical logs.

The logical-log backup of changes to a blobspace requires the blobspace to be online. Any blobspace that is off-line during a logical-log salvage(which means the blobspace was off-line before the database server failed)is no longer restorable using ON-Bar.

对 blobspace 的更改的逻辑日志备份要求 blobspace 处于联机状态。任何在逻辑日志挽救过程中处于脱机状态的空白（这意味着在数据库服务器故障之前 blobspace 处于脱机状态）不再可以使用 ON-Bar 恢复。

Re-create the blobspace and reload it as recommended in the Administrator's Guide.

按照“管理员指南”中的建议，重新创建 blobspace 并重新加载它。

-43162 Begin warm level restore (Storage Manager copy ID: ).

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43163 Completed warm level restore .

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43164 Begin backup logical log .

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43165 Completed backup logical log (Storage Manager copy ID: ).

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43166 Begin restore logical log (Storage Manager copy ID: ).

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43167 Completed restore logical log .

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43168 ON-Bar suspended the logical restore on log (expected to restore to ).

ON-Bar was able to restore up through log file x.

ON-Bar 能够通过日志文件 x 进行恢复。

To restore all data, however, you also need to restore log files x + 1 through y. Query your storage manager to find out if the backups of these log files exist and if they are restorable. If the log files are not restorable or you do not want to restore them, issue the following commands to force the logical restore to end:但是，要恢复所有数据，还需要还原日志文件 x + 1 到 y。查询存储管理器，找出这些日志文件的备份是否存在，以及它们是否可恢复。如果日志文件不可恢复或不希望还原它们，则发出以下命令强制逻辑恢复结束：onmode -k; oninit Otherwise, issue onbar -r -l to resume the logical restore.

否则，发出 onbar -r -l 以恢复逻辑恢复。

-43169 You must restore all critical storage spaces for a cold restore.

A cold restore was attempted that did not include the critical storage spaces.

尝试了不包含关键存储空间的冷还原。

Try the restore again, but include the root dbspaces and all other critical dbspaces, if any.

再次尝试还原，但包括 root dbspace 和所有其他关键 dbspaces（如果有的话）。

-43170 ON-Bar could not find the proper log from which to begin the logical restore.

Either no logical-log restore is needed or a logical-log backup is not restorable.

要么不需要逻辑日志恢复，要么逻辑日志备份不可恢复。

If the database server is not in quiescent or online mode, contact GBase Technical Support.

如果数据库服务器没有处于静止或联机模式，请与 GBase 技术支持部门联系。

-43171 Cannot restart a warm logical restore.

ON-Bar cannot restart a logical restore with the database server in online or quiescent mode.

ON-Bar 无法在联机或静态模式下重新启动数据库服务器的逻辑还原。

Bring down the database server and restart the restore.

关闭数据库服务器并重新启动还原。

-43172 Completed external restore.

This message is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43173 External restore failed.

An error occurred in the database server.

数据库服务器发生错误。

Refer to the ON-Bar activity log or database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅 ON-Bar 活动日志或数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase 技术支持部门联系。

-43174 percent of has been backed up.

This message provides progress feedback for backup as a percentage of dbspace size.

此消息以 dbspace 大小的百分比提供备份进度反馈。

-43175 percent of has been restored.

This message provides progress feedback for restore as a percentage of dbspace size.

此消息提供恢复进度反馈，作为 dbspace 大小的百分比。

-43176 buffers of have been restored.

This is an ON-Bar progress message that reports the number of buffers restored.

这是一个 ON-Bar 进度消息，它报告恢复的缓冲区的数量。

-43177 Physical restore complete. Logical restore required before work can continue. Use 'onbar -r -l' to do logical restore.

This restore was a physical-only restore, or the logical restore failed.

此还原是纯物理还原，或逻辑还原失败。

Perform a logical restore.

执行逻辑还原。

-43178 The data returned from the Storage Manager for restore is incomplete.

The amount of data in the buffer that the storage manager returned for the restore is not a multiple of the database server page size(2 kilobytes, 4 kilobytes, or 8 kilobytes, depending on your system and configuration). A restore requires complete pages of data.

存储管理器为恢复返回的缓冲区中的数据量不是数据库服务器页大小的倍数(2 KB、4 KB或 8 KB，取决于您的系统和配置)。还原需要完整的数据页。

Check your storage manager for possible errors. Verify that all the storage media are complete and usable and that all the storage devices are functional and online.

检查您的存储管理器是否可能出现错误。验证所有存储介质是否完整和可用，以及所有存储设备是否正常且在线。

-43179 Continuous logical log backup sessions cannot be destroyed. Use onbar off "Log backup ".

An attempt to destroy a continuous logical-log backup session (Log backup) was made. This action is not allowed.

尝试销毁连续逻辑日志备份会话(日志备份 )。此操作是不允许的。

If you need to stop a logical-log backup session for some reason, use'onbar off "Log backup "', in which is the number of the coserver (1, 2, 3, and so on), to temporarily suspend the session.

You can use 'onbar on "Log backup "' to resume the session when the problem is resolved. Do not use 'onbar -d "Log backup "'to destroy the session.

如果出于某种原因需要停止逻辑日志备份会话，请使用 'onbar off "Log backup"'，其中是 coserver (1, 2, 3 等等)的数量，来临时挂起会话。当问题解决时，可以使用 'onbar on "Log backup "' 来恢复会话。不要使用 'onbar -d "Log backup "' 来破坏会话。

-43180 One of the spaces externally restored on coserver was backed up after .

ON-Bar has determined the most recent time to which all coservers can be restored and has reported the internal global time stamp in the error message. One of the storage spaces that was externally restored on the named coserver was backed up after that time. Hence a logical restore cannot return all storage spaces to a consistent state.

ON-Bar 已经确定了最近的时间，所有协同服务器都可以恢复到这个时间，并在错误消息中报告了内部全局时间戳。在此之后，外部恢复到命名的协同服务器上的存储空间之一被备份。因此，逻辑还原不能将所有存储空间返回到一致状态。

Use the ctime() function to convert the global time stamp to a clock time. Then check that all the external backups used in the external restore of data on the named coserver were made before that time. Any space that was restored from too recent a backup needs to be re-restored from an older backup. Then try the ON-Bar external restore command again.

使用 ctime() 函数将全局时间戳转换为时钟时间。然后检查在命名的协同服务器上数据的外部恢复中使用的所有外部备份是否在此之前完成。从太近期的备份恢复的任何空间都需要从旧备份中重新还原。然后再次尝试 ON-Bar 外部还原命令。

-43181 Completed logical restore.

This message is an ON-Bar progress message.

此消息是 ON-Bar 进度消息。

No action is required.

不需要操作。

-43182 Completed whole-system restore.

This message is an ON-Bar progress message.

此消息是 ON-Bar 进度消息。

No action is required.

不需要操作。

-43183 Logical logs will not be backed up / salvaged because LTAPEDEV value is .

If the LTAPEDEV value in your ONCONFIG file is /dev/null on UNIX or NUL on Windows, logical-log backups are not performed. You set these special values to tell the database server and ON-Bar not to perform any logical-log backups. Data in the logical logs cannot be restored.

如果 ONCONFIG 文件中的 LTAPEDEV 值在 UNIX 上为/dev/null，在 Windows 上为 NUL，则不执行逻辑日志备份。将这些特殊值设置为告知数据库服务器和栏上不执行任何逻辑日志备份。无法还原逻辑日志中的数据。

Set the LTAPEDEV value to something other than /dev/null on UNIX or NUL on Windows or to blank if you want to perform logical-log backups.

If you do not want any logical-log backups, you can restore only from whole-system backups, performed with the following command:如果要执行逻辑日志备份，则将 LTAPEDEV 值设置为 UNIX 上的 /dev/null 或 Windows上的 NUL 以外的值，或者设置为空。如果不需要任何逻辑日志备份，则只能通过以下命令从整个系统备份恢复：onbar -b -w Also, you must restore with the following command:此外，还必须使用以下命令进行还原：onbar -r -w -p-43184 The transport buffer size has changed since the backup.

Changing buffer size to for restore.

A space or a logical log must be restored using the same transport buffer size as was used when the space or log was backed up. ON-Bar automatically detects that the buffer size has changed and uses the buffer size from the backup.

必须使用与备份空间或日志时相同的传输缓冲区大小来还原空间或逻辑日志。On-Bar 自动检测缓冲区大小是否已更改，并从备份中使用缓冲区大小。

-43185 A change in physical configuration has occurred. A level-0 backup of <space_name> is being performed.

The physical configuration of the database server has changed. For example, a storage space, chunk, or logical-log file has been added or dropped, or the physical log has been moved. To guarantee a successful restore, a level-0 backup of the affected space and the root dbspace is being performed now.

数据库服务器的物理配置已更改。例如，添加或删除了存储空间、chunk 或逻辑日志文件，或者移动了物理日志。为了保证恢复成功，现在正在执行受影响空间和 root dbspace 的级别 -0 备份。

No action is required.

不需要操作。

-43186 The logical log is full on one or more coservers. ON-Bar's attempt to back up these logs failed. A logical-log backup is needed.

The logical log is full on one or more coservers. Processing will be blocked until these logical logs are backed up.

逻辑日志已满在一个或多个协同服务器上。在备份这些逻辑日志之前，处理将被阻塞。

Perform a logical-log backup. Processing will continue after this backup is complete.

请执行逻辑日志备份。此备份完成后，处理将继续进行。

-43187 ON-Bar received an error/signal. The onbar session will abort after cleanup.

If any of the ON-Bar processes encounters a non-fatal error and if BAR_RETRY is set to ABORT(0), the parent process will not create any new child processes. If the parent process receives a signal, the process ignores the BAR_RETRY value and then aborts. In both cases, the ON-Bar child processes that are running will continue to completion.

如果任何列上进程遇到非致命错误，如果 BAR_RETRY 设置为 ABORT(0)，父进程将不会创建任何新的子进程。如果父进程收到信号，则进程将忽略 BAR_RETRY 值，然后中止。在这两种情况下，正在运行的列子进程将继续完成。

Rerun the backup or restore command.

请重新运行备份或还原命令。

-43189 Logical Logs cannot be restored because LTAPEDEV value is.

If the LTAPEDEV parameter value in your ONCONFIG file is /dev/null (UNIX)or NUL (NT) or blank, logical log restore cannot be performed. These are special values that you set to tell the server and ON-Bar that log backups are not desired. Data in the logical log cannot be restored.

如果您的 ONCONFIG 文件中的 LTAPEDEV 参数值为 /dev/null(UNIX) 或 NUL (NT) 或空白，则无法执行逻辑日志还原。无法还原逻辑日志中的数据。

Set the LTAPEDEV parameter value to something other than /dev/null (UNIX)or NUL (NT) or blank if logical log restores are desired. If logical log restores are not desired use the -w and -p options with ON-Bar commands to perform whole system, physical-only restore.

如果需要逻辑日志还原，则将 LTAPEDEV 参数值设置为 /dev/null(UNIX) 或 NUL (NT)或空白。如果不需要逻辑日志还原，则使用 -w 和 -p 选项和 ON-Bar 命令执行整个系统的物理恢复。

-43190 WARNING: Storage space names with path will not be supported from next release onwards. Correct this in .

Only space (dbspace, blobspace, and so forth) names should be specified to ON-Bar in a file or command line. ON-Bar will backup all the chunks belonging to the spaces.

在文件或命令行中，只应将空间(dbspace、blobspace 等)名称指定为 ON-Bar。 ON-Bar将备份属于空间的所有 chunk 。

Correct the file to specify storage space name without path prefixing.

请更正该文件以指定存储空间名称，而无需路径前缀。

-43194 WARNING: XBSA connect to storage manager failed.

Continuing external restore.

Either the storage manager is not running or it has not been installed and configured.

存储管理器没有运行，或者没有安装和配置。

For pure external physical-only restore, no storage manager is needed.

Therefore, the external restore is continued at this point.

However, a storage manager may be necessary later if logical logs need to be restored from backup media.

对于纯粹的外部物理恢复，不需要存储管理器。因此，此时继续进行外部恢复。但是，如果需要从备份媒体还原逻辑日志，则可能需要稍后使用存储管理器。

-43200 Shared memory not initialized.

The database server is not running.

数据库服务器未运行。

Start the database server. For instructions, see the Administrator's Guide.

请启动数据库服务器。有关说明，请参阅“管理员指南”。

-43201 The database server has crashed or been shutdown. Exiting...

The database server has failed or has been shut down while one or more ON-Bar worker processes are still running. The ON-Bar worker processes will be automatically shut down.

当一个或多个 ON-Bar 工作进程仍在运行时，数据库服务器已失败或已关闭。ON-Bar 工作进程将自动关闭。

-43202 Unable to determine mode of all coservers.

It was not possible to determine what mode each coserver is in (online,quiescent, off-line, or microkernel).

无法确定每个 coserver 所处的模式（online、quiescent、off-line 或 microkernel）。

Verify that all coservers are running and that the coservers are communicating with each other properly.

请确认所有的协同服务器都在运行，并确认各协同服务器是否正确地进行了通信。

-43203 Not all coservers are in a compatible mode.

Not all coservers are in the same mode. Each coserver must be in a mode compatible to all the others. For example, all the coservers must be in microkernel mode to perform a cold restore. On-line and quiescent modes are compatible, so a backup or warm restore can be performed as long as all coservers are in one of these two modes.

并不是所有的协同服务器都处于相同的状态。每个协同服务器必须处于与所有其他服务器兼容的模式中。例如，所有协同服务器必须处于 microkernel 模式下才能执行冷恢复。

On-line 模式和 quiescent 模式是兼容的，所以只要所有协同服务器都处于这两种模式中的一种，就可以执行备份或温还原。

Change all coservers to the same mode or to compatible modes.

请将所有协同服务器更改为相同的模式或兼容的模式。

-43204 ON-Bar is waiting for the database server to exit fast recovery mode.

After finishing the logical restore phase of a cold restore, the database server enters fast recovery mode. ON-Bar waits for fast recovery to complete before cataloging the activity of the cold restore.

在完成冷还原的逻辑恢复阶段后，数据库服务器进入快速恢复模式。在编目冷还原活动之前， ON-Bar 等待快速恢复完成。

-43205 Failed to connect to the sysmaster or sysutils database.

Wait until these databases are created and try again.

Either the sysmaster or sysutils database has not been created.

尚未创建 sysmaster 或 sysutils 数据库。

Monitor the database server message log until the following messages appear:请监视数据库服务器消息日志，直到出现以下消息："'sysmaster' database built successfully""'sysutils' database built successfully"Then retry your command.

然后重试您的命令。

If one or both of these messages fail to appear, contact GBase Technical Support.

如果其中一条或两条消息都没有出现，请与 GBase 技术支持部门联系。

-43206 An attempt to change the database server operating mode failed: .

An error occurred during an attempt to change the database server operating mode.

试图更改数据库服务器操作模式时发生错误。

Check the database server message log for errors.

请检查数据库服务器消息日志中是否有错误。

-43207 Unable to open connection to database server: .

The database server is in an incorrect operating mode.

数据库服务器处于不正确的操作模式。

Bring the database server to the correct mode. For a backup, the database server should be in online or quiescent mode. For a warm restore, the database server should be in online, quiescent, backup,or recovery mode. For a cold restore, the database server should be off-line for GBase 8s Dynamic Server 9.2x or later and in microkernel mode for GBase 8s Extended Parallel Server. To change the database server mode, use the onmode or oninit command.

使数据库服务器进入正确的模式。对于备份，数据库服务器应该处于 online 或quiescent 模式。对于温还原，数据库服务器应该处于 online、quiescent、backup 或recovery 模式。对于冷还原，对于 GBase 8s Dynamic Server 9.2x 或更高版本，数据库服务器应该处于 off-line 状态，对于 GBase 8s 扩展并行服务器，数据库服务器应该处于 microkernel 模式。若要更改数据库服务器模式，请使用 onmode 或 oninit 命令。

-43208 Fatal error initializing ASF; asfcode = <asfcode_value>An error occurred during initialization of the ASF layer.

初始化 ASF 层时发生错误。

To determine the cause of the error, refer to the ASF error codes and then rerun the backup or restore command.

若要确定错误原因，请参考 ASF 错误代码，然后重新运行备份或还原命令。

-43210 ON-Bar failed to initialize the XCC communications mechanism().

An error occurred in an attempt to initialize communications between coservers.

试图初始化协同服务器之间的通信时出错。

Refer to the database server message log for more information. If the cause of the error is still unclear, contact GBase Technical Support.

有关详细信息，请参阅数据库服务器消息日志。如果错误的原因尚不清楚，请与 GBase技术支持部门联系。

-43211 The onbar process is waiting for onbar_m processes to connect at .

In a cold restore on GBase 8s Extended Parallel Server or GBase 8s Dynamic Server with Advanced Decision Support and Extended Parallel options,the ON-Bar process that the user started launches onbar_m processes on various nodes of the MPP to collect data required to perform the cold restore. Each onbar_m process needs to connect to the ON-Bar process using a communications address that the ON-Bar process devised. This message names the address.

在具有高级决策支持和扩展并行选项的 GBase 8s 扩展并行服务器或 GBase 8s 动态服务器上的冷还原中，用户开始在 MPP 的各个节点上启动 onbar_m 进程以收集执行冷恢复所需的数据。每个 onbar_m 进程都需要使用 ON-Bar 进程设计的通信地址连接到 ON-Bar进程。这条消息为地址命名。

If you are starting onbar_m by hand, type the address that the message named on the onbar_m command line.

如果要手动启动 onbar_m，请键入 onbar_m 命令行上命名的消息的地址。

-43212 Waiting for onbar_m processes to connect...

Several onbar_m processes have just started, and ON-Bar is waiting for all of them to come up.

几个 onbar_m 进程刚刚开始，On-Bar 正在等待所有这些进程的出现。

-43213 All onbar_m processes have connected.

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43214 The onbar_m process started on node failed with status : .

One of the onbar_m processes failed to connect to ON-Bar.

其中一个 onbar_m 程未能连接到 ON-Bar。

If this message occurs once, try to start an onbar_m process on the named node by hand as user gbasedbt. If this message occurs repeatedly, contact GBase Technical Support with the status information in the error message and with the contents of your ONCONFIG file.

如果此消息只发生一次，请尝试以 gbasedbt 用户的身份在指定节点上启动 onbar_m 进程。如果此消息重复发生，请与 GBase 技术支持部门联系，了解错误消息中的状态信息和 ONCONFIG 文件的内容。

-43215 The onbar_m process on node sent an unexpected message ( instead of ).

This message indicates either an error in the ON-Bar software or an onbar_m process that did not start correctly.

此消息表示 On-Bar 软件中的错误或 onbar_m 进程未正确启动。

Contact GBase Technical Support.

请与 GBase 技术支持联系。

-43216 The ON-Bar process received a polling error from XCC( : ).

An error occurred in inter-coserver communications.

在协同服务器之间的通信中发生错误。

If this message occurs once, try to start the cold restore again. If this message occurs repeatedly, contact GBase Technical Support with the status information in the error message and with the contents of your ONCONFIG file.

如果此消息发生一次，请再次启动冷还原。如果此消息重复发生，请与 GBase 技术支持部门联系，了解错误消息中的状态信息和 ONCONFIG 文件的内容。

-43217 The ON-Bar process failed to send an XCC message( : ).

An error occurred in inter-coserver communications.

在协同服务器之间的通信中发生错误。

如果此消息发生一次，请再次启动冷还原。如果此消息重复发生，请与 GBase 技术支持部门联系，了解错误消息中的状态信息和 ONCONFIG 文件的内容。

-43218 The ON-Bar process failed to receive an XCC message( : value-2).

An error occurred in inter-coserver communications.

在协同服务器之间的通信中发生错误。

如果此消息发生一次，请再次启动冷还原。如果此消息重复发生，请与 GBase 技术支持部门联系，了解错误消息中的状态信息和 ONCONFIG 文件的内容。

-43219 A rename chunk restore failed. Server is not in off-line mode.

Restore with chunk rename can only be done as cold restore when the server is off-line.

使用 chunk 重命名的还原只能在服务器 off-line 时作为冷还原来完成。

To do a restore with chunk rename, bring the server off-line and do a cold restore.

若要使用 chunk 重命名进行还原，请将服务器 off-line 并进行冷还原。

-43225 There may be duplicate copy ID's in use for backup objects in the sysutils database. More than one backup object may share the same copy ID. Expiring backups using onsmsync in this scenario may cause backup objects that should not be expired to be removed from the PSM storage manager.

The number of unique ins_aid, ins_oid pairs for backup objects(act_type 1 or 5) does not match the number of unique copy ID's(ins_copyid_hi, ins_copyid_lo) for the backup objects in sysutils.

This may indicate that there is more than one backup object with the same copy ID in sysutils.

备份对象（act_type 1 或 5）的 unique ins_aid、 ins_oid 对的数量与 sysutils 中备份对象的唯一副本 ID（ins_copyid_hi，ins_copyid_lo）的数量不匹配。这可能表明sysutils 中有多个具有相同副本 ID 的备份对象。

Duplicate copy ID's in sysutils may result from exporting/importing backup objects from one PSM storage manager to another PSM storage manager where the same object ID's (copy ID's) in use in sysutils are now being used for new backups. In such cases,onsmsync may not be able to distinguish between the two objects during expiration processing. Manual clean-up may be needed until the sysutils info and the PSM storage manager catalog are compatible.

在 sysutils 中复制副本 ID 的原因可能是将备份对象从一个 PSM 存储管理器导出/导入到另一个 PSM 存储管理器，其中在 sysutils 中使用的相同对象 ID (复制 ID)正在用于新的备份。在这种情况下，onsmsync 可能无法在过期处理期间区分这两个对象。可能需要手动清理。sysutils info 和 PSM 存储管理器目录是兼容的。

To skip the check for duplicate copy ID's in sysutils, set the environment variable BAR_SKIP_DUPS_CHECK=1 and re-run the onsmsync expiration command.

若要跳过 sysutils 中重复复制 ID 的检查，请设置环境变量BAR_SKIP_DUPS_CHECK=1 ，然后重新运行 onsmsync expiration 命令。

-43230 The problem just reported is not fatal; processing will continue.

ON-Bar just reported a warning or error in the activity log. However, this problem is not fatal. ON-Bar will continue processing, either retrying or using a different algorithm to complete the task. Other unrecoverable errors might occur later.

ON-Bar 刚刚报告了活动日志中的警告或错误。然而，这个问题并不致命。ON-Bar 将继续处理，可以重试，也可以使用不同的算法来完成任务。其他不可恢复的错误以后可能会发生。

Watch for further errors. Be aware that further processing may take longer than expected.

注意进一步的错误。请注意，进一步的处理可能需要比预期更长的时间。

-43231 An unexpected error occurred: .

Several possible causes exist for this error, including operating-system failures, version incompatibilities, and software errors.

导致此错误的原因有几个，包括操作系统故障、版本不兼容和软件错误。

Verify that the versions of the database server, ON-Bar, and the storage manager are compatible. For a list of compatible versions, refer to the GBase 8s Backup and Restore Guide, release notes, machine notes, or storage manager documentation.

验证数据库服务器、 ON-Bar 和存储管理器的版本是否兼容.有关兼容版本的列表，请参阅 GBase 8s 备份和还原指南、发行说明、机器注释或存储管理器文档。

If the versions are compatible, try to stop the backup and restore process or processes and restart them.

如果版本兼容，请尝试停止备份和还原进程并重新启动它们。

If the error persists, note all circumstances, save a copy of the ON-Bar and database server message logs, and contact GBase Technical Support.

如果错误仍然存在，请注意所有情况，保存 ON-Bar 和数据库服务器消息日志的副本，并与 GBase 技术支持部门联系。

-43232 The error just encountered may be transitory. ON-Bar is retrying the last statement.

ON-Bar just reported a warning or error. This problem, however, might be caused by another process and might clear up after the other process continues. ON-Bar will automatically retry the failed statement.

ON-Bar 刚刚报告了一个警告或错误。但是，这个问题可能是由另一个进程引起的，并可能在另一个进程继续后清除。ON-Bar 将自动重试失败语句。

Monitor for further errors. If the automatic retry fails, retry the backup or restore command.

监视进一步的错误。如果自动重试失败，请重试备份或还原命令。

-43233 Linked list operation failed .

A linked list operation failed.

链接列表操作失败。

This error is internal. Retry the operation and if it continues to fail, contact GBase Technical Support.

此错误为内部错误。重试操作，如果操作继续失败，请与 GBase 技术支持部门联系。

-43234 New BAR_DEBUG level recognized: old value was , new value is .

The BAR_DEBUG parameter in the ONCONFIG file has changed values or debug level is specified on command line. The new debug level value will be used for further tracing.

ONCONFIG 文件中的 BAR_DEBUG 参数更改了值，或者在命令行上指定了调试级别。新的调试级别值将用于进一步跟踪。

-43240 Process successfully forked.

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43241 Process completed.

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43242 The ON-Bar process exited without returning an exit code.

An ON-Bar child process was started and exited, but the parent process could not find its exit code. This situation can occur if too many child processes exit at the same time.

启动并退出了“ON-Bar 子进程”，但父进程无法找到其退出代码。如果同时退出太多子进程，则会发生这种情况。

ON-Bar proceeds as if this child process were successful and cataloged its activity properly. Check the activity log for any evidence whether this process encountered an error. Make sure the bar_action and bar_object tables in the sysutils database correctly reflect the success or failure of this process.

ON-Bar 继续进行，就好像这个子进程是成功的，并正确地对其活动进行了分类。检查活动日志中是否有此过程遇到错误的任何证据。确保 sysutils 数据库中的 bar_action 和bar_object 表正确地反映了此过程的成功或失败。

-43243 The process is participating in a backup/restore session but is suspended.

The database administrator, computer operator, or storage manager sent SIGSTOP or SIGTSTP, usually a CTRL-Z or CTRL-Y, to this process. Presumably this action was taken to halt processing temporarily during resolution of a problem.

数据库管理员、计算机操作员或存储管理器向此进程发送SIGSTOP或SIGTSTP(通常为CTRL-Z或CTRL-Y)。据推测，采取这一是为了在解决问题期间暂时停止处理。

Send SIGCONT to this process (kill -CONT ) to allow the process to complete its backup or restore, SIGTERM to stop this particular process, or SIGQUIT to end the whole backup or restore session.

将 SIGCONT 发送到此进程（kill -CONT ）以允许进程完成其备份或还原，SIGTERM 用于停止此特定进程，或发送 SIGQUIT 以结束整个备份或恢复会话。

-43244 All onbar processes participating in the backup/restore session are suspended.

The database administrator, computer operator, or storage manager sent SIGSTOP or SIGTSTP, usually a CTRL-Z or CTRL-Y, to all of the processes involved in this backup or restore session. Presumably this action was taken to halt processing temporarily during resolution of a problem.

数据库管理员、计算机操作员或存储管理器将SIGSTOP或SIGTSTP(通常为CTRL-Z或CTRL-Y)发送到此备份或还原会话所涉及的所有进程。据推测，采取这一是为了在解决问题期间暂时停止处理。

Use the ps system command to find a list of all ON-Bar processes. Send SIGCONT to each of them (kill -CONT ) to allow each process to complete its backup or restore, SIGTERM to stop a particular process,or SIGQUIT to one of the processes to end the whole backup or restore session.

使用 ps 系统命令查找所有 ON-Bar 进程的列表。向每个进程发送 SIGCONT(kill -CONT) 以允许每个进程完成其备份或还原，向 SIGTERM 发送停止特定进程的 SIGTERM，或向其中一个进程发送 SIGQUIT 以结束整个备份或恢复会话。

-43245 ON-Bar could not start another child process.

ON-Bar encountered an error starting another process to back up or restore data in parallel. A lack of sufficient memory or the user having too many processes running at the same time usually causes this situation.

ON-Bar 启动另一个进程以并行备份或恢复数据时出错。内存不足或用户同时运行过多进程通常会导致这种情况。

Increase the amount of real memory or swap space, end any unnecessary processes, or reduce BAR_MAX_BACKUP value in your ONCONFIG file.

增加实际内存量或交换空间，结束任何不必要的进程，或减少 ONCONFIG 文件中BAR_MAX_BACKUP 值。

-43246 The ON-Bar process exited with a problem (exit code (0x), signal ).

An ON-Bar child process encountered an error while performing its backup or restore. The child process returned an error (the exit code) to its parent.

If the exit code has the value 141 (0x8d), then the child process exited because it received an operating-system signal, reported by this message.

ON-Bar 子进程在执行其备份或还原时遇到错误。子进程向其父进程返回一个错误(退出代码)。如果退出代码的值为 141(0x8d)，则子进程退出，因为它收到了由此消息报告的操作系统信号。

If the exit code reported in the message is non-zero, then look at the list of ON-Bar exit codes in the documentation or at the ON-Bar activity log to find the cause of the problem. If the signal number is non-zero, look at the documentation for your operating system to see what might have caused this problem.

如果消息中报告的退出代码为非零，则请查看文档中的 ON-Bar 退出代码列表或 ON-Bar活动日志，以找出问题的原因。如果信号为非零，请查看操作系统的文档，以了解可能导致此问题的原因。

-43247 complete, returning (0x).

An ON-Bar process has completed its processing and is exiting.

ON-Bar 进程已完成其处理并正在退出。

If the process returned 0, then no further action is required. If the process returned a nonzero value, then check the activity log for errors and take action appropriate for those errors.

如果进程返回 0，则不需要进一步的操作。如果进程返回一个非零值，则检查活动日志中是否有错误，并对这些错误采取适当的操作。

-43255 Successfully connected to Storage Manager.

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43256 Version of the XBSA shared library is not compatible with version of ON-Bar.

Either the XBSA shared library that the storage manager vendor provided has not been validated by GBase, or an error occurred during the installation of ON-Bar or the storage manager application.

要么是存储管理器供应商提供的 XBSA 共享库未经GBase验证，要么是在安装 ON-Bar 或存储管理器应用程序时发生错误。

Look at the contents of the sm_versions file in $GBS_HOME/etc or %GBS_HOME%\etc. Make sure that the data matches the version of your storage manager and confirm that this version of the storage manager has been certified with this version of ON-Bar. Consult your storage-manager documentation for the correct storage manager version to put into the sm_versions table in the sysutils database.

查看 $GBS_HOME/etc 或 %GBS_HOME%\etc 中 sm_versions 文件的内容。确保数据与存储管理器的版本相匹配，并确认此版本的存储管理器已通过此版本的 ON-Bar 认证。

请参阅存储管理器文档，以获得要放入 sysutils 数据库中 sm_versions 表中的正确存储管理器版本。

-43257 Could not open XBSA library .

The shared library does not exist, it has a bad format, or you do not have permission to read it.

共享库不存在，格式错误，或者您没有读取它的权限。

Make sure that the shared library for the Storage Manager was installed properly and that the ONCONFIG file has the correct value for BAR_BSALIB_PATH.

请确保存储管理器的共享库已正确安装，并且 ONCONFIG 文件的 BAR_BSALIB_PATH 具有正确的值。

-43258 ON-Bar could not get logical log from the Storage Manager.

The backup of this logical log file is missing.

缺少此逻辑日志文件的备份。

Query your storage manager to find out if the backup of this log file exists and if it is restorable.

请查询存储管理器，以确定此日志文件的备份是否存在以及是否可恢复。

-43259 Could not open XBSA library , so trying default path.

The shared library does not exist, it has a bad format, or you do not have permission to read it.

共享库不存在，格式错误，或者您没有读取它的权限。

Make sure that the shared library for the storage manager was installed properly and that the ONCONFIG file has the correct value for BAR_BSALIB_PATH.

确保存储管理器的共享库已正确安装，并且 ONCONFIG 文件的 BAR_BSALIB_PATH 具有正确的值。

-43260 ON-Bar was unable to get backup record of from storage manager.

The storage manager does not have a backup record for the dbspace or blobspace.

存储管理器没有 dbspace 或 blobspace 的备份记录。

For more information, contact the storage manager vendor or GBase Technical Support.

有关更多信息，请与存储管理器供应商或 GBase 技术支持部门联系。

-43261 BAR_BSALIB_PATH is undefined; trying default path.

Either a line in the ONCONFIG file contains BAR_BSALIB_PATH with no value,or a problem occurred reading the ONCONFIG file.

ONCONFIG 文件中的一行包含没有值的 BAR_BSALIB_PATH，或者读取 ONCONFIG 文件时出现问题。

Verify that the format of the ONCONFIG file is correct. Also make sure that either BAR_BSALIB_PATH is assigned a correct value or is not specified in the file at all.

验证 ONCONFIG 文件的格式是否正确。还要确保给 BAR_BSALIB_PATH 分配了一个正确的值，或者根本没有在文件中指定。

-43262 The wrong version of was returned from the Storage Manager.

The storage space or log file returned by the storage manager for restore is not the object requested by ON-Bar.

存储管理器返回的用于恢复的存储空间或日志文件不是 ON-Bar 请求的对象。

Query your storage manager to find out if the correct backup of this storage space or log file exists and if it is restorable.

请查询存储管理器以确定是否存在此存储空间或日志文件的正确备份，以及是否可恢复该存储空间或日志文件。

-43263 XBSA Error: () Active object does not exist.

Attempt to deactivate it failed.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

Refer to the storage manager message log (or equivalent) for more information. If the cause of the error is still unclear, contact your storage manager technical support. If you are using the GBase 8s Storage Manager, contact GBase Technical Support.

有关更多信息，请参考存储管理器消息日志(或等效)。如果错误的原因仍然不清楚，请与您的存储管理器技术支持联系。如果您正在使用 GBase 8s 存储管理器，请与 GBase 技术支持部门联系。

-43264 XBSA Error: () A system error occurred. Aborting XBSA session.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43265 XBSA Error: () Attempt to authorize failed.

Verify that the username is gbasedbt or root or is a member of the bargroup group.

验证用户名是 gbasedbt 或 root，或者是 bargroup 组的成员。

-43266 XBSA Error: () Invalid XBSA function call sequence.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43267 XBSA Error: () Invalid XBSA session handle.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43268 XBSA Error: () XBSA buffer is too small for the object.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43269 XBSA Error: () Description of the object exceeds the maximum allowed value: .

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43270 XBSA Error: () The database server name exceeds maximum allowed size .

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43271 XBSA Error: () The new security token name is invalid.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43272 XBSA Error: () Invalid vote value: Must be BSAVoteCOMMIT or BSAVote_ABORT.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43273 XBSA Error: () Invalid environment keyword.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43274 XBSA Error: () That object already exists.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43275 XBSA Error: () A new security token must be created.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43276 XBSA Error: () Backup object does not exist in Storage Manager.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43277 XBSA Error: () Exceeded available resources.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43278 XBSA Error: () A DataBlock pointer is required.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43279 XBSA Error: () An object name is required.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43280 XBSA Error: () Unable to access NULL pointer.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43281 XBSA Error: () Rule ID is required.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43282 XBSA Error: () The object is not empty.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43283 XBSA Error: () This object has not been backed up.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43284 XBSA Error: () Object information data exceeds maximum allowed size .

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43285 XBSA Error: () Object name exceeds maximum allowed size .

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43286 XBSA Error: () Operation is not authorized for .

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43287 XBSA Error: () A value for the old security token is required.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43288 XBSA Error: () The security token has expired.

Create a new one.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43289 XBSA Error: () The transaction was aborted.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43290 XBSA Error: () A quote is missing from an environment keyword.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43291 XBSA Error: () A username cannot be deleted while it owns objects.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43292 XBSA Error (): An unspecified XBSA error has occurred: .

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43293 XBSA Error: () A query or object retrieval tried to get more data than exists.

An error occurred in the storage manager application.

存储管理器应用程序中发生错误。

-43294 ON-Bar was unable to get the backup record of logical log from the storage manager.

The storage manager issued an error when finding a backup record for the logical log.

当找到逻辑日志的备份记录时，存储管理器发出一个错误。

For further information, contact the storage manager vendor or GBase Technical Support.

有关更多信息，请与存储管理器供应商或 GBase 技术支持部门联系。

-43295 WARNING: BAR_TIMEOUT unable to initialize connection to Storage Manager.

The storage manager may not be running or there may be storage manager configuration problems.

存储管理器可能没有运行，或者可能存在存储管理器配置问题。

Refer to the storage manager message log (or equivalent) for more information.

If the cause of the error is still unclear, contact your storage manager Technical Support. If you are using the GBase 8s Storage Manager, contact GBase Technical Support.

-43296 WARNING: BAR_TIMEOUT Storage Manager Progress may be stalled.

The current command has exceeded the BAR_TIMEOUT value. This may indicate a normal transfer of a large data set or it may mean the storage manager needs attention.

当前命令已超过 BAR_TIMEOUT 值。这可能表示大数据集的正常传输，也可能意味着存储管理器需要注意。

Check to make sure the storage manager is still running and that data is still being transfered to/from the storage manager.

Refer to the storage manager message log (or equivalent) for more information.

If the cause of the error is still unclear, contact your storage manager Technical Support. If you are using the GBase 8s Storage Manager, contact GBase Technical Support.

检查以确保存储管理器仍在运行，并且数据仍传输到或从存储管理器中传输。有关更多信息，请参考存储管理器消息日志(或等效)。如果错误的原因仍然不清楚，请与您的存储经理技术支持联系。如果您正在使用 GBase 8s 存储管理器，请与 GBase 技术支持部门联系。

-43297 BAR_BSALIB_PATH in ONCONFIG is not an absolute pathname.

The absolute path of the XBSA library was not specified for the BAR_BSALIB_PATH parameter in the ONCONFIG file.

未为 ONCONFIG 文件中的 BAR_BSALIB_PATH 参数指定 XBSA 库的绝对路径。

Modify the BAR_BSALIB_PATH parameter in the ONCONFIG file by specifying the absolute path of the XBSA library.

请通过指定 XBSA 库的绝对路径来修改 ONCONFIG 文件中的 BAR_BSALIB_PATH 参数。

-43300 WARNING: BAR_TIMEOUT: The backup and restore filter program progress might be stalled.

The current command has exceeded the amount of time specificed by the BAR_TIMEOUT configuration parameter. This can indicate a slow filter program, the transfer of a large data set, or it can mean that the storage manager needs attention.

当前命令已超过 BAR_TIMEOUT 配置参数指定的时间量。这可以表示一个缓慢的过滤程序，一个大数据集的传输，或者它可能意味着存储管理器需要注意。

ACTION操作Make sure the storage manager is still running and that data is still being transfered to or from the storage manager.

Review the storage manager message log or the log file for the filter.

If the cause of the error is still unclear, contact your storage manager or Technical Support for your filter. If you are using the GBase 8s Storage Manager, contact GBase Support.

确保存储管理器仍在运行，并且数据仍传输到或从存储管理器中传输。请检查存储管理器消息日志或过滤器的日志文件。如果错误的原因仍然不清楚，请与您的存储管理器或技术支持部门联系。如果您正在使用 GBase 8s 存储管理器，请与 GBase 技术支持部门联系。

-43303 Creating the backup and restore filter process failed with error code .

ON-Bar attempted to create a filter process for running the configured filter program. The process creation for execution of the filter program failed with the given error code.

ON-Bar 试图创建用于运行配置的过滤程序的过滤进程。使用给定的错误代码，执行过滤程序的进程创建失败。

ACTION操作Check that the BACKUP_FILTER and RESTORE_FILTER configuration parameters are configured correctly in the onconfig file. If the cause of the error is still unclear, contact Technical Support for your filter.

检查是否在 onconfig 文件中正确配置了 BACKUP_FILTER 和 RESTORE_FILTER 配置参数。如果错误的原因仍然不清楚，请为您的过滤器联系技术支持。

-43305 (copy ID ) not expired even though it matches the expiration policy.

The named object matches the expiration policy named on the command line with the -g, -i, or -t option. The object cannot be deleted, however, because it is needed to allow the restore of another object that does not match the expiration policy.

命名对象将命令行上命名的过期策略与 -g、-i 或 -t 选项匹配。但是，无法删除该对象，因为需要该对象才能恢复与过期策略不匹配的另一个对象。

This message is informational.

此消息是信息性的。

-43306 Whole system backup from not expired even though it matches the expiration policy.

The whole-system backup started at the described time matches the expiration policy named on the command line. The backup cannot be deleted, however,because it is needed to allow the restore of another whole-system backup that does not match the expiration policy.

在所述时间开始的整个系统备份与命令行上指定的过期策略匹配。但是，备份不能删除，因为需要备份才能恢复另一个与过期策略不匹配的整个系统备份。

This message is informational.

此消息是信息性的。

-43307 Expired (copy ID ), backed up.

The named object has been expired as requested.

命名对象已按请求过期。

-43308 Expired (copy ID ), backed up; restore may not be possible.

The named object has been expired as requested. Normally onsmsync would not have removed it, but the -O option was passed on the command line. If the object is a storage space, ON-Bar cannot determine if it can restore that space from remaining data in the sysutils database. If the object is a logical log, ON-Bar cannot determine if any subsequent restore attempts will fail.

命名对象已按请求过期。通常 onsmsync 不会删除它，但是 -O 选项是在命令行上传递的。如果对象是存储空间，ON-Bar 无法确定它是否可以从 sysutils 数据库中的剩余数据中恢复该空间。如果对象是逻辑日志，ON-Bar 无法确定后续的还原尝试是否会失败。

If the object can be re-created in the storage manager and you think you may need to restore this object with ON-Bar, then follow the procedures for re-creating the object in the storage manager. Then contact GBase Technical Support for assistance.

如果可以在存储管理器中重新创建对象，并且您认为可能需要使用 ON-Bar 恢复该对象，那么请遵循在存储管理器中重新创建对象的过程。然后，请与 GBase 技术支持部门联系以获得帮助。

-43309 Expired whole system backup from ; restore may not be possible.

The whole-system backup started at the described time has been expired as requested. Normally onsmsync would not have removed it, but the -O option was passed on the command line. ON-Bar cannot determine if it can restore from the remaining data in the sysutils database.

在所述时间启动的整个系统备份已按要求过期。通常 onsmsync 不会删除它，但是 -O 选项是在命令行上传递的。ON-Bar 无法确定它是否可以从 sysutils 数据库中的其余数据恢复。

If the objects in this whole-system backup can be re-created in the storage manager and you think you may need them to restore with ON-Bar, then follow the procedures for re-creating them in the storage manager. Then contact GBase Technical Support for assistance.

如果整个系统备份中的对象可以在存储管理器中重新创建，并且您认为可能需要使用ON-Bar 进行恢复，那么请遵循在存储管理器中重新创建对象的过程。然后，请与 GBase技术支持部门联系以获得帮助。

-43310 Could not update the sysutils database - run onsmsync -b when the database server is quiescent or online.

Either a log salvage was run as a distinct step (onbar -b -l -s), ON-Bar encountered an error cataloging an action but successfully updated the emergency boot file, or onsmsync was run when the database server was off-line or otherwise unavailable. Therefore the sysutils database is inconsistent with the storage manager and emergency boot file.

无论是作为一个单独的步骤运行日志救助 (onbar -b -l -s)，ON-Bar 在记录操作时遇到错误，但成功地更新了紧急引导文件，或者在数据库服务器 off-line 或其他不可用时运行 onsmsync。因此，sysutils 数据库与存储管理器和紧急引导文件不一致。

Bring the database server online (possibly including a physical and logical restore) and run onsmsync -b.

请将数据库服务器联机(可能包括物理和逻辑恢复)并运行 onsmsync -b。

-43319 Exiting without expiring any backup object. All the storage spaces met the expiration policy or storage spaces were not backed-up using ON-Bar.

After applying the expiration policies specified by the -g option, the onsmsync list of objects contains only logical logs. The list does not contain space backups.

应用 -g 选项指定的过期策略后，对象的 onsmsync 列表仅包含逻辑日志。列表不包含空间备份。

Use the -t or -i option to expire logical log backups.

使用 -t 或 -i 选项可以使逻辑日志备份过期。

-43320 Begin backup verification of level for (Storage Manager copy ID: ).

This message is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43321 percent of has been verified.

This message provides progress feedback for the backup verification as a percentage of dbspace size.

此消息为备份验证提供进度反馈，作为 dbspace 大小的百分比。

-43322 Completed level backup verification successfully.

This message is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43323 ERROR: Unable to create the physical check session:.

This error occurs during backup verification.

此错误发生在备份验证过程中。

Before you call Technical Support, examine the message log files for the database server, ON-Bar, and archecker.

在致电技术支持之前，请检查数据库服务器、ON-Bar 和 archecker 的消息日志文件。

-43324 ERROR: Unable to open the physical check errtxt: .

This error occurs during backup verification. It indicates a problem running the archecker process.

此错误发生在备份验证过程中。它表示运行 archecker 进程时出现问题。

Check permissions and disk space for the archecker temporary files. For these file locations, see $GBS_HOME/etc/ac_config.std or%GBS_HOME%\etc\ac_config.std. Before you call Technical Support, examine the message log files for the database server,ON-Bar, and archecker.

检查临时文件的权限和磁盘空间。有关这些文件位置，请参见$GBS_HOME/etc/ac_config.std 或 %GBS_HOME%\etc\ac_config.std。在致电技术支持之前，请检查数据库服务器、ON-Bar 和 archecker 的消息日志文件。

-43325 ERROR: Unable to write the physical check errtxt: .

This error occurs during backup verification. It indicates a problem running the archecker process.

此错误发生在备份验证过程中。它表示运行 archecker 进程时出现问题。

-43326 ERROR: Unable to close the physical check errtxt: .

This error occurs during backup verification. It indicates either a problem running the archecker process or a corrupt backup.

此错误发生在备份验证过程中。它表示运行 archecker 进程或损坏备份的问题。

-43328 Failure in archecker process execution status.

An error occurred during Level backup verification.

在级别备份验证期间发生错误。

Check permissions and disk space for the archecker temporary files. For these file locations, see $GBS_HOME/etc/ac_config.std or%GBS_HOME%\etc\ac_config.std. Before you call Technical Support,examine the message log files for the database server, ON-Bar, and archecker.

If the AC_CONFIG environment variable is not set and there is no ac_config.std file in $GBS_HOME/etc or %GBS_HOME%\etc, then look at the msg.log file generated by archecker in the directory where ON-Bar is executed.

检查临时文件的权限和磁盘空间。有关这些文件位置，请参见 $GBS_HOME/etc/ac_config.std 或 %GBS_HOME%\etc\ac_config.std。如果AC_CONFIG 环境变量未设置，并且$ GBS_HOME/etc 或 %GBS_HOME%\etc 中没有ac_config.std 文件，则查看执行 ON-Bar 目录中的 archecker 生成的 msg.log 文件。

-43362 Begin displaying logical log . (Storage Manager copy ID: ).

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43363 Completed displaying logical log .

This is an ON-Bar progress message.

这是一个 ON-Bar 进度信息。

-43364 No logical logs to display.

You are trying to display one or more logical logs but none of those you specified have been archived using ON-Bar or the emergency boot file might be corrupted.

您正在尝试显示一个或多个逻辑日志，但您指定的日志中没有一个已使用 ON-Bar 存档，或者紧急引导文件可能已损坏。

Make sure that the emergency boot file has the log backup information.

请确保紧急引导文件具有日志备份信息。

-43365 Unable to display logical log : .

There could be a problem in constructing a block of log records which shall be displayed using the callback function. The logical log file you are displaying may be corrupted.

在构造日志记录块时可能会出现问题，应该使用回调函数来显示这些记录。正在显示的逻辑日志文件可能已损坏。

-43373 Sysutils database will be updated when server exits fast recovery.

ON-Bar tries to update the sysutils database while the database server is in fast recovery. When the database server exits fast recovery, the sysutils database is updated.

在数据库服务器处于快速恢复状态时，ON-Bar 尝试更新 sysutils 数据库。当数据库服务器退出快速恢复时，sysutils 数据库将被更新。

Place the database server in quiescent or online mode, then run the onsmsync -b command. This command generates the emergency boot file.

将数据库服务器置于静止或在线模式下，然后运行 onsmsync -b 命令。此命令生成紧急引导文件。

-43376 Unable to convert datetime to string: .

The date string could not be interpreted because the format used did not match the format expected by ON-Bar.

无法解释日期字符串，因为所使用的格式与 ON-Bar 预期的格式不匹配。

Check for the values of environment variables related to internationalization or localization (such as CLIENT_LOCALE and GL_DATETIME). If the environment is set for localization, then make sure the date specified matches the local format for dates. If no appropriate environment variables are set, then make sure the date was specified in the standard SQL date format.

检查与国际化或本地化相关的环境变量的值(如 CLIENT_LOCALE 和 GL_DATETIME)。如果环境设置为本地化，则确保指定的日期与本地日期格式匹配。如果没有设置适当的环境变量，则确保日期是以标准 SQL Date 格式指定的。

-43380 Deadlock detected. Wait a few seconds for the lock to clear and try again.

Two processes attempted to lock the same sysutils database table or row at the same time resulting in a deadlock.

两个进程试图同时锁定相同的 sysutils 数据库表或行，导致死锁。

Wait a few seconds for the other process to complete and release the lock and try again.

等待其他进程完成并释放锁，然后再试一次。

-43381 The logical logs are full. ON-Bar might encounter errors writing to the sysutils database.

The logical logs were filled while ON-Bar was running. ON-Bar performs database transactions when it writes a record of what it has done to the ON-Bar catalogs in the sysutils database. Therefore, the work performed by the current ON-Bar process is not recorded in the sysutils database. However, it is recorded in the emergency boot file.

逻辑日志是在 ON-Bar 运行时填写的.在将对 sysutils 数据库中的 ON-Bar 目录所做操作的记录写入时，ON-Bar 执行数据库事务。因此，在 sysutils 数据库中没有记录当前条上进程所执行的工作。但是，它被记录在紧急引导文件中。

If by the end of the backup or restore, the object still was not cataloged,use onsmsync to update the data.

如果到备份或还原结束时，对象仍未编目，则使用 onsmsync 更新数据。

-43385 Restoring even though it is online.

ON-Bar by default does not restore spaces if they are online.

To get this message, the -O option must have been used on the onbar command line to override internal checks.

缺省情况下，如果空间处于 online 状态，则 ON-Bar不进行还原。要获得此消息，必须在 onbar 命令行上使用 -O 选项来覆盖内部检查。

No action is necessary. ON-Bar will restore the space.

没有必要采取。点对点将恢复空间。

-43388 The maximum allowed number of storage spaces per ON-Bar command has been exceeded.

There is a limit to how many storage spaces ON-Bar may process in a whole system backup or restore. This number varies from platform to platform.

Non-whole system backup or restore does not have such a limit.

在一个完整的系统备份或还原中，ON-Bar 的存储空间可以处理多少，这是有限制的。这个数字因平台而异。非完整系统备份或还原没有此限制。

If possible, retry the backup or restore without the whole system option.

If a whole system restore is required, consider reducing the number of storage spaces in your installation.

如果可能，请在没有整个系统选项的情况下重试备份或还原。如果需要整个系统还原，请考虑减少安装中的存储空间数量。

-43389 does not have a level backup.

A level backup will be performed by default.

An incremental backup requires that a backup of the previous level exists.

For example, there must be at least one level 0 backup of the object before a level 1 backup of it may be performed. Both a level 0 and a level 1 backup must exist before a level 2 backup may be performed.

增量备份要求存在上一级的备份。例如，在执行对象的 1 级备份之前，必须至少有一个0 级备份。在执行 2 级备份之前，必须同时存在 0 级和 1 级备份。

-43391 Skipped backup/restore of space .

The specified storage space was a temporary space, the space was online,or it is the root dbspace and the database server is in Fast Recovery mode and does not need a restore.

指定的存储空间是临时空间，空间是 online 的，或者是 root dbspace，数据库服务器处于快速恢复模式，不需要恢复。

No corrective action is necessary.

不需要采取纠正措施。

-43392 One or more BLOBspaces are down. Log backup has been aborted.

A BLOBspace is down. Backing up or salvaging the logical logs would make it impossible to restore this BLOB in the future.

一个 BLOBspace 关闭了。备份或挽救逻辑日志将使将来无法恢复这个 BLOB。

Bring all BLOBspaces online and retry the logical log backup or salvage.

将所有 BLOBspaces online 并重新尝试逻辑日志备份或救助。

-43393 Storage space is down and cannot be backed up.

Only storage spaces that are online can be backed up.

只能备份 online 存储空间。

Bring the storage space online and attempt the backup again.

请将存储空间 online 并再次尝试备份。

-43394 Storage space is not down so it will not be restored.

Only storage spaces that are off-line need to be restored. This storage space will not be restored, but restore of any other storage spaces will be attempted.

只需要恢复 off-line 的存储空间。将不会还原此存储空间，但将尝试还原任何其他存储空间。

-43395 A log backup is already running. Can't start another.

This occurs when several onbar processes try to back up the logical logs at the same time. One of the causes might be that the program defined by the ALARMPROGRAM parameter in your ONCONFIG file calls onbar to do log backups and is executed by the database server while another onbar process is also trying to perform a log backup. Another possible cause is that multiple onbar command-line calls were made to perform restores, and they are interfering with each other.

当多个 onbar 进程试图同时备份逻辑日志时，就会发生这种情况。原因之一可能是ONCONFIG 文件中由 ALARMPROGRAM 参数定义的程序调用 onbar 进行日志备份，并由数据库服务器执行，而另一个 onbar 进程也试图执行日志备份。另一个可能的原因是进行了多个 onbar 命令行调用来执行还原，并且它们相互干扰。

No action is required. The first log backup that is started will back up all of the used log files.

不需要采取任何。启动的第一个日志备份将备份所有使用的日志文件。

-43399 ERROR: No response was received from the database server.

Aborting ON-Bar.

There was no response from the database server. The database server may not be running properly and may have a problem.

数据库服务器没有响应。数据库服务器可能运行不正常，可能有问题。

Determine what is wrong with the database server, repair it, and retry the backup or restore.

确定数据库服务器的问题所在，修复它，然后重试备份或还原。

-43400 ondblog usage.

ondblog [-f ] []new mode:新模式：buf - Change database to buffered mode.

unbuf - Change database to unbuffered mode.

nolog - Change database to no logging. (not in AD/XP)ansi - Change database to be ANSI-compliant cancel - Cancel logging request.

-f File containing list of databases for logging change.

-f 包含用于记录更改的数据库列表的文件。

List of databases for logging change.

记录更改的数据库列表。

This message displays after an incorrect entry of the ondblog command.

此消息在 ondblog 命令输入错误后显示。

Revise the command and try again.

请修改该命令，然后重试。

-43402 ERROR: Invalid serial number. Consult your installation manual.

The serial number for ondblog is invalid.

ondblog 的序列号无效。

Ask your System Administrator to re-install ondblog.

请系统管理员重新安装 ondblog。

-43421 Logging mode is not available in this edition of the database server.

The named logging mode is available in some but not all versions of GBase 8s database servers.

命名日志模式在某些版本的 GBase 8s 数据库服务器中是可用的，但不是所有版本。

Find an appropriate logging mode that is available. Check the release notes or your Administrators Guide for supported logging modes.

找到可用的适当日志记录模式。请查看发版说明或管理员指南，了解支持的日志记录模式。

For GBase 8s Extended Parallel Server or GBase 8s Dynamic Server with Advanced Decision Support and Extended Parallel options, if you are trying to turn off logging for a database, try to convert all the tables in that database to one of the nonlogged table types.

对于具有高级决策支持和扩展并行选项的 GBase 8s Extended Parally Server 或 GBase 8s Dynamic Server，如果您试图关闭数据库的日志记录，请尝试将该数据库中的所有表转换为未记录的表类型之一。

-46007 Cannot perform Java-to-SQL type mapping for type ().

This error can occur if you use the SQL data type, such as FLOAT, in the EXTERNAL NAME clause of the CREATE FUNCTION statement.

如果在 CREATE FUNCTION 语句的 EXTERNAL NAME 子句中使用 SQL 数据类型(例如FLOAT)，则可能会发生此错误。

Use the Java data type, not the SQL data type, in the EXTERNAL NAME clause.

在 EXTERNAL NAME 子句中使用 Java 数据类型，而不是 SQL 数据类型。

-46103 Error loading Java UDR class (). Verify the three part name (<dbname.username.jarid>) of the installed jar with the jar file name is in your JAR_TEMP_PATH or /tmp directory.

A possible cause of this error is using "thisjar" instead of using the jar ID in the deploy.txt file.

造成此错误的一个可能原因是使用“thisjar”，而不是在 deploy.txt 文件中使用 jar ID。

-47086 Cannot specify current as default value with non-datetime column type.

You cannot assign a default value consisting of the current time from the system clock when the column data type is not DATETIME. Modify the column data type to DATETIME (if permitted), or specify a different default value for the column.

如果列数据类型不是 DATETIME，则不能从系统时钟分配由当前时间组成的缺省值。将列数据类型修改为 DATETIME (如果允许的话)，或为该列指定不同的缺省值。

-47087 Cannot specify null default value when column doesn't accept nulls.

Select a different (nonnull) default value for the column, or modify the column to accept null values.

为该列选择不同（非空）默认值，或修改该列以接受空值。

-47088 Cannot specify server or site as a default value with this column type.

You cannot specify a default value that consists of the current database server name or current site name for a column that is not a CHAR, NCHAR, VARCHAR, or NVARCHAR data type. Change the column data type (if permitted), or specify a different default value.

不能为非 CHAR、NCHAR、VARCHAR 或 NVARCHAR 数据类型的列指定由当前数据库服务器名称或当前站点名称组成的缺省值。更改列数据类型（如果允许的话），或指定不同的缺省值。

-47089 Cannot specify server or site as a default value with this column length.

For specifying a default value that consists of the current database server name or current site name for a CHAR, NCHAR, VARCHAR, or NVARCHAR column,the minimum column length must be 18. Increase the column length, or specify a different default value.

若要为 CHAR、NCHAR、VARCHAR 或 NVARCHAR 列指定由当前数据库服务器名称或当前站点名称组成的缺省值，则最小列长度必须为 18。增加列长度，或指定不同的缺省值。

-47090 Cannot specify today as a default value with this column type.

You cannot specify a default value that consists of the current system date for a column when the column data type is not DATE. Change the column data type (if permitted), or specify a different default value.

当列数据类型不是 DATE 时，不能指定由列的当前系统日期组成的缺省值。更改列数据类型（如果允许的话），或指定不同的缺省值。

-47091 Cannot specify user as a default value with this column type.

You cannot specify a default value that consists of the login name of the current user for a column that is not a CHAR, NCHAR, VARCHAR, or NVARCHAR data type. Change the column data type (if permitted), or specify a different default value.

不能为非 CHAR、NCHAR、VARCHAR 或 NVARCHAR 数据类型的列指定由当前用户的登录名组成的缺省值。更改列数据类型（如果允许的话），或指定不同的缺省值。

-47092 Cannot specify user as a default value with this column length.

In order to specify a default value that consists of the login name of the current user for a CHAR, NCHAR, VARCHAR, or NVARCHAR column, the minimum column length must be 8. Increase the column length, or specify a different default value.

为了指定由 CHAR、NCHAR、VARCHAR 或 NVARCHAR 列的当前用户的登录名组成的缺省值，最小列长度必须为 8 。增加列长度，或指定不同的缺省值。

-47093 Cannot create unique or primary key constraint with column type of BYTE or TEXT.

In order to create a primary or unique constraint on the column, change the column data type from TEXT or BYTE, if permitted.

为了在列上创建主约束或唯一约束，如果允许，请将列数据类型从 TEXT 或 BYTE 更改。

-47095 Column not found in referenced table.

You cannot create a foreign-key constraint on a column that does not exist in the referenced table. Specify a different referencing or referenced column for the constraint.

不能在引用表中不存在的列上创建外键约束。为约束指定不同的引用或引用列。

-47098 Number of columns in composite list exceeds maximum.

You cannot include more than 16 column names in a single primary or unique constraint on GBase 8s Dynamic Server, GBase 8s Universal Server, or GBase 8s OnLine Dynamic Server, or 8 column names in one primary or unique constraint on GBase 8s SE. Reduce the number of columns that are specified in the constraint definition.

在 GBase 8s Dynamic Server、GBase 8s Universal Server 或 GBase 8s Online Dynamic Server 上的单个主约束或唯一约束中，不能包含超过 16 个列名，也不能在GBase 8s SE 上的一个主约束或唯一约束中包含8个列名。减少约束定义中指定的列数。

-47099 You cannot modify an existing constraint.

You cannot use the ALTER TABLE menu options to modify an existing constraint. An asterisk preceding the name identifies existing constraints.

不能使用 ALTER TABLE 菜单选项修改现有约束。名称前面的星号标识现有约束。

-47100 Column not in this table.

You cannot create a constraint on a column that does not exist in the table.

不能在表中不存在的列上创建约束。

-47101 To drop an existing constraint, the current field must be constraint name.

The cursor is in the wrong field on the screen. Move the cursor to highlight an entry in the Constraint Name field to drop all columns that are associated with a primary key, check, or unique constraint.

Highlight the Constraint field to drop all columns that are associated with a foreign-key constraint.

光标在屏幕上的错误字段中。移动光标以突出显示约束名称字段中的条目，以删除与主键、CHECK 或唯一约束关联的所有列。突出显示约束字段以删除与外键约束关联的所有列。

-47102 You have exceeded the temporary buffer size.

The buffer in the SQL editor, which holds the check-constraint value and the literal default-constraint value, is full. If you are modifying the check constraint, a different editor might have a larger buffer.

SQL 编辑器中的缓冲区（包含检查约束值和文字默认约束值）已满。如果要修改 CHECK约束，则不同的编辑器可能具有更大的缓冲区。

-47104 The fill factor percentage must be a positive integer not exceeding 100.

You tried to specify a fill factor percentage that is a negative number or is greater than 100 percent. Specify a different percentage, or press RETURN to accept the default value of 90 percent.

您尝试指定一个填充因子百分比，该百分比为负数或大于100%。指定不同的百分比，或按“返回”以接受 90% 的默认值。

-47105 Dbspace has already been selected as part of the strategy.

You cannot use the same dbspace more than once in a fragmentation strategy. The dbspace you selected is already part of the strategy.

Select another dbspace from the current list.

在分片策略中，不能多次使用同一个 dbspace。您选择的 dbspace 已经是策略的一部分。从当前列表中选择另一个 dbspace。

-47106 Table has already been selected as part of the attaching strategy.

A table can be attached to a fragmentation strategy only once. The table that you selected is already part of the fragmentation strategy.

Select another table from the current list.

表只能附加到分片策略一次。您选择的表已经是分片策略的一部分。从当前列表中选择另一个表。

-47107 An Alter Table option has already been altered.

You can execute only one menu option in an ALTER FRAGMENT menu session,and it cannot be applied to the current strategy more than once. For example, you can add only one dbspace to a round-robin strategy, and you cannot delete a dbspace during the same ALTER TABLE session.

您只能在 ALTER FRAGMENT 菜单会话中执行一个菜单选项，并且它不能应用于当前策略不止一次。例如，只能向循环策略添加一个 dbspace，并且不能在同一个 ALTER TABLE 会话期间删除 dbspace。

-47108 Dbspace is not part of the current strategy.

You have specified a dbspace that is not part of the current fragmentation strategy. Select a dbspace from the list of available dbspaces that is displayed on the screen.

您已经指定了不属于当前分片策略的 dbspace。从屏幕上显示的可用 dbspace列表中选择 dbspace。

-47109 A Dbspace is required if a position is defined.

You have specified a dbspace as part of your attaching table strategy.

This action indicates that you wish to position the attaching table before or after a dbspace that is part of the fragmentation strategy being attached to. You must define a before or after position.

您已经指定了一个 dbspace 作为附加表策略的一部分。此操作表示希望在附加到的分片策略的一部分 dbspace 之前或之后放置附加表。必须定义“前”或“后”位置。

-47111 ALTER currently not supported for this strategy.

The fragmentation strategy you have chosen does not currently support ALTER FRAGMENT operations.

您所选择的分片策略目前不支持 ALTER FRAGMENT 操作。

If that fragmentation strategy is a design requirement of your application,consider creating a new table that uses the strategy, and then loading existing data into the new table whose fragmentation strategy matches your requirements.

如果该分片策略是应用程序的设计要求，请考虑创建一个使用该策略的新表，然后将现有数据加载到新表中，该表的分片策略与您的需求相匹配。

-47112 Must choose a fragmentation key.

You have not chosen a fragmentation key for the current fragmentation strategy.

您还没有为当前的分片策略选择分片键。

You must mark one of the table columns as selected, from the Fragment-key menu of the dbaccess utility.

必须从 dbaccess 实用程序的分片键菜单中将其中一个表列标记为选定的列。

-47113 Must write an interval value expression.

You have not written an interval value expression for the fragmentation strategy. Interval fragmentation requires that you choose an interval value appropriate for the fragmentation key.

您尚未为分片策略编写间隔值表达式。区间分片要求您选择适合于分片键的间隔值。

For example, with a fragment key of type DATE, valid interval values are:例如，对于类型为 DATE 的分片键，有效的间隔值是：INTERVAL(YYYY-MM) YEAR TO MONTH INTERVAL(MM) MONTH TO MONTH INTERVAL(YYYY) YEAR TO YEAR INTERVAL(DD) DAY TO DAY Where:YYYY = years MM = months DD = days For fragment keys of INTEGER, and other numeric types, the interval value must be a constant expression that evaluates to the same type as the fragment key.

对于 INTEGER 的分片键和其他数字类型，区间值必须是与分片键相同类型的常量表达式。

For example, with a fragment key of INTEGER TYPE, some valid interval values are:例如，对于 INTEGER TYPE 的分片键，一些有效的间隔值是：1337 0.1337E4-47114 Must specify at least one partition.

You must have at least one partition for data storage using the selected fragmentation strategy.

使用所选的分片策略存储数据必须至少有一个分区。

Within a given dbspace, each partition name that you declare must be unique among the names of partitions of the same table or index.

在给定的 dbspace 中，您声明的每个分区名称在同一表或索引的分区名称之间必须是唯一的。

-47115 Missing name from a partition.

You have omitted the name of one of the partitions in the fragmentation strategy.

您忽略了分片策略中的一个分区的名称。

Within a given dbspace, each partition name that you declare must be unique among the names of partitions of the same table or index.

在给定的 dbspace 中，您声明的每个分区名称在同一表或索引的分区名称之间必须是唯一的。

-47116 Missing expression from a partition.

You have omitted the partition expression from one of the partitions in the fragmentation strategy.

您已经忽略了分片策略中的一个分区中的分区表达式。

For Interval fragmentation, valid partition expressions are of the form:1. 对于区间分片，有效的分区表达式的形式如下：a. VALUES < {transition}The transition value, depends on the interval value, and the data type of the fragment key.

转换值取决于区间值和分片键的数据类型。

For example, with fragment key of DATE type, and an interval value of INTERVAL(1-3) YEAR TO MONTH, some valid partition expressions are:例如，使用 DATE 类型的分片键和 INTERVAL(1-3) YEAR TO MONTH 的间隔值，一些有效的分区表达式是：VALUES < DATETIME(1980-02-13) YEAR TO DAY VALUES < DATETIME(1986-11-01) YEAR TO DAY b. VALUES IS NULL This form is used to specify the NULL partition. You can only have one NULL partition in a fragmentation strategy.

此表单用于指定空分区。在分片策略中只能有一个空分区。

For List fragmentation, valid partition expressions are of the form:3. 对于列表分片，有效的分区表达式的形式如下：a. VALUES ({constant, ...})The constant value must be valid for the data type of the fragment key.

常量值必须对分片键的数据类型有效。

For example, with a fragment key of CHAR(20) type, some valid partition expressions are:例如，使用 Char(20) 类型的分片键，一些有效的分区表达式是：VALUES ("FL", "CA", "NY", "NJ")VALUES ("OH", "MD", "MI")VALUES (NULL)b. REMAINDER This form is used to specify the REMAINDER partition. There can only be one REMAINDER partition, and it must be the last partition in the partition list.

此表单用于指定 REMAINDER 分区。只能有一个 REMAINDER 分区，它必须是分区列表中的最后一个分区。

-47117 Missing dbspace name from a partition.

You have omitted the dbspace name from one of the partitions in the fragmentation strategy.

您忽略了分片策略中的一个分区中的 dbspace 名称。

-55900 Missing option list.

You specified a processor command-line option of -cc, -l, or -r and terminated the option incorrectly. For information on how command-line graphics terminate these options, see "Command-Line Conventions" on page 6 of the Introduction or online help.

您指定了处理器命令行选项 -cc、-l 或 -r，并错误地终止了该选项。有关命令行图形如何终止这些选项的信息，请参阅导言第 6 页中的“命令行约定”或联机帮助。

-55901 Unrecognized sub-option (option_name).

Text (option_name) following a colon (:) was not a valid suboption. For information on which suboptions are valid with the option, see the online help.

冒号(：)后面的文本(option_name)不是有效的子选项。有关该选项中哪些子选项有效的信息，请参阅联机帮助。

-55902 Incompatible file extension (file_extension) in option list.

For ESQL/C: You specified a processor command-line option of -cc -l,or -r and terminated the option with an incorrect file extension. For information on how command-line graphics terminate these options, see the GBase 8s ESQL/C Programmer's Supplement for Microsoft Windows Environments or online help.

对于 ESQL/C：您指定了处理器命令行选项 -cc -l 或 -r，并以不正确的文件扩展名终止了该选项。有关命令行图形如何终止这些选项的信息，请参阅 GBase 8s ESQL/C程序员对 Microsoft Windows 环境的补充说明或联机帮助。

For ESQL/COBOL: You specified a processor command-line option of -cb,-l, or -r and terminated the option with an incorrect file extension.

For information on how command-line graphics terminate these options,see the GBase 8s ESQL/COBOL Programmer's Supplement for Microsoft Windows Environments or online help.

对于 ESQL/COBOL：您指定了处理器命令行选项 -cb、-l 或 -r，并以不正确的文件扩展名终止了该选项。有关命令行图形如何终止这些选项的信息，请参阅 GBase 8s ESQL/C程序员对 Microsoft Windows 环境的补充说明或联机帮助。

-55903 Processor type option conflict.

You specified more than one CPU-type command-line option (for example,-cpu:i386 and -pm) that identifies the CPU type. Enter the esql command again without the conflicting options.

您指定了多个用于标识 CPU-类型的命令行选项(例如 -cpu:i386 和 -pm)。再次输入esql 命令，不要使用相互冲突的选项。

-55904 Error in spawned program.

For ESQL/C: The esql command processor created a program (compiler,linker, or resource compiler) that returned an error and caused esql to terminate. Check the generated output to determine the error, resolve the error, and run the esql command processor again.

对于 ESQL/C：esql 命令处理器创建了一个返回错误并导致 esql 终止的程序(编译器、链接器或资源编译器)。检查生成的输出以确定错误，解决错误，并再次运行 esql 命令处理器。

For ESQL/COBOL: The esqlcobo command processor created a program(compiler, linker, or resource compiler) that returned an error and caused esqlcobo to terminate. Check the generated output to determine the error, resolve the error, and run the esqlcobo command processor again.

对于 ESQL/COBOL：esqlcobo 命令处理器创建了一个返回错误并导致 esqlcobo 终止的程序(编译器、链接器或资源编译器)。检查生成的输出以确定错误，解决错误，并再次运行esqlcobo 命令处理器。

-55905 Illegal character in filename, `file_name'.

The file file_name contains one or more invalid characters.

文件 file_name 包含一个或多个无效字符。

-55906 Run-time option conflict.

For ESQL/C: You specified more than one runtime option (for example,-runtime:libc and -rt:d). Enter the esql command again without the conflicting options.

对于 ESQL/C：您指定了多个运行时选项(例如，-runtime:libc 和 -rt:d)。再次输入esql 命令，不要使用冲突的选项。

For ESQL/COBOL: You specified more than one runtime option (for example, -runtime:mfrts32 and -rt:s). Enter the esqlcobo command again without the conflicting options.

对于 ESQL/COBOL：您指定了多个运行时选项(例如， -runtime:mfrts32 和 -rt:s)。再次输入 esqlcobo 命令，不要使用相互冲突的选项。

-55907 Subsystem option conflict.

For ESQL/C: You specified more than one subsystem option (for example,-ss:c and -S:w). Enter the esql command again without the conflicting options.

对于 ESQL/C：您指定了多个子系统选项(例如 -ss:c 和 -S:w)。再次输入 esql 命令，不要使用冲突的选项。

For ESQL/COBOL: You specified more than one subsystem option (for example, -ss:c and -Sw). Enter the esqlcobo command again without the conflicting options.

对于 ESQL/COBOL：您指定了多个子系统选项(例如 -ss:c 和 -Sw)。再次输入 esqlcobo命令，不要使用相互冲突的选项。

-55909 I/O error in file (file_name).

An I/O error occurred in the file file_name. Probably no space is available. Increase available space and enter the command again.

文件 file_name 中发生 I/O 错误。可能没有空间了。增加可用空间并再次输入命令。

-55910 Option (option_name) is no longer supported.

For ESQL/C: This release does not support the specified command-line option. For valid options, check the GBase 8s ESQL/C Programmer's Supplement for Microsoft Windows Environments.

对于 ESQL/C：此版本不支持指定的命令行选项。要获得有效的选项，请查看 GBase 8s ESQL/C Programmer's Supplement for Microsoft Windows Environments。

For ESQL/COBOL: This release does not support the specified command-line option. For valid options, check the GBase 8s ESQL/COBOL Programmer's Supplement for Microsoft Windows Environments.

对于 ESQL/COBOL：此版本不支持指定的命令行选项。要获得有效的选项，请查看GBase 8s ESQL/COBOL Programmer's Supplement for Microsoft Windows Environments。

-55911 Unable to open the log file.

For ESQL/C: Unable to open the ESQL/C preprocessor log file. Probably no space is available. Increase available space and enter the command again.

对于 ESQL/C：无法打开 ESQL/C 预处理程序日志文件。可能没有空间了。增加可用空间并再次输入命令。

For ESQL/COBOL: Unable to open the ESQL/COBOL preprocessor log file.

Probably no space is available. Increase available space and enter the command again.

对于 ESQL/COBOL：无法打开 ESQL/COBOL 预处理程序日志文件。可能没有空间了。增加可用空间并再次输入命令。

-55912 Incompatible file extension for -e option.

For ESQL/C: You specified the -e command-line option but did not specify an ESQL/C source file (.ec file extension). Enter the command again, specifying the name of the .ec file.

对于 ESQL/C：您指定了 -e 命令行选项，但没有指定 ESQL/C 源文件（.ec 文件扩展名）。再次输入命令，指定 .ec 文件的名称。

For ESQL/COBOL: You specified the -e command-line option but did not specify an ESQL/COBOL source file (.eco file extension). Enter the command again, specifying the name of the .eco file.

对于 ESQL/COBOL：您指定了 -e 命令行选项，但没有指定 ESQL/COBOL 源文件(.eco 文件扩展名)。再次输入命令，指定 .eco 文件的名称。

-55913 Missing target filename for `-o' option.

You specified the -o command-line option but did not specify an output file. Enter the command again, specifying the filename of the output file.

您指定了 -o 命令行选项，但没有指定输出文件。再次输入命令，指定输出文件的文件名。

-55914 Incompatible file extension for `-c' option.

You specified the -c command-line option but specified an incompatible file extension. Enter the command again, specifying the name of the file with a compatible file extension.

您指定了 -c 命令行选项，但指定了不兼容的文件扩展名。再次输入命令，指定具有兼容文件扩展名的文件名。

-55915 Missing name of log file for `-log' option.

You specified the -log command-line option but omitted a filename for the log file. Enter the command again, specifying the name of the log file.

您指定了 -log 命令行选项，但忽略了日志文件的文件名。再次输入命令，指定日志文件的名称。

-55917 Compiler option conflict.

You specified more than one command-line option that identifies the compiler type (for example, -mc and -bc). Enter the esql command again without the conflicting option.

您指定了多个命令行选项来标识编译器类型(例如 -mc 和 -bc)。再次输入 esql 命令，不要使用冲突选项。

-55918 Missing name of source file list file for '-f' option.

For ESQL/C: You specified the -f command-line option but omitted a filename for the list of ESQL/C source files. Enter the command again,specifying the name of the list file.

对于 SQL/C：您指定了 -f 命令行选项，但省略了 ESQL/C 源文件列表的文件名。再次输入命令，指定列表文件的名称。

For ESQL/COBOL: You specified the -f command-line option but omitted a filename for the list of ESQL/COBOL source files. Enter the esqlcobo command again, specifying the name of the list file.

对于ESQL/COBOL：您指定了-f命令行选项，但省略了ESQL/COBOL源文件列表的文件名。再次输入esqlcobo命令，指定列表文件的名称。

对于 ESQL/COBOL：您指定了 -f 命令行选项，但省略了 ESQL/COBOL 源文件列表的文件名。再次输入 esqlcobo 命令，指定列表文件的名称。

-55919 Application type option conflict.

For ESQL/C: You specified more than one application type option (for example, -wd and -target:exe). Enter the esql command again without the conflicting options.

对于 ESQL/C：您指定了多个应用程序类型选项(例如 -wd 和 -target:exe)。再次输入esql 命令，不要使用冲突的选项。

For ESQL/COBOL: You specified more than one application type option(for example, -wd and -target:exe). Enter the esqlcobo command again without the conflicting options.

对于 ESQL/COBOL：您指定了多个应用程序类型选项(例如 -wd 和 -target:exe)。再次输入 esqlcobo 命令，不要使用相互冲突的选项。

-55920 Cannot open ESQL response file 'file_name'.

For ESQL/C: The esql command processor cannot open the specified ESQL command-line response file. Verify that the name of the file after the'@' option exists.

对于 ESQL/C：esql 命令处理器无法打开指定的 ESQL 命令行响应文件。验证“@”选项后的文件名是否存在。

For ESQL/COBOL: The esqlcobo command processor cannot open the specified ESQLCOBO command-line response file. Verify that the name of the file after the `@' option exists.

对于 ESQL/COBOL：esqlcobo 命令处理器无法打开指定的 ESQLCOBO 命令行响应文件。验证“@”选项后面的文件名是否存在。

-55921 Unable to allocate memory.

For ESQL/C: ESQL cannot allocate memory. Terminate one or more applications and enter the command again.

对于 ESQL/C：ESQL 不能分配内存。终止一个或多个应用程序并再次输入命令。

For ESQL/COBOL: ESQL/COBOL cannot allocate memory. Terminate one or more applications and enter the command again.

对于 ESQL/COBOL：ESQL/COBOL 无法分配内存。终止一个或多个应用程序并再次输入命令。

-55922 Preprocessor detected errors.

For ESQL/C: The ESQL/C preprocessor detected one or more errors,causing the processor to stop. Correct the errors and rerun.

对于 ESQL/C：ESQL/C 预处理器检测到一个或多个错误，导致处理器停止。纠正错误并重新运行。

For ESQL/COBOL: The ESQL/COBOL preprocessor detected one or more errors, causing the esqlcobo command processor to stop. Correct the errors and rerun.

对于 ESQL/C：ESQL/COBOL预处理器检测到一个或多个错误，导致 esqlcobo 命令处理器停止。更正错误并重新运行。

-55923 No source or object file.

You did not specify the name of a source or the program object file. No files could be passed to the linker. Enter the command again,specifying the name of the file to pass to the linker.

您没有指定源或程序对象文件的名称。无法将任何文件传递给链接器。再次输入命令，指定要传递给链接器的文件的名称。

-55925 Cannot open file 'file_name'.

For ESQL/C: The esql command processor could not open the specified file. If you specified the -f option, check that the source list file exists. If -f was omitted, this error indicates that the processor cannot find the necessary space to create some file.

对于 ESQL/C：esql 命令处理器无法打开指定的文件。如果指定了 -f 选项，请检查源列表文件是否存在。如果省略了 -f，则此错误表示处理器无法找到创建某个文件所需的空间。

For ESQL/COBOL: The esqlcobo command processor could not open the specified file. If you specified the -f option, check that the source list file exists. If -f was omitted, this error indicates that the processor cannot find the necessary space to create some file.

对于 ESQL/COBOL：esqlcobo 命令处理器无法打开指定的文件。如果指定了 -f 选项，请检查源列表文件是否存在。如果省略了 -f，则此错误表示处理器无法找到创建某个文件所需的空间。

-55926 Unable to spawn the compiler.

For ESQL/C: The esql command processor cannot start the compiler. Make sure the directory that contains your C compiler is included in the PATH environment variable.

对于 ESQL/C：esql 命令处理器无法启动编译器。确保包含 C 编译器的目录包含在 PATH环境变量中。

For ESQL/COBOL: The esqlcobo command processor cannot start the compiler. Make sure the directory that contains your COBOL compiler is included in the PATH environment variable.

对于 ESQL/COBOL：esqlcobo 命令处理器无法启动编译器。确保包含 COBOL 编译器的目录包含在 PATH 环境变量中。

-55927 Unable to spawn the linker.

For ESQL/C: The esql command processor cannot start the linker. Make sure the directory that contains your linker is included in the PATH environment variable.

对于 ESQL/C：esql 命令处理器无法启动链接器。确保包含链接器的目录包含在 PATH 环境变量中。

For ESQL/COBOL: The esqlcobo command processor cannot start the linker. Make sure that the directory containing your linker is included in the PATH environment variable.

对于 ESQL/COBOL：esqlcobo 命令处理器无法启动链接器。确保包含链接器的目录包含在PATH 环境变量中。

-55928 Unable to spawn the resource compiler.

For ESQL/C: The esql command processor cannot start the resource compiler. Make sure the directory that contains your resource compiler is included in the PATH environment variable.

对于 ESQL/C：esql 命令处理器无法启动资源编译器。确保包含资源编译器的目录包含在PATH 环境变量中。

For ESQL/COBOL: The esqlcobo command processor cannot start the resource compiler. Make sure the directory that contains your resource compiler is included in the PATH environment variable.

对于 ESQL/COBOL：esqlcobo 命令处理器无法启动资源编译器。确保包含资源编译器的目录包含在 PATH 环境变量中。

-55929 Missing ESQL response file.

For ESQL/C: The esql command processor cannot locate the ESQL command-line response file (specified after the '@'). Verify that the filename is correct.

对于 ESQL/C：esql 命令处理器无法定位 ESQL 命令行响应文件(在“@”之后指定)。验证文件名是否正确。

For ESQL/COBOL: The esqlcobo command processor cannot locate the ESQLCOBO command-line response file (specified after the `@'). Verify that the filename is correct.

对于 ESQL/COBOL：esqlcobo 命令处理器无法定位 ESQLCOBO 命令行响应文件(在`@‘之后指定)。验证文件名是否正确。

-55930 Too many parameters specified.

You exceeded the maximum number of parameters for the preprocessor,compiler, linker (linker options or list of libraries), or resource compiler. Reduce the number of parameters and run the command again.

您超过了预处理器、编译器、链接器（链接器选项或库列表）或资源编译器的最大参数。

减少参数并再次运行命令。

-55931 No source file provided.

For ESQL/C: You have not provided the name of an ESQL/C source file.

Possibly you specified the -e option (preprocess only) and omitted the name of an ESQL/C source file (.ec file extension). Possibly you specified the -c option (preprocess and compile only) and omitted the name of an ESQL/C source file (.ec) or C source file (.c).

对于 ESQL/C：您没有提供 ESQL/C 源文件的名称。可能您指定了 -e 选项(仅预处理)并省略了 ESQL/C 源文件的名称(.ec文件扩展名)。可能您指定了 -c 选项(仅用于预处理和编译)，并省略了 ESQL/C 源文件(.ec)或 C 源文件(.C)的名称。

For ESQL/COBOL: You have not provided the name of an ESQL/COBOL source file. Possibly you specified the -e option (preprocess only) and omitted the name of an ESQL/COBOL source file (.eco file extension).

Possibly you specified the -c option (preprocess and compile only) and omitted the name of an ESQL/COBOL source file (.eco) or COBOL source file (.cbl).

对于 ESQL/COBOL：您没有提供 ESQL/COBOL 源文件的名称。可能您指定了 -e 选项(仅预处理)并省略了 ESQL/COBOL 源文件的名称 (.eco文件扩展名)。可能您指定了 -c 选项(仅用于预处理和编译)，并省略了 ESQL/COBOL 源文件(.ECO)或 COBOL 源文件(.cbl)的名称。

-55932 File_name has incompatible file format.

The command-line response file file_name is too large. Decrease its size and run the command again.

命令行响应文件 file_name 太大了。缩小其大小并再次运行该命令。

-55933 esql: error error_num: Multibyte filter detected error.

The ESQL/C multibyte filter has encountered one of the following conditions:ESQL/C 多字节过滤器遇到下列情况之一：-Unable to initialize GLS library routines-无法初始化 GLS 库例程-Unable to write to the source (.c) file when it renames the file-当源(.c)文件重命名时无法写入该文件-Unable to write to the output file-无法写入输出文件-Some other I/O error-其他I/O错误Check the file permissions on the directory that contains your ESQL/C source file to ensure that you have read and write permission. Also check the file permissions on the ESQL/C source file itself to ensure that you have read and write permission.

检查包含 ESQL/C 源文件的目录上的文件权限，以确保您具有读写权限。还检查 ESQL/C源文件本身的文件权限，以确保您具有读写权限。

-73002 Cannot issue a SQL statement in the secondary thread.

You need to define the user-defined routine as variant.

您需要将用户定义的例程定义为变量。

-73003 An invalid argument is specified.

Either the return type buffer is empty or the length of the buffer is not valid.

返回类型缓冲区为空或缓冲区长度无效。

-73018 Unsupported data type.

Check the file permissions on the directory that contains your ESQL/C source file to ensure you have read and write permission. Also check the file permissions on the ESQL/C source file itself to ensure you have read and write permission.

检查包含 ESQL/C 源文件的目录上的文件权限，以确保您具有读写权限。还要检查ESQL/C 源文件本身的文件权限，以确保您具有读写权限。

-79700 Method not supported.

GBase 8s JDBC Driver does not support this JDBC method.

GBase 8s JDBC 驱动程序不支持此 JDBC 方法。

-79701 Blob not found The GBase 8s JDBC Driver encountered an exception during the access of BLOB. With JDK 1.4 and above, the initial exception is available through the cause facility of java.lang.Throwable.

GBase 8s JDBC 驱动程序在访问 BLOB 期间遇到异常。在 JDK 1.4 和更高版本中，初始异常可以通过 java.lang.Throwable 的原因工具获得。

-79702 Can't create new object The software could not allocate memory for a new String object.

软件无法为新的字符串对象分配内存。

-79703 Row/column index out of range The row or column index is out of range. Compare the index to the number of rows and columns expected from the query to ensure that it is within range.

行或列索引超出范围。将索引与查询所期望的行数和列数进行比较，以确保其在范围内。

-79704 Can't load driver GBase 8s JDBC Driver could not create an instance of itself and register it in the DriverManager class. The rest of the SQLException text describes what failed.

GBase 8s JDBC 驱动程序无法创建自身的实例并将其注册到 DriverManager 类中。SQLException 文本的其余部分描述了失败的原因。

-79705 Incorrect URL format The database URL you have submitted is invalid. GBase 8s JDBC Driver does not recognize the syntax. Check the syntax and try again.

您提交的数据库 URL 无效。GBase 8s JDBC 驱动程序不识别语法。检查语法，然后再试一次。

-79706 Incomplete input An invalid character was found during conversion of a String value to an IntervalDF or IntervalYM object. For correct values, see the GBase 8s JDBC Driver Programmer's Guide.

在将 String 值转换为 IntervalDF 或 IntervalYM 对象时发现无效字符。有关正确的值，请参阅 GBase 8s JDBC 驱动程序员指南。

-79707 Invalid qualifier.

An error was found during construction of an INTERVAL qualifier from atomic elements: length, start, or end values. Check the length, start,and end values to verify that they are correct.

在从原子元素(长度、开始值或结束值)构造 INTERVAL 限定符时发现了一个错误。检查长度、开始值和结束值以验证它们是否正确。

For correct values, see the GBase 8s JDBC Driver Programmer's Guide.

要获得正确的值，请参阅 GBase 8s JDBC 驱动程序员指南。

-79708 Can't take null input.

The string you provided is null. GBase 8s JDBC Driver does not understand null input in this case.

您提供的字符串为空。在本例中，GBase 8s JDBC 驱动程序不理解空输入。

Check the input string to ensure that it has the proper value.

请检查输入字符串，以确保它具有正确的值。

-79709 Error in date format.

The expected input is a valid date string in the following format:yyyy-mm-dd.

预期的输入是以下格式的有效日期字符串：yyyy-mm-dd。

Check the date and verify that it has a four-digit year followed by a valid two-digit month and two-digit day. The delimiter must be a hyphen (-).

检查日期，并验证它有一个四位数的年份，然后是一个有效的两位数的月份和两位数的日期。分隔符必须是连字符(-)。

-79710 Syntax error in SQL escape clause.

Invalid syntax was passed to a JDBC escape clause. Curly braces and a keyword demarcate valid JDBC escape clause syntax: for example,{keyword syntax}.

将无效语法传递给 JDBC 转义子句。大括号和关键字划分有效的 JDBC 转义子句语法：例如，{关键字语法}。

Check the JDBC 2.0 documentation from Sun Microsystems for a list of valid escape clause keywords and syntax.

查看 Sun Microsystems 的 JDBC 2.0 文档，以获得有效转义子句关键字和语法的列表。

-79711 Error in time format.

An invalid time format was passed to a JDBC escape clause.

向 JDBC 转义子句传递了无效的时间格式。

The escape clause syntax for time literals has the following format:时间文本的转义子句语法具有以下格式：{t "hh:mm:ss"}.

-79712 Error in timestamp format.

An invalid timestamp format was passed to a JDBC escape clause.

向 JDBC 转义子句传递了无效的时间戳格式。

The escape clause syntax for timestamp literals has the following format:时间戳文本的转义子句语法具有以下格式：{ts "yyyy-mm-dd hh:mm:ss.f..."}.

-79713 Incorrect number of arguments.

An incorrect number of arguments was passed to the scalar function escape syntax. The correct syntax is {fn function(arguments)}.

将不正确的参数传递给标量函数转义语法。正确的语法是{fn 函数(参数)}。

Verify that the correct number of arguments was passed to the function.

验证传递给函数的参数数目是否正确。

-79714 Type not supported.

You specified a data type that GBase 8s JDBC Driver does not support.

您指定了GBase 8s JDBC 驱动程序不支持的数据类型。

Check your program to make sure the data type is among those that the driver supports.

请检查您的程序，以确保数据类型在驱动程序支持的数据类型中。

-79715 Syntax error.

Invalid syntax was passed to a JDBC escape clause. Curly braces and a keyword demarcate valid JDBC escape clause syntax: for example,{keyword syntax}.

将无效语法传递给 JDBC 转义子句。大括号和关键字划分有效的 JDBC 转义子句语法：例如，{关键字语法}。

Check the JDBC 2.0 documentation from Sun Microsystems for a list of valid escape clause keywords and syntax.

请查看 Sun Microsystems 的 JDBC 2.0 文档，以获得有效转义子句关键字和语法的列表。

-79716 System or internal error.

An operating or runtime system error or a driver internal error occurred.

发生了操作或运行时系统错误或驱动程序内部错误。

The accompanying message describes the problem.

所附消息描述了问题。

-79717 Invalid qualifier length.

The length value for an INTERVAL object is incorrect.

INTERVAL 对象的长度值是不正确的。

For correct values, see the GBase 8s JDBC Driver Programmer's Guide.

要获得正确的值，请参阅 GBase 8s JDBC 驱动程序员指南。

-79718 Invalid qualifier start code.

The start value for an INTERVAL object is incorrect.

INTERVAL 对象的开始值不正确。

For correct values, see the GBase 8s JDBC Driver Programmer's Guide.

要获得正确的值，请参阅 GBase 8s JDBC 驱动程序员指南。

-79719 Invalid qualifier end code.

The end value for an INTERVAL object is incorrect.

INTERVAL 对象的结束值不正确。

For correct values, see the GBase 8s JDBC Driver Programmer's Guide.

要获得正确的值，请参阅 GBase 8s JDBC 驱动程序员指南。

-79720 Invalid qualifier start or end code.

The start or end value for an INTERVAL object is incorrect.

INTERVAL 对象的开始值或结束值不正确。

For correct values, see the GBase 8s JDBC Driver Programmer's Guide.

要获得正确的值，请参阅 GBase 8s JDBC 驱动程序员指南。

-79721 Invalid interval string.

An error occurred during conversion of a STRING value to an IntervalDF or IntervalYM object.

将 STRING 值转换为 IntervalDF 或 IntervalYM 对象时发生错误。

For the correct format, see the GBase 8s JDBC Driver Programmer's Guide.

要获得正确的值，请参阅 GBase 8s JDBC 驱动程序员指南。

-79722 Numeric characters expected.

An error occurred during conversion of a STRING value to an IntervalDF or IntervalYM object. A numeric value was expected and not found.

将 STRING 值转换为 IntervalDF 或 IntervalYM 对象时发生错误。需要一个数值，但找不到。

For the correct format, see the GBase 8s JDBC Driver Programmer's Guide.

要获得正确的值，请参阅 GBase 8s JDBC 驱动程序员指南。

-79723 Delimiter characters expected.

An error occurred during conversion of a STRING value to an IntervalDF or IntervalYM object. A delimiter was expected and not found.

将 STRING 值转换为 IntervalDF 或 IntervalYM 对象时发生错误。需要一个分隔符，但找不到。

For the correct format, see the GBase 8s JDBC Driver Programmer's Guide.

要获得正确的值，请参阅 GBase 8s JDBC 驱动程序员指南。

-79724 Characters expected.

An error occurred during conversion of a STRING value to an IntervalDF or IntervalYM object. End of string was encountered before conversion was complete.

将 STRING 值转换为 IntervalDF 或 IntervalYM 对象时发生错误。在完成转换之前，会遇到字符串的结束。

For the correct format, see the GBase 8s JDBC Driver Programmer's Guide.

要获得正确的值，请参阅 GBase 8s JDBC 驱动程序员指南。

-79725 Extra characters found.

An error occurred during conversion of a STRING value to an IntervalDF or IntervalYM object. End of string was expected, but more characters were in the string.

将 STRING 值转换为 IntervalDF 或 IntervalYM 对象时发生错误。字符串的结尾是预期的，但字符串中有更多的字符。

For the correct format, see the GBase 8s JDBC Driver Programmer's Guide.

要获得正确的值，请参阅 GBase 8s JDBC 驱动程序员指南。

-79726 Null SQL statement.

The SQL statement passed in was null.

传入的 SQL 语句为空。

Check the SQL statement string in your program to make sure the string contains a valid statement.

请检查程序中的 SQL 语句字符串，以确保字符串包含有效语句。

-79727 Statement was not prepared.

The SQL statement contains one or more host variables but was not prepared properly.

SQL 语句包含一个或多个主机变量，但没有正确准备。

If you use host variables in your SQL statement (for example, insert into mytab values (?, ?);), you must use connection.prepareStatement()to prepare the SQL statement before you can execute it.

如果在 SQL 语句中使用主机变量(例如，insert into mytab values (?, ?);)，则必须在执行 SQL 语句之前使用 connection.prepareStatement() 准备 SQL 语句。

-79728 Unknown object type.

If this object type is a null opaque type, the type is unknown and cannot be processed. If this object type is a complex type, the data in the collection or array is of an unknown type and cannot be mapped to a GBase 8s type. If this object type is a row, one of the elements in the row cannot be mapped to an Gbasedbt type.

如果此对象类型为空不透明类型，则该类型未知，无法处理。如果此对象类型是复杂类型，则集合或数组中的数据是未知类型，无法映射到 GBase 8s 类型。如果此对象类型是行，则行中的一个元素不能映射到 GBase 8s 类型。

Verify the customized type mapping or data type of the object.

验证对象的自定义类型映射或数据类型。

-79729 Method cannot take argument.

An argument was supplied for a method that does not take an argument.

为不接受参数的方法提供了参数。

Refer to your Java API specification or the GBase 8s JDBC Driver Programmer's Guide to make sure you are using the method properly.

请参考您的 Java API 规范或 GBase 8s JDBC 驱动程序指南，以确保正确使用该方法。

-79730 Connection not established.

A method was not called to establish a connection.

没有调用方法来建立连接。

You must obtain the connection by calling the DriverManager.getConnection() method first.

您必须首先调用 DriverManager.getConnection() 方法来获得连接。

-79731 MaxRows out of range.

The specified MaxRows value is invalid because it is not within the range of possible values for MaxRows.

指定的 MaxRows 值无效，因为它不在 MaxRows 的可能值范围内。

Make sure you specify a value between 0 and Integer.MAX_VALUE.

请确保在 0 和 Integer.MAX_VALUE 之间指定一个值。

-79732 Illegal cursor name.

The specified name is not a valid cursor name.

指定的名称不是有效游标名。

Make sure the string passed in is not null or empty.

确保传入的字符串非空或者不是空的。

-79733 No active result.

The statement does not contain an active result.

该语句不包含活动结果。

Check your program logic to make sure you have called the executeXXX()method before you refer to the result.

在引用结果之前，请检查您的程序逻辑，以确保您已经调用了 executeXXX() 方法。

-79734 GBASEDBTSERVER has to be specified.

GBASEDBTSERVER is a property required for connecting to a GBase 8s database.

GBASEDBTSERVER 是连接到 GBase 8s 数据库所需的属性。

You can specify the GBASEDBTSERVER property in the database URL or as part of a properties object that is passed to the connect() method.

可以在数据库 URL 中指定 GBASEDBTSERVER 属性，也可以将其指定为传递给 connect()方法的属性对象的一部分。

-79735 Can't instantiate protocol.

An internal error occurred during a connection attempt.

在尝试连接时发生内部错误。

Call GBase Technical Support.

请致电 GBase 技术支持。

-79736 No connection/statement establish yet.

There is no current connection or statement.

没有当前连接或语句。

Check your program to make sure a connection was properly established or a statement was created.

请检查程序，以确保连接已正确建立或语句已创建。

-79737 No meta data.

The SQL statement attempts to use metadata, but no metadata is available.

SQL 语句尝试使用元数据，但没有可用的元数据。

Make sure the statement generates a result set before you attempt to use it.

请确保语句在尝试使用该语句之前生成结果集。

-79738 No such column name.

The specified column does not exist.

指定的列不存在。

Make sure the column name is correct.

请确保列名正确。

-79739 No current row.

The cursor is not properly positioned.

游标的位置不正确。

You must first position the cursor within the result set by using a method such as resultset.next(), resultset.beforefirst(),resultset.first(), or resultset.absolute().

您必须首先通过使用如下方法将游标定位在结果集中，例如 resultset.next()、resultset.beforefirst()、resultset.first() 或 resultset.absolute()。

-79740 No statement created.

There is no current statement.

没有当前语句。

Make sure the statement was properly created.

请确保语句已正确创建。

-79741 Can't convert to.

No data conversion is possible from the column data type to the one specified. The actual data type is appended to the end of this message.

不可能从列数据类型转换到指定的数据类型。实际的数据类型被附加到此消息的末尾。

Review your program logic to make sure that the conversion you asked for is supported. For the data mapping matrix,see the GBase 8s JDBC Driver Programmer's Guide.

检查程序逻辑以确保支持所要求的转换。有关数据映射矩阵，请参阅 GBase 8s JDBC驱动程序员指南。

-79742 Can't convert from.

No data conversion is possible from the data type you specified to the column data type. The actual data type is appended to the end of this message.

不可能从指定的数据类型转换为列数据类型。实际的数据类型被附加到此消息的末尾。

Check your program logic to make sure that the conversion you asked for is supported. For the data mapping matrix, see the GBase 8s JDBC Driver Programmer's Guide.

检查您的程序逻辑，以确保支持您所要求的转换。有关数据映射矩阵，请参阅 GBase 8s JDBC 驱动程序员指南。

-79743 Forward fetch only.

This error number is not in use by a current version of GBase 8s JDBC Driver.

当前版本的 GBase 8s JDBC 驱动程序不使用此错误号。

-79744 Transactions not supported.

The user tried to call commit() or rollback() on a database that does not support transactions or has tried to set autoCommit to false on a nonlogging database.

用户试图在不支持事务的数据库上调用 commit() 或 rollback() ，或者试图在非日志数据库上将 autoCommit 设置为 false。

Verify that the current database has the correct logging mode and review the program logic.

请验证当前数据库具有正确的日志记录模式并检查程序逻辑。

-79745 Read only mode not supported.

GBase 8s does not support read-only mode.

GBase 8s 不支持只读模式。

-79746 No Transaction Isolation on non-logging db's.

GBase 8s does not support setting the transaction isolation level on nonlogging databases.

GBase 8s 不支持在非日志数据库上设置事务隔离级别。

-79747 Invalid transaction isolation level.

If the database server could not complete the rollback, this error occurs.

如果数据库服务器无法完成回滚，则会发生此错误。

For details about why the rollback failed, see the rest of the SQLException message. This error also occurs if an invalid transaction level is passed to setTransactionIsolation(). The valid values follow:有关回滚失败的详细信息，请参阅 SQLException 消息的其余部分。如果将无效的事务级别传递给 setTransactionIsolation()，也会发生此错误。有效值如下：TRANSACTION_READ_UNCOMMITTED TRANSACTION_READ_COMMITTED TRANSACTION_REPEATABLE_READ TRANSACTION_SERIALIZABLE-79748 Can't lock the connection.

GBase 8s JDBC Driver normally locks the connection object just before beginning the data exchange with the database server. The driver could not obtain the lock.

GBase 8s JDBC 驱动程序通常在开始与数据库服务器进行数据交换之前锁定连接对象。

驱动程序无法获得锁。

Only one thread at a time should use the connection object.

次只有一个线程应该使用连接对象。

-79749 Number of input values does not match number of question marks.

The number of variables that you set using the PreparedStatement.setXXX()methods in this statement does not match the number of ? placeholders that you wrote into the statement.

在此语句中使用 PreparedStatement.setXXX() 方法设置的变量数与写入语句的？占位符的数量不匹配。

Locate the text of the statement and verify the number of placeholders,and then check the calls to PreparedStatement.setXXX().

找到语句的文本并验证占位符的数量，然后检查对 PreparedStatement.setXXX() 的调用。

-79750 Method only for queries.

The Statement.executeQuery(String) and PreparedStatement.executeQuery()methods should only be used if the statement is a SELECT statement.

仅当语句是 SELECT 语句时才使用 Statement.executeQuery(String) 和PreparedStatement.executeQuery() 方法。

For other statements, use the Statement.execute(String),Statement.executeBatch(), Statement.executeUpdate(String),Statement.getUpdateCount(), Statement.getResultSet(),or PreparedStatement.executeUpdate() method.

对于其他语句，使用 Statement.execute(String)、Statement.executeBatch()、Statement.executeUpdate(String)、Statement.getUpdateCount()、Statement.getResultSet()或 PreparedStatement.executeUpdate() 方法。

-79751 Forward fetch only.

The result set is not set to FETCH_FORWARD.

结果集未设置为 FETCH_FORWARD。

Call Resultset.setFetchDirection(ResultSet.FETCH_FORWARD) to reset the direction.

调用 Resultset.setFetchDirection(ResultSet.FETCH_FORWARD) 来重置方向。

-79752 Insufficient Blob data The GBase 8s JDBC Driver encountered an unexpected exception during the access of BLOB. The GBase 8s JDBC Driver was unable to transfer the specified number of bytes.

GBase 8s JDBC 驱动程序在访问 BLOB 期间遇到意外异常。GBase 8s JDBC 驱动程序无法传输指定的字节数。

-79753 Out of Blob memory The GBase 8s JDBC Driver was unable to allocate memory while handling BLOB data.This error occurs when the JDBC driver fails to allocate memory required to perform LOB operations in memory.

You can reset the LOBCACHE or IFX_CODESETLOB properties to perform blob operations using temporary files rather than using memory.

GBase 8s JDBC 驱动程序在处理 BLOB 数据时无法分配内存，当 JDBC 驱动程序无法分配内存中执行LOB操作所需的内存时，就会发生此错误。您可以重置 LOBCACHE 或IFX_CODESETLOB 属性来使用临时文件而不是使用内存执行 BLOB 操作。

-79754 Write Fault The GBase 8s JDBC Driver encountered an error writing to a temporary file while handling LOB data.

GBase 8s JDBC 驱动程序在处理LOB数据时遇到了写入临时文件的错误。

-79755 Object is null.

The object passed in is null.

传入的对象为空。

Check your program logic to make sure your object reference is valid.

请检查程序逻辑以确保对象引用是有效的。

-79756 must start with 'jdbc'.

The first token of the database URL is not the keyword jdbc (case insensitive).

数据库 URL 的第一个令牌不是关键字 jdbc(大小写不敏感)。

Start the URL with jdbc, as in the following example:用 JDBC 启动 URL，如下面的例子：jdbc:gbasedbt-sqli://mymachine:1234/mydatabase:user=me:password=secret-79757 Invalid sub-protocol.

The current valid subprotocol that GBase 8s supports is gbasedbt-sqli.

GBase 8s 支持的当前有效子协议是 gbasedbt-sqli。

Use the gbasedbt-sqli subprotocol.

使用 gbasedbt-sqli 子协议。

-79758 Invalid ip address.

The format of the database server's IP address is invalid.

数据库服务器的 IP 地址格式无效。

When you connect to a GBase 8s database server with an IP address,specify the IP address in the correct format. A valid IP address is a set of four numbers between 0 and 255, separated by dots (.): for example, 127.0.0.1.

使用 IP 地址连接到 GBase 8s 数据库服务器时，请以正确的格式指定IP地址。一个有效的 IP 地址是一个由 0 到 255 之间的四个数字组成的集合，由 dots(.)隔开：例如，127.0.0.1。

-79759 Invalid port number.

The port number must be a valid four-digit number, as follows:端口号必须是有效的四位数字，如下所示：jdbc:gbasedbt-sqli://mymachine:1234/mydatabase:user=me:password=secret In this example, 1234 is the port number.

在本例中，1234 是端口号。

-79760 Invalid database name.

This statement contains the name of a database in some invalid format.

此语句以某种无效格式包含数据库名称。

The maximum length for database names and cursor names depends on the version of the database server.

extension.

数据库名称和游标名称的最大长度取决于数据库服务器的版本。

-79761 Invalid Property format.

The database URL accepts property values in key=value pairs. For example,user=gbasedbt:password=gbasedbt adds the key=value pairs to the list of properties that are passed to the connection object.

数据库 URL 接受键=值对中的属性值。例如，user=gbasedbt：password=gbasedbt 将键=值对添加到传递给连接对象的属性列表中。

Check the syntax of the key=value pair for syntax errors. Make sure there is only one = sign; that no spaces separate the key, value,or =; and that key=value pairs are separated by one colon (:), again with no spaces.

检查键=值对的语法是否有语法错误。确保只有一个 = 符号；没有空格来分隔键、值或 =；键=值对由一个冒号(：)分隔，同样没有空格。

-79763 Only CONCUR_READ_ONLY is supported.

GBase 8s JDBC Driver supports only the ResultSet.CONCUR_READ_ONLY method.

GBase 8s JDBC 驱动程序只支持 ResultSet.CONCUR_READ_ONLY 方法。

You can only call the Connection.createStatement(int, int),Connection.prepareStatement(String, int, int), or Connection.CallableStatement(String, int, int) method with a result set concurrency value of CONCUR_READ_ONLY.

只能调用 Connection.createStatement(int, int)、Connection.prepareStatement(String, int, int), 或Connection.CallableStatement(String, int, int)方法，其结果集并发值为CONCUR_READ_ONLY。

-79764 Invalid Fetch Direction value.

An invalid fetch direction was passed as an argument to the Statement.setFetchDirection() or ResultSet.setFetchDirection() method.

将一个无效的提取方向作为参数传递给 Statement.setFetchDirection() 或ResultSet.setFetchDirection() 方法。

Verify that the argument is one of the valid fetch direction values,which are FETCH_FORWARD, FETCH_REVERSE, and FETCH_UNKNOWN.

验证该参数是有效的 FETCH 方向值之一，这些值是 FETCH_FORWARD、FETCH_REVERSE和 FETCH_UNKNOWN。

-79765 ResultSet Type is TYPE_FETCH_FORWARD, direction can only be FETCH_FORWARD.

The result set type has been set to TYPE_FORWARD_ONLY, but the setFetchDirection() method has been called with a value other than FETCH_FORWARD.

结果集类型已设置为 TYPE_FORWARD_ONLY，但 setFetchDirection() 方法的值不是FETCH_FORWARD。

Verify that the direction specified is consistent with the result type specified.

验证指定的方向是否与指定的结果类型一致。

-79766 Incorrect Fetch Size value.

The Statement.setFetchSize() method has been called with an invalid value.

使用无效值调用 Statement.setFetchSize() 方法。

Verify that the value passed in is greater than 0. If the setMaxRows method has been called, the fetch size must not exceed that value.

验证传入的值大于 0。如果调用了 setMaxRows 方法，则获取大小不能超过该值。

-79767 ResultSet Type is TYPE_FORWARD_ONLY.

A method such as ResultSet.beforeFirst(), ResultSet.afterLast(),ResultSet.first(), ResultSet.last(), ResultSet.absolute(),ResultSet.relative(), ResultSet.current(), or ResultSet.previous()has been called, but the result set type is TYPE_FORWARD_ONLY.

已经调用了一个方法，如 ResultSet.beforeFirst()、ResultSet.afterLast()、ResultSet.first()、ResultSet.last()、ResultSet.absolute()、ResultSet.relative()、ResultSet.current() 或 ResultSet.previous()，但结果集类型是 TYPE_FORWARD_ONLY。

Call only the ResultSet.next() method if the result set type is TYPE_FORWARD_ONLY.

如果结果集类型为 TYPE_FORWARD_ONLY，则只调用 ResultSet.next() 方法。

-79768 Incorrect row value.

The ResultSet.absolute(int) method has been called with a value of 0.

The parameter must be greater than 0.

ResultSet.absolute(int) 方法被 0 值所调用。参数必须大于0。

-79769 A customized type map is required for this data type.

No customized type map exists for an opaque type.

不透明类型不存在自定义类型映射。

You must register a customized type map to use any opaque types.

必须注册自定义类型映射才能使用任何不透明类型。

-79770 Cannot find the SQLTypeName specified in the SQLData or Struct.

The SQLTypename object you specified in the SQLData or Struct class does not exist in the database.

在SQLData或Struct类中指定的SQLTypename对象在数据库中不存在。

Make sure that the type name is valid.

请确保类型名称有效。

-79771 Input value is not valid.

The input value is not accepted for this data type.

此数据类型不接受输入值。

Make sure this input is valid for this data type.

请确保此输入对此数据类型有效。

-79772 No more data to read. Verify your SQLdata class or getSQLTypeName().

You have asked for more data than is available.

您要求的数据比可用的要多。

Check your SQLData class to make sure it matches what is in the database schema. The SQLTypeName object might also be incorrect.

检查 SQLData 类，确保它与数据库模式中的内容匹配。SQLTypeName 对象也可能不正确。

-79773 Invalid arguments.

The GBase 8s JDBC Driver throws this exception whenever a method is called with an invalid argument. Refer to the JDBC API documentation to ensure that a valid argument is being passed to the method that is throwing this exception.

每当调用带有无效参数的方法时，GBase 8s JDBC 驱动程序都会抛出此异常。请参阅JDBC API 文档，以确保向抛出此异常的方法传递有效的参数。

-79774 Unable to create local file.

Large object data read from the database server can be stored either in memory or in a local file. If the LOBCACHE value is 0 or the large object size is greater than the LOBCACHE value, the large object data from the database server is always stored in a file. In this case, if a security exception occurs, GBase 8s JDBC Driver makes no attempt to store the large object into memory and throws this exception.

从数据库服务器读取的大对象数据可以存储在内存中，也可以存储在本地文件中。如果LOBCACHE 值为 0 或大对象大小大于 LOBCACHE 值，则来自数据库服务器的大对象数据始终存储在文件中。在这种情况下，如果发生安全异常，则 GBase 8s JDBC 驱动程序不会尝试将大对象存储到内存中并抛出此异常。

-79775 Only TYPE_SCROLL_INSENSITIVE and TYPE_FORWARD_ONLY are supported.

GBase 8s JDBC Driver only supports a result set type of TYPE_SCROLL_INSENSITIVE and TYPE_FORWARD_ONLY.

GBase 8s JDBC 驱动程序只支持 TYPE_SCROLL_INSENSITIVE 和 TYPE_FORWARD_ONLY 的结果集类型。

Use only these values.

仅使用这些值。

-79776 Type requested () does not match row type information () type.

Row-type information was acquired either through the system catalogs or through the supplied row definition. The row data provided does not match this row element type.

行类型信息是通过系统目录或通过提供的行定义获取的。提供的行数据与此行元素类型不匹配。

The type information must be modified, or the data must be provided.

必须修改类型信息，或者必须提供数据。

-79777 readObject/writeObject() only supports UDTs, Distincts and complex types.

The SQLData.writeObject() method was called for an object that is not a user-defined, distinct, or complex type.

为对象调用 SQLData.writeObject() 方法，该对象不是用户定义的、不同的或复杂的类型。

Verify that you have provided customized type-mapping information.

请确保您提供了自定义的类型映射信息。

-79778 Type mapping class must be a java.util.Collection implementation.

You provided a type mapping to override the default for a set, list, or multiset data type, but the class does not implement the java.util.Collection interface.

您提供了一个类型映射来覆盖 set、List 或 multiset 数据类型的默认值，但是该类没有实现 java.util.Collection 接口。

-79779 To insert null data into a row use java null representation.

The GBase 8s JDBC Driver throws this exception whenever an application attempts to set row column null in an incorrect manner. Ensure that java null representation is used instead of an object to set null data.

每当应用程序试图以不正确的方式设置行列为 null 时，GBase 8s JDBC驱动程序就会抛出此异常。确保使用 java null 表示而不是将对象设置为空数据。

-79780 Data within a collection must all be the same Java class and length.

Collection data was of different Java classes or lengths.

集合的数据是不同的 Java 类或具有不同的长度。

Verify that all the objects in the collection are of the same class.

请集合中的所有对象都属于同一个类。

-79781 Index/Count out of range.

Array.getArray() or Array.getResultSet() was called with index and count values. Either the index is out of range or the count is too big.

使用索引和计数值调用了 Array.getArray() 或 Array.getResultSet()。索引超出范围或计数太大。

Verify that the number of elements in the array is sufficient for the index and count values.

请验证数组中的元素数量是否足以满足索引和计数值的需要。

-79782 Method can be called only once.

Make sure methods like Statement.getUpdateCount() and Statement.getResultSet() are called only once per result.

确保每个结果只调用一次 Statement.getUpdateCount()和Statement.getResultSet()等方法。

-79783 Encoding or code set not supported.

The encoding or code set entered in the DB_LOCALE or CLIENT_LOCALE variable is not valid.

DB_LOCALE 或 CLIENT_LOCALE 变量中输入的编码或代码集无效。

For valid code sets, see the GBase 8s JDBC Driver Programmer's Guide.

有效的代码集，请参阅《GBase 8s JDBC Driver 程序员指南》。

-79784 Locale not supported.

The locale entered in the DB_LOCALE or CLIENT_LOCALE variable is not valid.

DB_LOCALE 或 CLIENT_LOCALE 变量中输入的语言环境无效。

For valid locales, see the GBase 8s JDBC Driver Programmer's Guide.

有效的语言环境，请参阅《GBase 8s JDBC Driver 程序员指南》。

-79785 Unable to convert JDBC escape format date string to localized date string.

The JDBC escape format for date values must be specified in the format{d 'yyyy-mm-dd'}.

日期值的 JDBC 转义格式必须为 {d 'yyyy-mm-dd'}。

Verify that the JDBC escape date format specified is correct. Verify the DBDATE and GL_DATE settings for the correct date string format if either of these was set to a value in the connection database URL string or property list.

验证指定的 JDBC 转义日期格式是否正确。如果将 DBDATE 和 GL_DATE 设置为连接数据库 URL 字符串或属性列表中的值，则验证正确日期字符串格式的 DBDATE和 GL_DATE 设置。

-79786 Unable to build a Date object based on localized date string representation.

The localized date string representation specified in a CHAR, VARCHAR, or LVARCHAR column is not correct, and a date object cannot be built based on the year, month, and day values.

CHAR、VARCHAR 或 LVARCHAR 列中指定的语言环境日期字符串表示形式不正确，并且无法根据年、月和日值构建日期对象。

Verify that the date string representation conforms to the DBDATE or GL_DATE date formats if either one of these is specified in a connection database URL string or property list. If neither DBDATE or GL_DATE is specified but a CLIENT_LOCALE or DB_LOCALE is explicitly set in a connection database URL string or property list, verify that the date string representation conforms to the JDK short default format(DateFormat.SHORT).

如果在连接数据库 URL 字符串或属性列表中指定了日期字符串表示形式，则验证日期字符串表示是否符合 DBDATE 或 GL_DATE 格式。如果没有指定 DBDATE 或 GL_DATE，但在连接数据库 URL 字符串或属性列表中显式设置了 Client_locale 或 DB_locale，则请验证日期字符串表示形式是否符合 JDK 短默认格式 (DateFormates.SHORT)。

-79787 Blob/Clob object has not been created from a BLOB/CLOB column.

The GBase 8s JDBC Driver throws this exception whenever an application calls methods that attempt to use smart large object functionality on an object that does not represent a smart large object.

For example, smart large objects (BLOB or CLOB) support random access to the data while simple large objects (TEXT or BYTE) do not support random access.

Ensure that the object being passed has been created from a smart large object.

只要应用程序调用尝试在不代表智能大对象的对象上使用智能大对象功能的方法，GBase 8s JDBC Driver 就会抛出此异常。例如，智能大对象（BLOB 或 CLOB）支持对数据的随机访问，而简单的大对象（TEXT 或 BYTE）不支持随机访问。确保已从智能大对象创建传递的对象。

-79788 User name must be specified.

The user name is required to establish a connection with GBase 8s JDBC Driver.

用户名是 GBase 8s JDBC Driver 建立连接所必需的。

Make sure you pass in user=your_user_name as part of the database URL or one of the properties.

确保将 user = your_user_name 作为数据库 URL 或其中一个属性的一部分传递。

-79789 Server does not support GLS variables DB_LOCALE, CLIENT_LOCALE,or GL_DATE.

These variables can only be used if the database server supports GLS.

只有在数据库服务器支持 GLS 时才能使用这些变量。

Check the documentation for your database server version and omit these variables if they are not supported.

检查数据库服务器版本的文档，如果不支持，请省略这些变量。

-79790 Invalid complex type definition string.

The value that the getSQLtypeName() method returns is either null or invalid.

getSQLtypeName() 方法返回的值为 null 或无效。

Check the string to verify that it is either a valid named-row name or a valid row-type definition.

检查字符串以验证它是有效的命名行名称还是有效的行类型定义。

-79791 Invalid object. Cannot be inserted into clob/blob column.

GBase 8s JDBC Driver throws this exception whenever an application supplies an invalid object to the JDBC driver for insertion in a clob/blob column.

The JDBC driver attempts to determine if the provided java object may be used for inserting data in a blob/clob column. If the JDBC driver discovers that the object is not compatible, this exception is thrown. Make sure that the application is passing the correct type of object when calling PreparedStatement::setObject() method.

每当应用程序向 JDBC 驱动程序提供无效对象以插入 clob/blob列时，GBase 8s JDBC Driver 就会抛出此异常。JDBC 驱动程序尝试确定提供的 java 对象是否可用于在 blob/clob 列中插入数据。如果 JDBC 驱动程序发现该对象不兼容，则抛出此异常。在调用PreparedStatement::setObject()方法时，确保应用程序正在传递正确类型的对象。

-79792 Row must contain data.

The Array.getAttributes() or Array.getAttributes(Map) method has returned 0 elements.

Array.getAttributes()或 Array.getAttributes(Map)方法返回了 0 个元素。

Make sure the method returns a nonzero number.

确保该方法返回非零数字。

-79793 Data in array does not match getBaseType() value.

The Array.getArray() or Array.getArray(Map) method returns an array where the element type does not match the JDBC base type.

Array.getArray() 或 Array.getArray(Map) 方法返回了一个数组，但其元素类型不符合JDBC 基类。

-79794 Row length provided () doesn't match row type information .

Data in the row does not match the length in the row-type information.

行中的数据不符合行类型信息的长度。

You do not have to pad string lengths to match what is in the row definition, but lengths for other data types should match.

不必填充字符串长度以匹配行定义中的内容，但其他数据类型的长度应匹配。

-79795 Row extended id provided () doesn't match row type information ().

The extended ID of the object in the row does not match the extended ID as defined in row-type information.

行中对象的扩展 ID 与行类型信息中定义的扩展 ID 不匹配。

Either update the row-type information (if you are providing the row definition) or check the type-mapping information.

要么更新行类型信息(如果您正在提供行定义)，要么检查类型映射信息。

-79796 Cannot find UDT, distinct or named row () in database.

The getSQLTypeName() method has returned a name that cannot be found in the database.

getSQLTypeName() 方法返回的名称不在数据库中。

Verify that the Struct or SQLData object returns the correct information.

验证 Struct 或 SQLData 对象返回了正确的信息。

-79797 DBDATE setting must be at least 4 characters and no longer than 6 characters.

This error occurs because the DBDATE format string that is passed to the database server either has too few characters or too many.

发生此错误的原因是传递给数据库服务器的 DBDATE 格式字符串字符太少或太多。

To fix the problem, verify the DBDATE format string with the user documentation and make sure that the correct year, month, day, and possibly era parts of the DBDATE format string are correctly identified.

要解决此问题，请使用用户文档验证 DBDATE 格式字符串，并确保正确标识 DBDATE格式字符串的正确年份、月份、日期和可能的时间部分。

-79798 A numerical year expansion is required after 'Y' character in DBDATE string.

This error occurs because the DBDATE format string has a year designation(specified by the character Y), but no character follows the year designation to denote the numerical year expansion (2 or 4).

发生此错误的原因是 DBDATE 格式字符串具有年份指示符（由字符 Y 指定），但年份后面没有字符表示数字年份扩展（2 位数或 4 位数）。

To fix the problem, modify the DBDATE format string to include the numerical year expansion value after the Y character.

要解决此问题，请修改 DBDATE 格式字符串以包含 Y 字符后面的数字年份扩展值。

-79799 An invalid character is found in the DBDATE string after the 'Y' character.

This error occurs because the DBDATE format string has a year designation (specified by the character Y), but the character that follows the year designation is not a 2 or 4 (for two-digit years and four-digit years, respectively).

发生此错误是因为 DBDATE 格式字符串有一个年份指示符(由字符Y指定)，但在指定年份之后的字符不是 2 或 4(分别用于两位数年份和四位数年份)。

To fix the problem, modify the DBDATE format string to include the required numerical year expansion value after the Y character. Only a 2 or 4 character should immediately follow the Y character designation.

若要解决此问题，请修改 DBDATE 格式字符串，以便在 Y 字符之后包含所需的数字年展开值。

只有 2 或 4 个字符应立即紧跟 Y 字符。

-79800 No 'Y' character is specified before the numerical year expansion value.

This error occurs because the DBDATE format string has a numerical year expansion (2 or 4 to denote two-digit years or four-digit years,respectively), but the year designation character (Y) was not found immediately before the numerical year expansion character specified.

发生此错误的原因是 DBDATE 格式字符串具有数字年份扩展（2 或 4 分别表示两位数年份或四位数年份），但在指定的数字年份扩展字符之前未找到年份指定字符(Y)。

To fix the problem, modify the DBDATE format string to include the required Y character immediately before the numerical year expansion value requested.

要解决此问题，请修改 DBDATE 格式字符串，以便在请求的数字年份扩展值之前包含所需的 Y 字符。

-79801 An invalid character is found in DBDATE format string.

This error occurs because the DBDATE format string has a character that is not allowed.

发生此错误的原因是 DBDATE 格式字符串具有不允许的字符。

To fix the problem, modify the DBDATE format string to include only the correct date part designations: year (Y), numerical year expansion value (2 or 4), month (M), and day (D). Optionally, you can include an era designation (E) and a default separator character (hyphen, dot, or slash), which is specified at the end of the DBDATE format string.

For further information on correct DBDATE format string character designations, refer to the user documentation.

要解决此问题，请修改 DBDATE 格式字符串以仅包括正确的日期部分名称：年(Y)、数字年份扩展值(2 或 4)、月(M)和日(D)。（可选）您可以包含时代标识（E）和默认分隔符（连字符、点或斜杠），它在 DBDATE 格式字符串的末尾指定。有关正确的 DBDATE 格式字符串字符指定的更多信息，请参阅用户文档。

-79802 Not enough tokens are specified in the string representation of a date value.

This error occurs because the date string specified does not have the minimum number of tokens or separators needed to form a valid date value(composed of year, month, and day numerical parts). For example,12/15/98 is a valid date string representation with the slash character as the separator or token. But 12/1598 is not a valid date string representation because there are not enough separators or tokens.

To fix the problem, modify the date string representation to include a valid format for separating the day, month, and year parts of a date value.

发生此错误是因为指定的日期字符串没有形成有效日期值所需的最小数目的标记或分隔符(由年份、月份和日数字部分组成)。例如，12/15/98 是以斜杠字符作为分隔符或标记的有效日期字符串表示形式。但是 12/1598 不是一个有效的日期字符串表示，因为没有足够的分隔符或标记。若要解决此问题，请修改日期字符串表示形式，以包括用于分隔日期值的日期、月份和年份部分的有效格式。

-79803 Date string index out of bounds during date format parsing to build Date object.

This error occurs because there is not a one-to-one correspondence between the date string format required by DBDATE or GL_DATE and the actual date string representation you defined. For example, if GL_DATE is set to %b %D %y and you specify a character string of 'Oct', there is a definite mismatch between the format required by GL_DATE and the actual date string.

发生此错误是因为 DBDATE 或 GL_DATE 所需的日期字符串格式与您定义的实际日期字符串表示之间没有一对一的对应关系。例如，如果 GL_Date 设置为 %b%D%y，并且指定一个字符串‘OCT’，则 GL_DATE 所需的格式与实际日期字符串之间存在不匹配。

To fix the problem, modify the date string representation of the DBDATE or GL_DATE setting so that the date format specified matches one-to-one with the required date string representation.

要解决此问题，请修改 DBDATE 或 GL_DATE 设置的日期字符串表示形式，以便指定的日期格式与所需的日期字符串表示形式一对一匹配。

-79804 No more tokens are found in DBDATE string representation of a date value.

This error occurs because the date string specified does not have any more tokens or separators needed to form a valid date value (composed of year,month, and day numerical parts) based on the DBDATE format string. For example, 12/15/98 is a valid date string representation when DBDATE is set to MDY2/. But 12/1598 is not a valid date string representation because there are not enough separators or tokens.

发生此错误是因为指定的日期字符串不具有基于 DBDATE 格式字符串形成有效日期值（由年、月和日数字部分组成）所需的标记或分隔符。例如，当 DBDATE 设置为 MDY2/ 时，12/15/98 是有效的日期字符串表示。但 12/1598 不是有效的日期字符串表示形式，因为没有足够的分隔符或标记。

To fix the problem, modify the date string representation to include a valid format for separating the day, month, and year parts of a date value based on the DBDATE format string setting.

要解决此问题，请修改日期字符串表示，以包含基于 DBDATE 格式字符串设置分隔日期值的日、月和年部分的有效格式。

-79805 No era designation found in DBDATE/GL_DATE string representation of date value.

This error occurs because the date string specified does not have a valid era designation as required by the DBDATE or GL_DATE format string setting.

For example, if DBDATE is set to Y2MDE-, but the date string representation specified by the user is 98-12-15, this is an error because no era designation is at the end of the date string value.

发生此错误的原因是指定的日期字符串没有 DBDATE 或 GL_DATE 格式字符串设置所需的有效时代标识。例如，如果 DBDATE 设置为 Y2MDE-，但用户指定的日期字符串表示形式为 98-12-15，这是一个错误，因为没有时间标记位于日期字符串值的末尾。

To fix the problem, modify the date string representation to include a valid era designation based on the DBDATE or GL_DATE format string setting. In this example, a date string representation of 98-12-15 AD would probably suffice, depending on the locale.

要解决此问题，请修改日期字符串表示以包含基于 DBDATE 或 GL_DATE 格式字符串设置的有效时代标识。在此示例中，日期字符串表示 98-12-15 AD 可能就足够了，具体取决于区域设置。

-79806 Numerical day value cannot be determined from date string based on DBDATE.

This error occurs because the date string specified does not have a valid numerical day designation as required by the DBDATE format string setting.

For example, if DBDATE is set to Y2MD-, but the date string representation you specify is 98-12-nn, this is an error, because nn is not a valid numerical day representation.

发生此错误是因为指定的日期字符串不具有 DBDATE 格式字符串设置所要求的有效的数字日指定。

例如，如果 DBDATE 设置为 Y2MD-，但是您指定的日期字符串表示形式是 98-12-nn，这是一个错误，因为 nn 不是有效的数字日表示形式。

To fix the problem, modify the date string representation to include a valid numerical day designation (1-31) based on the DBDATE format string setting.

要解决此问题，请修改日期字符串表示，以包含基于 DBDATE 格式字符串设置的有效数字日期指定（1-31）。

-79807 Numerical month value cannot be determined from date string based on DBDATE.

This error occurs because the date string specified does not have a valid numerical month designation as required by the DBDATE format string setting.

For example, if DBDATE is set to Y2MD-, but the date string representation you specify is 98-nn-15, this is an error, because nn is not a valid numerical month representation.

发生此错误是因为指定的日期字符串不具有 DBDATE 格式字符串设置所要求的有效的数字月份指定。

例如，如果 DBDATE 设置为 Y2md-，但是您指定的日期字符串表示形式是98-nn-15，这是一个错误，因为 nn 不是有效的数字月份表示形式。

To fix the problem, modify the date string representation to include a valid numerical month designation (1-12) based on the DBDATE format string setting.

要解决此问题，请修改日期字符串表示形式，以包括基于 DBDATE 格式字符串设置的有效的数字月份指定(1-12)。

-79808 Not enough tokens specified in %D directive representation of date string.

This error occurs because the date string specified does not have the correct number of tokens or separators needed to form a valid date value based on the GL_DATE %D directive (mm/dd/yy format). For example, 12/15/98 is a valid date-string representation based on the GL_DATE %D directive,but 12/1598 is not a valid date-string representation because there are not enough separators or tokens.

发生此错误的原因是指定的日期字符串没有基于 GL_DATE％D 指令（mm/dd/yy 格式）形成有效日期值所需的正确数量的标记或分隔符。例如，12/15/98 是基于 GL_DATE％D 指令的有效日期字符串表示，但 12/1598 不是有效的日期字符串表示，因为没有足够的分隔符或标记。

To fix the problem, modify the date-string representation to include a valid format for the GL_DATE %D directive.

要解决此问题，请修改日期字符串表示以包含 GL_DATE％D 指令的有效格式。

-79809 Not enough tokens specified in %x directive representation of date string.

This error occurs because the date string specified does not have the correct number of tokens or separators needed to form a valid date value based on the GL_DATE %x directive (format required is based on day, month, and year parts, and the ordering of these parts is determined by the specified locale). For example, 12/15/98 is a valid date-string representation based on the GL_DATE %x directive for the U.S. English locale, but 12/1598 is not a valid date-string representation because there are not enough separators or tokens.

发生此错误的原因是指定的日期字符串没有根据 GL_DATE％x 指令形成有效日期值所需的正确数量的标记或分隔符（所需格式基于日、月和年部分，以及这些部分由指定的语言环境决定）。例如，12/15/98 是基于美国英语语言环境的 GL_DATE％x 指令的有效日期字符串表示形式，但 12/1598 不是有效的日期字符串表示形式，因为没有足够的分隔符或标记。

To fix the problem, modify the date-string representation to include a valid format for the GL_DATE %x directive based on the locale.

要解决此问题，请修改日期字符串表示，以包含基于语言环境的 GL_DATE％x 指令的有效格式。

-79810 This release of JDBC requires to be run with JDK 1.2+.

GBase 8s JDBC Driver, Version 2.x, requires a JDK version of 1.2 or greater.

GBase 8s JDBC Driver V2.x，要求 JDK 版本为 1.2 或更高版本。

-79811 Connection without user/password not supported.

You called the getConnection() method for the DataSource object, and the user name or the password is null.

您为 DataSource 对象调用了getConnection() 方法，并且用户名或密码为 null。

Use the user name and password arguments of the getConnection() method or set these values in the DataSource object.

使用 getConnection()方法的用户名和密码参数，或在 DataSource 对象中设置这些值。

-79812 User/Password does not match with Datasource.

You called the getConnection(user, passwd) method for the DataSource object, and the values you supplied did not match the values already found in the data source.

为 DataSource 对象调用了 getConnection(user，passwd)方法，但是提供的值与在数据源中找到的值不一致。

-79813 Cannot call setBindColType() after executeQuery().

GBase 8s JDBC Driver allows an application to specify the output type of the resultset values so that the server can cast to that type before returning to the client. However the output type needs to be specified before the query is executed.This error occurs when an application attempts to specify the output type after the query has been executed.

GBase 8s JDBC Driver 允许应用程序指定结果集值的输出类型，以便服务器可以在返回到客户端之前强制转换为该类型。但是，在执行查询之前需要指定输出类型。

当应用程序在执行查询后尝试指定输出类型时，会发生此错误。

-79814 Blob/Clob object is either closed or invalid.

If you retrieve a smart large object using the ResultSet.getBlob() or ResultSet.getClob() method or create one using the IfxBlob() or IfxCblob()constructor, a smart large object is opened. You can then read from or write to the smart large object.

如果使用 ResultSet.getBlob()或 ResultSet.getClob()方法检索智能大对象或使用IfxBlob()或 IfxCblob()构造函数创建一个智能大对象，则会打开智能大对象。然后，可以读取或写入智能大对象。

After you execute the IfxBlob.close() method, do not use the smart-large-object handle for further read/write operations, or this exception is thrown.

执行 IfxBlob.close()方法后，请不要使用 smart-large-object 句柄进行进一步的读/写操作，否则抛出此异常。

-79815 Not in Insert mode. Need to call moveToInsertRow() first.

You tried to use the insertRow() method, but the mode is not set to Insert.

尝试使用 insertRow() 方法，但是模式没有设置为 Insert。

Call the moveToInsertRow() method before you call insertRow().

请在调用 insertRow() 前调用 moveToInsertRow() 方法。

-79816 Cannot determine the table name.

The table name in the query either is incorrect or refers to a table that does not exist.

查询中的表名不是不正确，就是不存在。

-79817 No serial, rowid, or primary key specified in the statement.

The updatable scrollable feature works only for tables that have a SERIAL column, a primary key, or a row ID specified in the query. If the table does not have any of these, an updatable scrollable cursor cannot be created.

可更新的可滚动功能仅适用于具有查询中指定的 SERIAL 列、主键或行 ID的表。

如果表中没有任何这些项，则无法创建可更新的可滚动游标。

-79818 Statement concurrency type is not set to CONCUR_UPDATABLE.

You tried to call the insertRow(), updateRow(), or deleteRow() method for a statement that has not been created with the CONCUR_UPDATABLE concurrency type.

您尝试为未用 CONCUR_UPDATABLE 并发类型创建的语句调用 insertRow()、updateRow()或 deleteRow()方法。

Re-create the statement with this type set for the concurrency attribute.

使用并发属性类型重新创建语句。

-79819 Still in Insert mode. Call moveToCurrentRow() first.

You cannot call the updateRow() or deleteRow() method while still in Insert mode.

在 Insert 模式下无法调用 updateRow() 或 deleteRow() 方法。

Call the moveToCurrentRow() method first.

请先调用 moveToCurrentRow() 方法。

-79820 Function contains an output parameter.

You have passed in a statement that contains an OUT parameter, but you have not used the drivers CallableStatement.registerOutParameter() and getXXX()methods to process the OUT parameter.

您已经传递了包含 OUT 参数的语句，但没有使用驱动程序 CallableStatement.RegierOutParameter()和 getXXX()方法来处理 OUT 参数。

-79821 Name unnecessary for this data type.

The data type you specified does not require a name.

指定的数据类型不需要名称。

Use another method that does not have a type parameter.

使用另一个没有类型参数的方法。

If you have a data type that requires a name (an opaque type or complex type), you must call a method that has a parameter for the name, such as the following methods:如果您的数据类型需要名称(不透明类型或复杂类型)，则必须调用具有名称参数的方法，如以下方法：public void IfxSetNull(int i, int ifxType, String name)public void registerOutParameter(int parameterIndex, int sqlType,java.lang.String name);public void IfxRegisterOutParameter(int parameterIndex, int ifxType,java.lang.String name);-79822 OUT parameter has not been registered.

The function you specified using the CallableStatement interface has an OUT parameter that has not been registered.

使用 CallableStatement 接口指定的函数具有一个未注册的 OUT 参数。

Call one of the registerOutParameter() or IfxRegisterOutParameter() methods to register the OUT parameter type before you call the executeQuery() method.

在调用 executeQuery() 方法之前，请调用 registerOutParameter() 或 IfxRegisterOutParameter()方法注册 OUT 参数。

-79823 IN parameter has not been set.

The function you specified using the CallableStatement interface has an IN parameter that has not been set.

使用 CallableStatement 接口指定的函数具有一个未设置的 IN 参数。

Call the setNull() or IfxSetNull() method if you want to set a null IN parameter. Otherwise, call one of the set methods inherited from the PreparedStatement interface.

如果要设置 null IN 参数，则调用 setNull() 或 IfxSetNull() 方法。否则，调用从 PreparedStatement 接口继承的 SET 方法之一。

-79824 OUT parameter has not been set.

The function specified using the CallableStatement interface has an OUT parameter that has not been set.

使用 CallableStatement 接口指定的函数具有一个未设置的 OUT 参数。

Call the setNull() or IfxSetNull() method if you want to set a null OUT parameter. Otherwise, call one of the set methods inherited from the PreparedStatement interface.

如果要设置 null OUT 参数，则调用 setNull() 或 IfxSetNull() 方法。否则，调用从 PreparedStatement 接口继承的 SET 方法之一。

-79825 Type name is required for this data type.

This data type is an opaque type, distinct type, or complex type, and it requires a name.

此数据类型是 opaque 类型、distinct 类型或复杂类型，它需要一个名称。

Use set methods for IN parameters and register methods for OUT parameters that take a type name as a parameter.

对 IN 参数使用 set 方法，并为类型名称作为参数的 OUT 参数注册方法。

-79826 Ambiguous java.sql.Type. Use IfxRegisterOutParameter().

The SQL type specified either has no mapping to an GBase 8s data type or has more than one mapping.

指定的 SQL 类型没有映射到 GBase 8s 数据类型或具有多个映射。

Use one of the IfxRegisterOutParameter() methods to specify the GBase 8s data type.

使用 IfxRegisterOutParameter（）方法之一指定 GBase 8s 数据类型。

-79827 Function does not have an output parameter.

This function does not have an OUT parameter, or this function has an OUT parameter whose value the server version does not return. None of the methods in the CallableStatement interface apply.

此函数没有 OUT 参数，或者此函数具有 OUT 参数，其值不是服务器版本不返回的值。

CallableStatement 接口中的所有方法都不适用。

Use the inherited methods from the PreparedStatement interface.

使用 PreparedStatement 接口中的继承方法。

-79828 Function parameter specified is not an OUT parameter.

GBase 8s functions can have only one OUT parameter, and it is always the last parameter.

GBase 8s 函数只能有一个 OUT 参数，它始终是最后一个参数。

-79829 Invalid directive used for the GL_DATE environment variable.

One or more of the directives that the GL_DATE environment variable specifies is not allowed.

不允许 GL_DATE 环境变量指定的一个或多个指令。

For a list of the valid directives for a GL_DATE format, see the GBase 8s JDBC Driver Programmer's Guide.

有关 GL_DATE 格式的有效指令的列表，请参阅 “GBase 8s JDBC Driver 程序员指南”。

-79830 Insufficient information given for building a Time or Timestamp Java object.

For correct performance of string to binary conversions for building a java.sql.Timestamp or java.sql.Time object, all the DATETIME fields must be specified for the chosen date-string representation.

为了正确执行字符串到二进制转换以构建 java.sql.Timestamp 或 java.sql.Time 对象，必须为所选的日期字符串表示指定所有 DATETIME 字段。

For java.sql.Timestamp objects, specify the year, month, day, hour, minute,and second parts in the string representation.

对于 java.sql.Timestamp 对象，请在字符串表示中指定年、月、日、小时、分钟和秒。

For java.sql.Time objects, specify the hour, minute, and second parts in the string representation.

对于 java.sql.Time 对象，请在字符串表示中指定小时、分钟和秒部分。

-79831 Exceeded maximum number of connections configured for Connection Pool Manager.

If you repeatedly connect to a database using a DataSource object without closing the connection, connections accumulate. When the total number of connections for the DataSource object exceeds the maximum limit (100), this error is thrown.

如果使用 DataSource 对象重复连接到数据库而不关闭连接，则会累积连接。当 DataSource 对象的连接总数超过最大限制（100）时，将引发此错误。

-79832 Netscape Exception! Permission to connect denied by user.

User does not have permission to connect.

用户没有权限进行连接。

-79833 Netscape Exception! Unknown exception while enabling privilege.

This error is raised by the GBase 8s JDBC Driver when it fails to perform a privileged operation. Check the java security policy file to make sure that necessary privileges have been granted.

当 GBase 8s JDBC Driver 无法执行特权操作时，会引发此错误。检查 java 安全策略文件以确保已授予必要的权限。

-79834 Distributed transactions (XA) not supported by this server.

This error results when an application attempts to open an XA connection to a server that does not support distributed transactions. Ensure that the server that the application is connecting to supports distributed transactions.

当应用程序尝试打开与不支持分布式事务的服务器的 XA 连接时，会出现此错误。

确保应用程序连接的服务器支持分布式事务。

-79835 RowSet is set to ReadOnly.

This error results when an application attempts an update/insert or delete operation on a read-only RowSet. Ensure that the RowSet in use is not read-only.

当应用程序尝试对只读 RowSet 执行更新/插入或删除操作时，会出现此错误。

确保使用的 RowSet 不是只读的。

-79836 Proxy Error: No database connection.

This error is thrown by the GBase 8s HTTP Proxy if you try to communicate with the database on an invalid or bad database connection.

如果您尝试在无效或错误的数据库连接上与数据库通信，则 GBase 8s HTTP 代理会抛出此错误。

Make sure your application has opened a connection to the database. Check your Web server and database error logs.

确保您的应用程序已打开与数据库的连接。检查 Web 服务器和数据库错误日志。

-79837 Proxy Error: Input/output error while communicating with the database.

This error is thrown by the GBase 8s HTTP Proxy if an error is detected while the proxy is communicating with the database. This error can occur if your database server is not accessible.

如果在代理与数据库通信时检测到错误，则 GBase 8s HTTP 代理会抛出此错误。

如果您的数据库服务器不可访问，则会发生此错误。

Make sure your database server is accessible. Check your database and Web server error logs.

确保您的数据库服务器可访问。检查数据库和 Web 服务器错误日志。

-79838 Cannot execute change permission command (chmod/attrib).

The driver is unable to change the permissions on the client JAR file. This could happen if your client platform does not support the chmod or attrib command, or if the user running the JDBC application does not have the authority to change access permissions on the client JAR file.

驱动程序无法更改客户端 JAR 文件的权限。如果您的客户端平台不支持 chmod 或 attrib 命令，或者运行 JDBC 应用程序的用户无权更改客户端 JAR 文件的访问权限，则可能会发生这种情况。

Make sure the chmod or attrib command is available for your platform and that the user running the application has the authority to change access permissions on the client JAR file.

确保 chmod 或 attrib 命令可用于您的平台，并且运行该应用程序的用户有权更改客户端 JAR 文件的访问权限。

-79839 Same Jar SQL name already exists in the system catalog.

The JAR filename specified when your application called UDTManager.createJar() has already been registered in the database server.

应用程序调用 UDTManager.createJar()时指定的 JAR 文件名已在数据库服务器中注册。

Use UDTMetaData.setJarFileSQLName() to specify a different SQL name for the JAR file.使用 UDTMetaData.setJarFileSQLName() 为 JAR 文件指定不同的 SQL 名称。

-79840 Unable to copy JAR file from client to server.

This error occurs when the pathname set using setJarTmpPath() is not writable by user gbasedbt or the user specified in the JDBC connection.

当使用 setJarTmpPath() 设置的路径名不能由用户 gbasedbt 或 JDBC 连接中指定的用户写入时，会发生此错误。

Make sure the pathname is readable and writable by any user.

确保路径名是任何用户都可读写的。

-79841 Invalid or Inconsistent Tuning Parameters for Connection Pool Datasource The GBase 8s JDBC Driver encountered an invalid Connection Pool Datasource property value. Make sure that application is using valid values to set Connection Pool Datasource properties. Refer to the GBase 8s JDBC Programmer's Guide for details of valid values.

GBase 8s JDBC Driver 遇到无效的连接池 Datasourcemproperty 值。确保应用程序使用有效值来设置 setmConnection 池数据源属性。有关有效值的详细信息，请参阅“GBase 8s JDBC 程序员指南”。

-79842 No UDR information was set in UDRMetaData.

Your application called the UDRManager.createUDRs() method without specifying any UDRs for the database server to register.

应用程序调用 UDRManager.createUDRs()方法，而没有为数据库服务器指定任何要注册的 UDR。

Specify UDRs for the database server to register by calling the UDRMetaData.setUDR() method before calling the UDRManager.createUDRs()method.

在调用 UDRManager.createUDRs()方法之前，通过调用 UDRMetaData.setUDR()方法为要注册的数据库服务器指定 UDR。

-79843 SQL name of the JAR file was not set in UDR/UDT metaData.

Your application called either the UDTManager.createUDT() method or the UDRManager.createUDRs() method without specifying an SQL name for the JAR file that contains the opaque types or UDRs for the database server to register.

应用程序调用了 UDTManager.createUDT() 方法或 UDRManager.createUDRs() 方法，而没有为包含不透明类型的 JAR 文件指定 SQL 名称，也没有为数据库服务器注册 UDR 指定 SQL 名称。

Specify an SQL name for a JAR file by calling the UDTMetaData.setJarFileSQLName() or UDRMetaData.setJarFileSQLName() method before you call the UDTManager.createUDT() or UDRManager.createUDRs() method.

在调用 UDTManager.createUDT()或 UDRManager.createUDRs()方法之前，通过调用UDTMetaData.setJarFileSQLName()或 UDRMetaData.setJarFileSQLName()方法为 JAR文件指定 SQL 名称。

-79844 Cannot create/remove UDT/UDR as no database is specified in the connection.

Your application created a connection without specifying a database.

应用程序创建了连接，但是没有指定数据库。

The following example establishes a connection and opens a database named "test":以下示例建立一个连接并打开数据库 "test"：url = "jdbc:gbasedbt-sqli:myhost:1533/test:" +"gbasedbtserver=myserver;user=rdtest;password=test";conn = DriverManager.getConnection(url);The following example establishes a connection with no database open:以下示例建立一个连接，但未打开数据库：url = "jdbc:gbasedbt-sqli:myhost:1533:" +"gbasedbtserver=myserver;user=rdtest;password=test";conn = DriverManager.getConnection(url);To resolve this problem, use the following SQL statements after the connection is established and before you call the createUDT() or createUDRs() method:要解决此问题，在建立连接之后，调用 createUDT() 或 createUDRs() 之前，使用以下SQL 语句：Statement stmt = conn.createStatement();stmt.executeUpdate("create database test ...");Alternatively, use the following code:或者，使用以下代码：stmt.executeUpdate("database test");-79845 JAR file on the client does not exist or cannot be read.

This error occurs for one of the following reasons:出现此错误的原因有以下几种：You failed to create a client JAR file.

您无法创建客户端 JAR 文件。

You specified an incorrect pathname for the client JAR file.

您为客户端JAR文件指定了错误的路径名。

The user running the JDBC application or the user specified in the connection does not have permission to open or read the client JAR file.

运行 JDBC 应用程序的用户或连接中指定的用户无权打开或读取客户端 JAR 文件。

-79846 Invalid JAR file name.

The client JAR file your application specified as the second parameter to UDTManager.createUDT() or UDRManager.createUDRs() must end with the .jar extension.

应用程序为 UDTManager.createUDT() 或 UDRManager.createUDRs()指定的第二参数-客户端 JAR 文件，必须具有 .jar 扩展名。

-79847 The javac or jar command failed.

The driver encountered compilation errors in one of the following cases:在以下某种情况下，驱动程序遇到编译错误：Compiling .class files into .jar files, using the jar command, in response to a createJar() command from a JDBC application使用 jar 命令将 .class 文件编译为 .jar 文件，以响应 JDBC 应用程序中的createJar()命令Compiling .java files into .class files and .jar files, using the javac and jar commands, in response to a call to the UDTManager.createUDTClass()method from a JDBC application使用 javac 和 jar 命令将 .java 文件编译为 .class 文件和 .jar 文件，以响应从 JDBC 应用程序调用 UDTManager.createUDTClass()方法-79848 Same UDT SQL name already exists in the system catalog.

Your application called UDTMetaData.setSQLName() and specified a name that is already in the database server.

应用程序调用了 UDTMetaData.setSQLName()，但指定了数据库服务器中已有的名称。

-79849 UDT SQL name was not set in UDTMetaData.

Your application failed to call UDTMetaData.setSQLName() to specify an SQL name for the opaque type.

您的应用程序无法调用 UDTMetaData.setSQLName() 来指定 opaque 类型的 SQL 名称。

-79850 UDT field count was not set in UDTMetaData.

Your application called UDTManager.createUDTClass() without first specifying the number of fields in the internal data structure that defines the opaque type.

您的应用程序调用了 UDTManager.createUDTClass()，但之前没有指定定义不透明类型的内部数据结构中的字段数。

Specify the number of fields by calling UDTMetaData.setFieldCount().

通过调用 UDTMetaData.setFieldCount() 指定字段数。

-79851 UDT length was not set in UDTMetaData.

Your application called UDTManager.createUDTClass() without first specifying a length for the opaque type.

您的应用程序调用 UDTManager.createUDTClass() 而不首先指定 opaque 类型的长度。

Specify the total length for the opaque type by calling UDTMetaData.setLength().通过调用 UDTMetaData.setLength() 指定 opaque 类型的总长度。

-79852 UDT field name or field type was not set in UDTMetaData.

Your application called UDTManager.createUDTClass() without first specifying a field name and data type for each field in the data structure that defines the opaque type.

您的应用程序调用 UDTManager.createUDTClass()，而不首先为定义 opaque 类型的数据结构中的每个字段指定字段名称和数据类型。

Specify each field name by calling UDTMetaData.setFieldName(). Specify a data type for each field by calling UDTMetaData.setFieldType().

通过调用 UDTMetaData.setFieldName()指定每个字段名称。通过调用UDTMetaData.setFieldType()为每个字段指定数据类型。

-79853 No class files to be put into the jar.

Your application called the createJar() method and passed a zero-length string for the classnames parameter.

您的应用程序调用了 createJar() 方法，并为 classnames 参数传递了一个零长度字符串。

The method signature is as follows:方法签名如下：createJar(UDTMetaData mdata, String[] classnames)-79854 UDT java class must implement java.sql.SQLData interface.

Your application called UDTManager.createUDT() to create an opaque type whose class definition does not implement the java.sql.SQLData interface.

UDTManager cannot create an opaque type from a class that does not implement this interface.

您的应用程序调用 UDTManager.createUDT() 来创建 opaque 类型，但其类定义没有实现java.sql.SQLData 接口。UDTManager 无法从未实现此接口的类创建 opaque 类型。

-79855 Specified UDT java class is not found.

Your application called the UDTManager.createUDT() method, but the driver could not find a class with the name you specified for the third parameter.

应用程序调用UDTManager.createUDT() 方法，但驱动程序找不到具有您为第三个参数指定的名称的类。

-79856 Specified UDT does not exists in the database.

Your application called UDTManager.removeUDT(String sqlname) to remove an opaque type named sqlname from the database, but no opaque type with that name exists in the database.

您的应用程序调用 UDTManager.removeUDT(String sqlname)，从数据库中删除名为sqlname 的 opaque 类型，但数据库中不存在具有该名称的 opaque 类型。

-79857 Invalid support function type.

This error occurs only if your application calls the UDTMetaData.setSupportUDR() method and passes an integer other than 0 through 7 for the type parameter.

仅当应用程序调用 UDTMetaData.setSupportUDR() 方法并为 type 参数传递 0 到 7之间的整数时，才会发生此错误。

Use the constants defined for the support UDR types. For more information,see the GBase 8s JDBC Driver Programmer's Guide.

使用为支持 UDR 类型定义的常量。有关更多信息，请参阅“GBase 8s JDBC 驱动程序程序员指南”。

-79858 The command to remove file on the client failed.

If UDTMetaData.keepJavaFile() is not called or is set to FALSE, the driver removes the generated .java file when the UDTManager.createUDTClass() method executes. This error results if the driver was unable to remove the .java file.

如果未调用 UDTMetaData.keepJavaFile()或将其设置为false，则在执行 UDTManager.createUDTClass()方法时，驱动程序将删除生成的 .java文件。如果驱动程序无法删除 .java文件，则会出现此错误。

-79859 Invalid UDT field number.

Your application called a UDTMetaData.setXXX() or UDTMetaData.getXXX() method and specified a field number that was less than 0 or greater than the value set through the UDTMetaData.setFieldCount() method.

您的应用程序调用了 UDTMetaData.setXXX() 或 UDTMetaData.getXXX() 方法，并指定了一个字段号，该字段号小于或大于 UDTMetaData.setFieldCount() 方法设置的值。

-79860 Ambiguous java type - cannot use Object/SQLData as method argument.

One or more parameters of the method to be registered as a UDR is of type java.lang.Object or java.sql.SQLData. These Java data types can be mapped to more than one GBase 8s data type, so the driver is unable to choose a type.

要注册为 UDR 的方法的一个或多个参数是 java.lang.Object 或 java.sql.SQLData类型。这些 Java 数据类型可以映射到多个 GBase 8s 数据类型，因此驱动程序无法选择一个类型。

Avoid using java.lang.Object or java.sql.SQLData as a method argument.

避免使用 java.lang.Object 或 java.sql.SQLData 作为方法参数。

-79861 Specified UDT field type has no Java type match.

Your application called UDTMetaData.setFieldType() and specified a data type that has no 100% match in Java. The following data types are in this category:您的应用程序调用了 UDTMetaData.setFieldType()，并指定了在 Java 中没有 100%匹配的数据类型。以下数据类型属于此类别：IfxTypes.IFX_TYPE_BYTE IfxTypes.IFX_TYPE_TEXT IfxTypes.IFX_TYPE_VARCHAR IfxTypes.IFX_TYPE_NVCHAR IfxTypes.IFX_TYPE_LVARCHAR Use IFX_TYPE_CHAR or IFX_TYPE_NCHAR instead; these data types map to java.lang.String.

使用 IFX_TYPE_CHAR 或 IFX_TYPE_NCHAR 代替；这些数据类型映射到 java.lang.String。

-79862 Invalid UDT field type.

Your application called UDTMetaData.setFieldType() and specified an unsupported data type for the opaque type.

应用程序调用了 UDTMetaData.setFieldType()，但为 opaque 类型指定了一个不支持的数据类型。

For supported data types, see the GBase 8s JDBC Driver Programmer's Guide.

有关支持的数据类型，请参阅《GBase 8s JDBC Driver 程序员指南》。

-79863 UDT field length was not set in UDTMetaData.

Your application specified a field of a character, datetime, or interval data type by calling UDTMetaData.setFieldType() but failed to specify a field length.

应用程序通过调用 UDTMetaData.setFieldType() 指定字符、日期时间或间隔数据类型的字段，但未能指定字段长度。

Call UDTMetaData.setFieldLength() to set a field length.

调用 UDTMetaData.setFieldLength() 设置字段长度。

-79864 Statement length exceeds the maximum.

Your application issued an SQL PREPARE, DECLARE, or EXECUTE IMMEDIATE statement that is longer than the database server can handle. The limit differs with different implementations but in most cases is up to 65,535 characters.

您的应用程序发出了比数据库服务器可以处理的更长的 SQL PREPARE、DECLARE 或EXECUTE IMMEDIATE 语句。语句的限制因不同的实现而不同，但在大多数情况下最多为 65,535 个字符。

Review the program logic to ensure that an error has not caused your application to present a string that is longer than intended. If the text has the intended length, revise the application to present fewer statements at a time.

检查程序逻辑以确保错误未导致应用程序显示超出预期的字符串。如果文本具有预期长度，则修改应用程序以一次显示较少的语句。

This error is the same as error -460 that the database server returns.

此错误与数据库服务器返回的错误 -460 相同。

-79865 'Statement' already closed.

This error occurs when an application attempts to call a method on a Statement object that has already been closed.

Make sure that the Statement object has not already been closed.

当应用程序尝试在已关闭的 Statement 对象上调用方法时，会发生此错误。

确保尚未关闭 Statement 对象。

-79868 ResultSet not open, operation not permitted.

This error occurs when an application attempts to call a method on a ResultSet object that has already been closed.The method can be called only on an open ResultSet object. Ensure that the ResultSet object in use has not already been implicitly or explicitly closed.

当应用程序尝试在已关闭的 ResultSet 对象上调用方法时，会发生此错误。此方法只能在打开的ResultSet 对象上调用。确保没有隐式或显式关闭正在使用的 ResultSet 对象。

-79877 Invalid parameter value for setting maximum field size.

This error occurs when an application attempts to set a maximum field size to a negative value. Ensure that application is passing a non-negative integer when calling the setMaxFieldSize() method on a Statement object.

当应用程序尝试将最大字段大小设置为负值时，会发生此错误。在 Statement 对象上调用 setMaxFieldSize() 方法时，确保应用程序传递非负整数。

-79878 ResultSet not open, operation 'next' not permitted. Verify that autocommit is OFF This message appears when an application attempts to fetch a row using a ResultSet that has been closed. Make sure that the ResultSet in use has not been closed, automatically or explicitly.

A ResultSet object is automatically closed when the Statement object that generated the ResultSet object is closed, re-executed, or used to retrieve the next result from a sequence of multiple results.

当应用程序尝试使用已关闭的 ResultSet 获取行时，将显示此消息。确保未关闭、自动或显式地关闭正在使用的 ResultSet。当生成 ResultSet 对象的语句对象关闭、重新执行或用于从多个结果序列检索下一个结果时，ResultSet 对象将自动关闭。

-79879 An unexpected exception was thrown. See next exception for details.

This message appears when the JDBC driver encounters an exception that is not anticipated in the normal course of events.Another exception chained to this exception contains further information regarding the unexpected error condition that occurred.

当 JDBC 驱动程序遇到在正常事件过程中未预料到的异常时，将显示此消息。链接到此异常的另一个异常，它包含有关发生的意外错误情况的更多信息。

-79880 Unable to set JDK Version for the Driver.

This message appears when the JDBC driver fails to determine which version of JDK is being used to run the java application. JDBC driver attempts to read"java.version" system property to find out which JDK version is being used.

Ensure that the JDBC driver JAR has necessary privileges to access the"java.version" system property.

当 JDBC 驱动程序无法确定正在使用哪个版本的 JDK 来运行 Java 应用程序时，会出现此消息。

JDBC 驱动程序尝试读取 “java.version” 系统属性以找出正在使用的JDK 版本。确保 JDBC 驱动程序 JAR 具有访问 “java.version” 系统属性的必要权限。

-79881 Already in local transaction, so cannot start XA transaction.

This error message appears when a JDBC application attempts to start an XA transaction for a connection that is already associated with a local transaction. XAResource does not support nested transactions. Before attempting to start an XA transaction, the application needs to ensure that the connection is not associated with any other transaction.

当 JDBC 应用程序试图为已经与本地事务关联的连接启动 XA 事务时，会出现此错误消息。

XAResource 不支持嵌套事务。在尝试启动 XA 事务之前，应用程序需要确保连接与任何其他事务无关。

-79882 Method not supported with this server.

This error message appears when a JDBC client attempts to use functionality that is not supported by the version of server the JDBC client is connected to.

This functionality is available in later versions of the server.

You can migrate to the latest server version to use this functionality当 JDBC 客户机试图使用连接到的服务器版本不支持的功能时，会出现此错误消息。

此功能可在服务器的后期版本中使用。您可以迁移到最新的服务器版本以使用此功能。

-79883 Class that implements IfmxPAM interface could not be located or loaded.

This error message appears when the JDBC driver fails to load the class specified by the IFX_PAM_CLASS connection property.In order to use the PAM authentication mechanism, the JDBC application specifies the name of a class as a connection property. The JDBC driver failed to load the specified class.

Ensure that the specified class is in the CLASSPATH.

当 JDBC 驱动程序无法加载 IFX_PAM_class 连接属性指定的类时，将出现此错误消息，为了使用 PAM 身份验证机制，JDBC 应用程序将类名指定为连接属性。JDBC 驱动程序未能加载指定的类。确保指定的类在 CLASSPATH 中。

-79884 Class must implement com.gbasedbt.jdbc.IfmxPAM interface for PAM functionality.

This message appears when the class whose name has been set as a value of the IFX_PAM_CLASS property does not implement the com.gbasedbt.jdbc.IfmxPAM interface.In order to use the PAM authentication mechanism, the JDBC application needs to set the IFX_PAM_CLASS connection property.The class specified as value of a IFX_PAM_CLASS connection property should Implement the com.gbasedbt.jdbc.IfmxPAM interface.

当名称设置为 IFX_PAM_CLASS 属性值的类没有实现 com.Gbasedbt.jdbc.IfmxPAM 接口时，就会出现此消息。为了使用 PAM 身份验证机制，JDBC 应用程序需要设置 IFX_PAM_CLASS连接属性。指定为 IFX_PAM_CLASS 连接属性值的类应该实现 com.sulix.jdbc.IfmxPAM 接口。

-79885 PAM authorization has failed.

This message appears when PAM authorization of a JDBC client fails.

Ensure that your application is responding with a correct response string to the challenge message received from a PAM-enabled server.

当 JDBC 客户端的 PAM 授权失败时，就会出现此消息。确保应用程序使用正确的响应字符串响应从启用 PAM 的服务器接收的质询消息。

-79886 PAM Response Message Size exceeds maximum size allowed.

Length of the PAM response string set by your application exceeds the maximum allowed size. The PAM standard defines the maximum size of a PAM message to be 512 bytes (IfxPAMChallenge.PAM_MAX_MESSAGE_SIZE).

Ensure that a correct PAM response string is supplied by your application.

应用程序设置的 PAM 响应字符串的长度超过了允许的最大大小。PAM 标准将PAM 消息的最大大小定义为 512 字节（IfxPAMChallenge.PAM_MAX_MESSAGE_SIZE）。

确保应用程序提供了正确的 PAM 响应字符串。

-79887 Parameter name not found.

A parameter name is not found in the argument names of the specified stored procedure. Either one of the parameter names is not valid or the stored procedure name is incorrect.

在指定的存储过程的参数名称中找不到参数名称。其中一个参数名称无效或存储过程名称不正确。

Correct the parameter or procedure name and run the procedure again.

更正参数或过程名称并再次运行该过程。

-79888 Parameters are specified by both name and ordinal position for the same CallableStatement object.

A CallableStatement object must be consistent in the way it specifies parameters; that is, it must only use methods that take parameter names(String objects), or it must use only methods that take parameter ordinal positions (integers). A CallableStatement object that mixes the two types of references throws an SQLException object.

CallableStatement 对象必须在指定参数的方式上保持一致;也就是说，它只能使用带有参数名称（String 对象）的方法，或者它必须只使用带有参数 ordina 位置（整数）的方法。混合两种类型的引用的 CallableStatement 对象将抛出 SQLException 对象。

Specify parameters either by name or by ordinal for a particular CallableStatement object.

为特定的 CallableStatement 对象按名称或按顺序指定参数。

-79889 You cannot set a savepoint, rollback to a savepoint, or release a savepoint when the transaction is in autocommit mode.

The JDBC application attempted to create or reference a savepoint while the autocommit transaction mode was true for the connection. Before attempting to set a savepoint, to rollback to a savepoint, or to release a savepoint,the application needs to ensure that autocommit is false. By default,autocommit is true in JDBC for connections to any IDS database that supports transaction logging.

当连接的自动提交事务模式为真时，JDBC 应用程序尝试创建或引用保存点。在尝试设置保存点，回滚到保存点或释放保存点之前，应用程序需要确保自动提交为 false。默认情况下，JDBC 中的 autocommit 为 true，用于连接到支持事务日志记录的任何 IDS 数据库。

-79890 You cannot set a savepoint, rollback to a savepoint, or release a savepoint within an XA transaction.

The JDBC application attempted to create or reference a savepoint within an XA transaction. Savepoints are not supported in XA transactions.

JDBC 应用程序尝试在 XA 事务中创建或引用保存点。XA 事务不支持保存点。

-79891 The identifier declared for the named savepoint cannot be null.

The JDBC application attempted to set a savepoint by passing NULL as the the savepoint name. The savepoint name cannot be NULL for the connection.

setSavepoint(string) method. Use instead the setSavepoint() method if you want to create an unnamed savepoint.

JDBC 应用程序尝试通过传递 NULL 作为保存点名称来设置保存点。连接的保存点名称不能为NULL。setSavepoint(string)方法。如果要创建未命名的保存点，请使用 setSavepoint()方法。

-79892 The savepoint cannot be null when rolling back to a savepoint or releasing a savepoint.

The JDBC application attempted to rollback to a savepoint or to release a savepoint by passing a NULL savepoint object. Only savepoint objects that were created by the setSavepoint() methods can be passed to methods that rollback to a savepoint or that release a savepoint.

JDBC 应用程序试图回滚到 savepoint，或者通过传递空 savepoint 对象来释放 savepoint。

只有由 setSavepoint()方法创建的 savepoint 对象才能传递给回滚到 savepoint 或发布 savepoint 的方法。

-79893 The savepoint is not valid in the current connection.

The JDBC application attempted to rollback to a savepoint (or to release a savepoint) by passing an invalid savepoint object. Before the application can rollback to a savepoint or release a savepoint, that savepoint must first be created in the current connection.

JDBC 应用程序试图通过传递无效的 savepoint 对象回滚到 savepoint(或释放 savepoint)。

在应用程序回滚到 savepoint 或发布 savepoint 之前，必须首先在当前连接中创建该 savepoint。

-79894 You cannot return the numeric identifier of a named savepoint.

The JDBC application attempted to call getSavepointId() on a named savepoint. If the savepoint was declared using the setSavepoint(string)method, then getSavepointId() is not a valid method, and it returns this exception. Call instead the getSavepointName() method to return the name of a savepoint.

JDBC 应用程序试图在命名的 savepoint 上调用 getSavepointId()。如果保存点是使用setSavepoint(String) 方法声明的，则 getSavepointId()不是有效方法，它将返回此异常。相反，调用 getSavepointName()方法来返回 savepoint 的名称。

-79895 You cannot return the name of an unnamed savepoint.

The JDBC application attempted to call getSavepointName() on an unnamed savepoint. If the savepoint was declared using the setSavepoint()method, then getSavepointName() is not a valid method, and it returns this exception. Call instead the getSavepointId() method to return the numeric identifier of an unnamed savepoint.

JDBC 应用程序试图在未命名的 savepoint 上调用 getSavepointName()。如果保存点是使用 setSavepoint() 方法声明的，则 getSavepointName()不是有效方法，它将返回此异常。相反，调用 getSavepointId() 方法来返回未命名的 savepoint 的数字标识符。

-79896 Incorrect connection array index in the connection pool.

The connection array index is not a valid index.

This is caused when the application tries to remove a connection from the connection pool and the array index is either negative or more than the maximum connection size for the pool.

连接数组索引是一个无效索引。当应用程序尝试从连接池中删除连接并且数组索引为负数或大于池的最大连接大小时，会导致此问题。

This problem is probably caused by the JVM running out of resources.

Check for any relevant operating system messages.

此问题可能是由 JVM 耗尽资源引起的。检查是否有相关的操作系统消息。

-79999 Message text will be provided in later release.

An error message with detailed message text will be provided in future releases.

将在未来版本中提供带有详细消息文本的错误消息。

21511 Cannot request more than 1 page for online index build.

The online index build has requested more than 1 page during parallel build.

在线索引构建在并行构建期间请求超过 1 页。

-21511 Cannot request more than 1 page for online index build.

The online index build has requested more than 1 page during parallel build.

在线索引构建在并行构建期间请求超过 1 页。

21512 Exclusive access required to pre-image buffer.

Exclusive access required to pre-image buffer. Either a buffer was released with BF_MODIFY flag, or it was shared or waited for by some other thread.

预映像缓冲区需要独占访问权限。使用 BF_MODIFY 标志释放缓冲区，或者由其他某个线程共享或等待它。

-21512 Exclusive access required to pre-image buffer.

Exclusive access required to pre-image buffer. Either a buffer was released with BF_MODIFY flag, or it was shared or waited for by some other thread.

预映像缓冲区需要独占访问权限。使用 BF_MODIFY 标志释放缓冲区，或者由其他某个线程共享或等待它。

21513 Error in online index operation Some internal error occurred during the online index operation.

在线索引操作期间发生了一些内部错误。

-21513 Error in online index operation Some internal error occurred during the online index operation.

在线索引操作期间发生了一些内部错误。

21514 Error saving keyp after online index build There was some error when saving new keyp after online index build.

在线索引构建后保存新 keyp 时出现错误。

-21514 Error saving keyp after online index build There was some error when saving new keyp after online index build.

在线索引构建后保存新 keyp 时出现错误。

21515 Cannot perform online index build for attached indices Online index build is allowed only for detached and semi-detached indices.

It is not supported for attached index builds.

只有分离和半分离的索引允许在线索引构建。附加的索引构建不支持。

-21515 Cannot perform online index build for attached indices Online index build is allowed only for detached and semi-detached indices.

It is not supported for attached index builds.

只有分离和半分离的索引允许在线索引构建。附加的索引构建不支持。

21516 Partially read row This is an internally set error on reading rows for parallel index build.

It is ignored if the parallel build is being performed for an online index这是为并行索引生成读取行的内部设置错误。如果要为联机索引执行并行生成，则忽略它。

-21516 Partially read row This is an internally set error on reading rows for parallel index build.

It is ignored if the parallel build is being performed for an online index这是为并行索引生成读取行的内部设置错误。如果要为联机索引执行并行生成，则忽略它。

21517 Error allocating bufQ for preimage or updator log Error occurred when allocating buffer queue for preimage or updator logging.

为预映像或更新程序日志分配缓冲区队列时发生错误。

-21517 Error allocating bufQ for preimage or updator log Error occurred when allocating buffer queue for preimage or updator logging.

为预映像或更新程序日志分配缓冲区队列时发生错误。

21518 Error occurred while starting a thread to process preimage or updator log.

Error occurred while starting a thread for processing preimage or updator log.

启动用于处理预映像或更新程序日志的线程时发生错误。

-21518 Error occurred while starting a thread to process preimage or updator log.

Error occurred while starting a thread for processing preimage or updator log.

启动用于处理预映像或更新程序日志的线程时发生错误。

21519 No preimage exists No preimage exists when one was believed to be there.

没有预映象存在，误认为有一个预映象存在。

-21519 No preimage exists No preimage exists when one was believed to be there.

没有预映象存在，误认为有一个预映象存在。

21520 Bad temp partition physaddr Bad temp partition physaddr was obtained for preimage or updator log partition.

为 preimage 或 updator 日志分区获取了错误的临时分区 physaddr。

-21520 Bad temp partition physaddr Bad temp partition physaddr was obtained for preimage or updator log partition.

为 preimage 或 updator 日志分区获取了错误的临时分区 physaddr。

21521 More than 1 online index operation on the same table More than 1 online index operation is not allowed on the same table.

同一个表上只能有一个联机索引操作。

-21521 More than 1 online index operation on the same table More than 1 online index operation is not allowed on the same table.

同一个表上只能有一个联机索引操作。

21522 No online index build possible No online index build is possible in the requested scenario.

The index build requires reading rows one by one, or online index builds are not allowed in this IDS edition.

在请求的方案中无法进行在线索引构建。索引构建需要逐行读取，或者在此 IDS 版本中不允许联机索引构建。

-21522 No online index build possible No online index build is possible in the requested scenario.

The index build requires reading rows one by one, or online index builds are not allowed in this IDS edition.

在请求的方案中无法进行在线索引构建。索引构建需要逐行读取，或者在此 IDS 版本中不允许联机索引构建。

21523 Cannot proceed with a dirty/modified table data dictionary entry.

DML operations are susceptible to this error when they are referencing an older copy of the table's data dictionary information.

Most likely, the database server just completed a 'CREATE/DROP INDEX ... 'operation on the table referred to by the DML operation.

DML 操作在引用表的数据字典信息的旧副本时容易发生此错误。最有可能的是，数据库服务器刚刚完成了 DML 操作所引用的表上的 “CREATE/DROP INDEX...” 操作。

This error is accompanied by SQL Error -710.

此错误伴随 SQL 错误 -710。

-21523 Cannot proceed with a dirty/modified table data dictionary entry.

DML operations are susceptible to this error when they are referencing an older copy of the table's data dictionary information.

Most likely, the database server just completed a 'CREATE/DROP INDEX ... 'operation on the table referred to by the DML operation.

This error is accompanied by SQL Error -710.

此错误伴随 SQL 错误 -710。

21524 Cannot create a temporary operating system file to use in a sort A sort was being performed that did not use a dbspace partition to store overflow data. Overflow data is written to a temporary operating system file. However, the database server could not create a temporary operating system file for this sort. Consider setting the PSORT_DBTEMP environment variable to a secure directory with a minimum of 200 MB of free space.

If PSORT_DBTEMP is not set then the database server stores overflow data in the /tmp or $GBS_HOME/tmp directory.

正在执行的排序不使用 dbspace 分区来存储溢出数据。溢出数据将写入临时操作系统文件。

但是，数据库服务器无法为此类型创建临时操作系统文件。考虑将 PSORT_DBTEMP 环境变量设置为具有至少 200 MB 可用空间的安全目录。如果未设置 PSORT_DBTEMP，则数据库服务器将溢出数据存储在 /tmp 或 $GBS_HOME/tmp 目录中。

-21524 Cannot create a temporary operating system file to use in a sort A sort was being performed that did not use a dbspace partition to store overflow data. Overflow data is written to a temporary operating system file. However, the database server could not create a temporary operating system file for this sort. Consider setting the PSORT_DBTEMP environment variable to a secure directory with a minimum of 200 MB of free space.

If PSORT_DBTEMP is not set then the database server stores overflow data in the /tmp or $GBS_HOME/tmp directory.

正在执行的排序不使用 dbspace 分区来存储溢出数据。溢出数据将写入临时操作系统文件。

21525 Cannot write to a temporary operating system file during a sort A sort was being performed that did not use a dbspace partition to store overflow data. Overflow data is written to a temporary operating system file. However, the database server could not write to this temporary operating system file, most likely because the file directory is out of space. The location of this file is in the path specified by the PSORT_DBTEMP environment variable. If PSORT_DBTEMP is not set then the database server puts these temporary files in the /tmp or$GBS_HOME/tmp directory.

正在执行不使用 dbspace 分区存储溢出数据的排序。溢出数据写入临时操作系统文件。但是，数据库服务器无法写入此临时操作系统文件，这很可能是因为文件目录空间不足。此文件的位置位于 PSORT_DBTEMP 环境变量指定的路径中。如果未设置 PSORT_DBTEMP，则数据库服务器将这些临时文件放在 /tmp 或 $GBS_HOME/tmp 目录中。

-21525 Cannot write to a temporary operating system file during a sort A sort was being performed that did not use a dbspace partition to store overflow data. Overflow data is written to a temporary operating system file. However, the database server could not write to this temporary operating system file, most likely because the file directory is out of space. The location of this file is in the path specified by the PSORT_DBTEMP environment variable. If PSORT_DBTEMP is not set then the database server puts these temporary files in the /tmp or$GBS_HOME/tmp directory.

21526 This log cannot be dropped, because the next log has an open transaction.

This error occurs when a log is requested to be dropped, but cannot be because the next log contains the beginning of an open transaction. This log is required to roll back that transaction, explicitly or implicitly during long transaction abort. Also, the remaining log space might not be sufficient to hold the rollback log records.

当请求删除日志时会发生此错误，但不能这样做，因为下一个日志包含打开事务的开始。

在长事务中止期间，要显式或隐式地回滚该事务，需要此日志。另外，剩余的日志空间可能不足以保存回滚日志记录。

-21526 This log cannot be dropped, because the next log has an open transaction.

当请求删除日志时会发生此错误，但不能这样做，因为下一个日志包含打开事务的开始。

在长事务中止期间，要显式或隐式地回滚该事务，需要此日志。另外，剩余的日志空间可能不足以保存回滚日志记录。

21527 The partition could not be created because the dbspace is currently unavailable.

The partition could not be created in the specified dbspace because that dbspace is either disabled, in the process of being restored from a backup, or in the process of being updated as part of fast recovery.

无法在指定的 dbspace 中创建分区，因为该 dbspace 在从备份还原的过程中，或者在作为快速恢复的一部分进行更新的过程中是禁用的。

Enable the dbspace or wait for it to complete its recovery, and then run the command to create the partition again.

启用 dbspace 或等待它完成其恢复，然后运行命令再次创建分区。

-21527 The partition could not be created because the dbspace is currently unavailable.

无法在指定的 dbspace 中创建分区，因为该 dbspace 在从备份还原的过程中，或者在作为快速恢复的一部分进行更新的过程中是禁用的。

Enable the dbspace or wait for it to complete its recovery, and then run the command to create the partition again.

启用 dbspace 或等待它完成其恢复，然后运行命令再次创建分区。

-21542 GBase Global Security Kit (GSKit) library call failed.

A call into the GBase Global Security Kit (GSKit) library failed in an unexpected manner.

对 GBase Global Security Kit (GSKit) 库的调用意外失败。

-21543 Encryption key not found.

An encrypted database server instance was unable to find the encryption key necessary to perform encryption or decryption.

加密的数据库服务器实例无法找到执行加密或解密所需的加密密钥。

-21544 Attempt to encrypt data that is already encrypted.

An encrypted database server instance unexpectedly encountered data that appears to be already encrypted while attempting to encrypt data.

加密的数据库服务器实例意外地遇到了在尝试加密数据时似乎已加密的数据。

-21545 Attempt to decrypt data that is not encrypted.

An encrypted database server instance unexpectedly encountered data that appears to be already unencrypted while attempting to decrypt data.

加密的数据库服务器实例意外地遇到了在尝试解密数据时似乎未加密的数据。

-21546 Error registering encryption key.

An encrypted database server instance encountered an error registering the encryption key with the encryption/decryption subsystem. This may indicate an illegal or corrupt encryption key. The associated data cannot be encrypted or decrypted.

加密的数据库服务器实例遇到向加密/解密子系统注册加密密钥的错误。这可能表示非法或损坏的加密密钥。相关数据无法加密或解密。

-21547 Encryption of data failed.

An encrypted database server instance encountered an error encrypting data.

加密的数据库服务器实例遇到加密数据的错误。

-21548 Decryption of data failed.

An encrypted database server instance encountered an error decrypting data.

加密的数据库服务器实例遇到解密数据的错误。

-21549 Unable to initialize encryption cipher.

This error is raised by an encrypted database server instance. The server was unable to initialize the encryption cipher due to an internal resource constraint or because the encryption cipher is unsupported.

加密的数据库服务器实例引发此错误。由于内部资源限制或加密密码不受支持，服务器无法初始化加密密码。

-21550 Error creating or accessing the Encryption Key Database.

An encrypted database server instance saves encryption keys in an Encryption Key Database. If this error occurs when initializing a new encrypted server instance (-i and -e options to oninit) or creating an encrypted instance from an archive restore ("-E on" option to the restore),the server encountered an error creating the Encryption Key Database. If this error occurs when booting an existing server instance, the server encountered an error accessing the Encryption Key Database.

Refer to the message log for additional information.

加密的数据库服务器实例将加密密钥保存在加密密钥数据库中。如果在初始化新的加密服务器实例（-i 和 -e 选项为 oninit）或从存档还原创建加密实例（还原的“-E on”选项）时发生此错误，则服务器在创建加密时遇到错误密钥数据库。如果在引导现有服务器实例时发生此错误，则服务器在访问加密密钥数据库时遇到错误。有关其他信息，请参阅消息日志。

-26014 Alter fragment on typed table is not allowed.

Alter fragment on table/index is not supported for typed table.

类型表不支持表/索引上的更改分片。

-26015 All fragments of the table or index need to be of same pagesize.

This error can occur on creating a fragmented table or index across dbspaces of different pagesize. It can also occur while performing an ALTER FRAGMENT on a table or index and the new dbspaces are of different pagesize than the dbspaces in the existing fragmentation strategy. For an interval fragmented table or index, this error can occur if the pagesize of the dbspaces in the STORE IN clause is different from the pagesize of initial fragment dbspaces.

在跨不同页面大小的 dbspace 创建碎片表或索引时，可能会发生此错误。在对表或索引执行 ALTER FRAGMENT 时也会发生这种情况，并且新 dbspace 的页面大小与现有分片策略中的 dbspace 不同。对于间隔分片表或索引，如果 STORE IN 子句中的 dbspace 的 pagesize与初始分片 dbspace 的 pagesize 不同，则会发生此错误。

-26016 Illegal leading byte 0x20 in Index name (index_name).

In some situations, such as when a constraint is defined, the database server creates indexes internally. These indexes, by convention, always have a leading ASCII blank (hex 20) as the first byte of their name. To avoid a conflict, user-created indexes cannot have an ASCII blank (hex 20)as the first byte of their name. Also, there can be no reference to indexes with a leading blank in any user-issued statements. This rule is enforced regardless of the locale. This rule is also enforced regardless of the use of the DELIMIDENT environment variable.

在某些情况下，例如定义约束时，数据库服务器会在内部创建索引。按照惯例，这些索引始终具有前导 ASCII 空白（十六进制 20）作为其名称的第一个字节。为避免冲突，用户创建的索引不能将 ASCII 空格（十六进制 20）作为其名称的第一个字节。此外，在任何用户发出的语句中都不能引用带有前导空格的索引。无论语言环境如何，都会强制执行此规则。无论是否使用 DELIMIDENT 环境变量，都会强制执行此规则。

-26017 External indices are not supported with non-default pagesizes.

Virtual-Index Interface (VII) does not support creating index on non-default pagesize dbspaces. This error can occur while creating a R-Tree index (which is part of the server and internally implemented using VII), or when creating any index which was implemented using VII.

虚拟索引接口（VII）不支持在非默认的 pagesize dbspace 上创建索引。创建 R-Tree索引（它是服务器的一部分并在内部使用 VII 实现）或创建使用 VII 实现的任何索引时，可能会发生此错误。

32000 The rollback was caused by an unspecified reason.

This error is same as XA_RBROLLBACK in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_RBROLLBACK 相同。有关更多信息，请参阅“分布式事务处理：XA 规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：In the xa_commit context, the Resource Manager rolled back the transaction branch for an unspecified reason. The Resource Manager did not commit the work done on behalf of the transaction branch. Upon return, the Resource Manager has rolled back the branch's work and has released all held resources.

This value can be returned only if TMONEPHASE is set in flags.

在 xa_commit 上下文中，资源管理器因未指定的原因回滚事务分支。资源管理器未提交代表事务分支完成的工作。返回后，资源管理器已回滚分支的工作并已释放所有持有的资源。仅当在标志中设置了 TMONEPHASE 时，才能返回此值。

In the xa_end context, the Resource Manager marked the transaction branch rollback-only for an unspecified reason. The Resource Manager has dissociated the transaction branch from the thread of control and has marked rollback-only the work performed on behalf of *xid.

在 xa_end 上下文中，资源管理器仅针对未指定的原因标记了事务分支回滚。资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表 *xid 执行的工作。

In the xa_prepare context, the Resource Manager rolled back the transaction branch for an unspecified reason. The Resource Manager did not prepare to commit the work done on behalf of the transaction branch. Upon return, the Resource Manager has rolled back the branch's work and has released all held resources.

在 xa_prepare 上下文中，资源管理器因未指定的原因回滚事务分支。资源管理器没有准备代表事务分支提交完成的工作。返回后，资源管理器已回滚分支的工作并已释放所有持有的资源。

In the xa_rollback context, the Resource Manager rolled back the transaction branch for an unspecified reason. The Resource Manager has rolled back the transaction branch's work and has released all held resources. These values are typically returned when the branch was already marked rollback-only.

在 xa_rollback 上下文中，资源管理器因未指定的原因回滚事务分支。资源管理器已回滚事务分支的工作并已释放所有持有的资源。当分支已标记为仅回滚时，通常会返回这些值。

In the xa_start context, the Resource Manager marked the transaction branch rollback-only for an unspecified reason. The Resource Manager has not associated the transaction branch with the thread of control and has marked *xid rollback-only.

在 xa_start 上下文中，资源管理器标记了事务分支回滚 - 仅用于未指定的原因。

资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid rollback-only。

Also refer to the Resource Manager guide for more details.

也请参阅资源管理器指南以获取更多的信息。

-32000 The rollback was caused by an unspecified reason.

This error is same as XA_RBROLLBACK in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_RBROLLBACK 相同。有关更多信息，请参阅“分布式事务处理：XA 规范”。

This value can be returned only if TMONEPHASE is set in flags.

在 xa_start 上下文中，资源管理器标记了事务分支回滚 - 仅用于未指定的原因。

资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid rollback-only。

Also refer to the Resource Manager guide for more details.

也请参阅资源管理器指南以获取更多的信息。

32001 The rollback was caused by a communication failure.

This error is same as XA_RBCOMMFAIL in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPENXA 规范标准中的 XA_RBCOMMFAIL 相同。有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：A communication failure occurred within the Resource Manager.

资源管理器内部发生通信失败。

In the xa_commit context, the Resource Manager did not commit the work done on behalf of the transaction branch. Upon return, the Resource Manager has rolled back the branch's work and has released all held resources. This value can be returned only if TMONEPHASE is set in flags.

在 xa_commit 上下文中，资源管理器未提交代表事务分支完成的工作。返回后，资源管理器已回滚分支的工作并已释放所有持有的资源。仅当在标志中设置了 TMONEPHASE 时，才能返回此值。

In the xa_end context, the Resource Manager has dissociated the transaction branch from the thread of control and has marked rollback-only the work performed on behalf of *xid.

在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表 *xid 执行的工作。

In the xa_prepare context, the Resource Manager did not prepare to commit the work done on behalf of the transaction branch. Upon return, the Resource Manager has rolled back the branch's work and has released all held resources.

在 xa_prepare 上下文中，资源管理器没有准备提交代表事务分支完成的工作。

返回时，资源管理器已回滚了分支的工作，并释放了所有持有的资源。

In the xa_rollback context, the Resource Manager has rolled back the transaction branch's work and has released all held resources. These values are typically returned when the branch was already marked rollback-only.

在 xa_rollback 上下文中，资源管理器回滚了事务分支的工作，并释放了所有持有的资源。当分支已经标记为 ROLLBACK 时，通常会返回这些值。

In the xa_start context, the Resource Manager has not associated the transaction branch with the thread of control and has marked *xid rollback-only.

在 xa_start 上下文中，资源管理器没有将事务分支与控制线程关联，而是标记为 *xid rollback-only。

Also refer to the Resource Manager guide for more details.

可参阅资源管理器指南以获取更多的信息。

-32001 The rollback was caused by a communication failure.

This error is same as XA_RBCOMMFAIL in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPENXA 规范标准中的 XA_RBCOMMFAIL 相同。有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：A communication failure occurred within the Resource Manager.

资源管理器内部发生通信失败。

In the xa_end context, the Resource Manager has dissociated the transaction branch from the thread of control and has marked rollback-only the work performed on behalf of *xid.

在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表 *xid 执行的工作。

在 xa_prepare 上下文中，Resource Manager 没有准备提交代表事务分支完成的工作。

返回时，资源管理器已回滚了分支的工作，并释放了所有持有的资源。

在 xa_rollback 上下文中，资源管理器回滚了事务分支的工作，并释放了所有持有的资源。

当分支已经标记为 ROLLBACK 时，通常会返回这些值。

In the xa_start context, the Resource Manager has not associated the transaction branch with the thread of control and has marked *xid rollback-only.

在 xa_start 上下文中，资源管理器没有将事务分支与控制线程关联，而是标记为 *xid rollback-only。

Also refer to the Resource Manager guide for more details.

可参阅资源管理器指南以获取更多的信息。

32002 The rollback was caused by a deadlock was detected.

This error is same as XA_RBDEADLOCK in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPENXA 规范中的 XA_RBDEADLOCK 相同。有关更多信息，请参阅“分布式事务处理：XA 规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：The Resource Manager detected a deadlock.

资源管理器检测到一个死锁。

In the xa_end context, the Resource Manager has dissociated the transaction branch from the thread of control and has marked rollback-only the work performed on behalf of *xid.

在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表 *xid 执行的工作。

在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。

返回后，资源管理器已回滚分支的工作并已释放所有持有的资源。

在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。

当分支已标记为仅回滚时，通常会返回这些值。

In the xa_start context, the Resource Manager has not associated the transaction branch with the thread of control and has marked *xid rollback-only.

在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid rollback-only。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅资源管理器指南。

-32002 The rollback was caused by a deadlock was detected.

This error is same as XA_RBDEADLOCK in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPENXA 规范中的 XA_RBDEADLOCK 相同。有关更多信息，请参阅“分布式事务处理：XA 规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：The Resource Manager detected a deadlock.

资源管理器检测到一个死锁。

In the xa_end context, the Resource Manager has dissociated the transaction branch from the thread of control and has marked rollback-only the work performed on behalf of *xid.

在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表 *xid 执行的工作。

在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。

返回后，资源管理器已回滚分支的工作并已释放所有持有的资源。

在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。

当分支已标记为仅回滚时，通常会返回这些值。

In the xa_start context, the Resource Manager has not associated the transaction branch with the thread of control and has marked *xid rollback-only.

在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid rollback-only。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅资源管理器指南。

32003 A condition that violates the integrity of the resources was detected.

This error is same as XA_RBINTEGRITY in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_RBINTEGRITY 相同。有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：The Resource Manager detected a violation of the integrity of its resources.

资源管理器检测到违反其资源的完整性。

In the xa_end context, the Resource Manager has dissociated the transaction branch from the thread of control and has marked rollback-only the work performed on behalf of *xid.

在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表 *xid 执行的工作。

在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。返回后，资源管理器已回滚分支的工作并已释放所有持有的资源。

在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。

当分支已标记为仅回滚时，通常会返回这些值。

In the xa_start context, the Resource Manager has not associated the transaction branch with the thread of control and has marked *xid rollback-only.

在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid rollback-only。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅资源管理器指南。

-32003 A condition that violates the integrity of the resources was detected.

This error is same as XA_RBINTEGRITY in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_RBINTEGRITY 相同。有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：The Resource Manager detected a violation of the integrity of its resources.

资源管理器检测到违反其资源的完整性。

In the xa_end context, the Resource Manager has dissociated the transaction branch from the thread of control and has marked rollback-only the work performed on behalf of *xid.

在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表 *xid 执行的工作。

在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。返回后，资源管理器已回滚分支的工作并已释放所有持有的资源。

在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。

当分支已标记为仅回滚时，通常会返回这些值。

In the xa_start context, the Resource Manager has not associated the transaction branch with the thread of control and has marked *xid rollback-only.

在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid rollback-only。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅资源管理器指南。

32004 The Resource Manager rolled back the transaction branch for a reason not on the XA rollback errors.

This error is same as XA_RBOTHER in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPENXA 规范标准中的 XA_RBOTHER 相同。有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：In the xa_commit context, the Resource Manager rolled back the transaction branch for a reason not on the XA rollback errors. The Resource Manager did not commit the work done on behalf of the transaction branch. Upon return,the Resource Manager has rolled back the branch's work and has released all held resources. This value can be returned only if TMONEPHASE is set in flags.

在 xa_commit 上下文中，资源管理器回滚事务分支的原因不是 XA 回滚错误。资源管理器未提交代表事务分支完成的工作。返回后，资源管理器已回滚分支的工作并释放所有持有的资源。仅当在标志中设置了 TMONEPHASE 时，才能返回此值。

In the xa_end context, the Resource Manager marked the transaction branch rollback-only for a reason not on the XA rollback errors. The Resource Manager has dissociated the transaction branch from the thread of control and has marked rollback-only the work performed on behalf of *xid.

在 xa_end 上下文中，资源管理器将事务分支标记为仅回滚，原因不在于 XA 回滚错误。

资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表 *xid 执行的工作。

In the xa_prepare context, the Resource Manager rolled back the transaction branch for a reason not on the XA rollback errors. The Resource Manager did not prepare to commit the work done on behalf of the transaction branch. Upon return, the Resource Manager has rolled back the branch's work and has released all held resources.

在 xa_prepare 上下文中，资源管理器回滚事务分支的原因不是 XA 回滚错误。资源管理器没有准备代表事务分支提交完成的工作。返回后，资源管理器已回滚分支的工作并已释放所有持有的资源。

In the xa_rollback context, the Resource Manager rolled back the transaction branch for a reason not on the XA rollback errors. The Resource Manager has rolled back the transaction branch's work and has released all held resources.

These values are typically returned when the branch was already marked rollback-only.

在 xa_rollback 上下文中，资源管理器回滚事务分支的原因不是 XA 回滚错误。资源管理器已回滚事务分支的工作并已释放所有持有的资源。当分支已标记为仅回滚时，通常会返回这些值。

In the xa_start context, the Resource Manager marked the transaction branch rollback-only for a reason not on the XA rollback errors. The Resource Manager has not associated the transaction branch with the thread of control and has marked *xid rollback-only.

在 xa_start 上下文中，资源管理器将事务分支标记为仅回滚，原因不在于 XA 回滚错误。

资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid rollback-only。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

-32004 The Resource Manager rolled back the transaction branch for a reason not on the XA rollback errors.

This error is same as XA_RBOTHER in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPENXA 规范标准中的 XA_RBOTHER 相同。有关更多信息，请参阅“分布式事务处理：XA规范”。

在 xa_end 上下文中，资源管理器将事务分支标记为仅回滚，原因不在于 XA 回滚错误。

资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表 *xid 执行的工作。

These values are typically returned when the branch was already marked rollback-only.

资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid rollback-only。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

32005 A protocol error occurred in the Resource Manager.

This error is same as XA_RBPROTO in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_RBPROTO 相同。有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：A protocol error occurred within the Resource Manager.

资源管理器中发生协议错误。

In the xa_end context, the Resource Manager has dissociated the transaction branch from the thread of control and has marked rollback-only the work performed on behalf of *xid.

在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表 *xid 执行的工作。

在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。返回后，资源管理器已回滚分支的工作并已释放所有持有的资源。

在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。当分支已标记为仅回滚时，通常会返回这些值。

In the xa_start context, the Resource Manager has not associated the transaction branch with the thread of control and has marked *xid rollback-only.

在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid rollback-only。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

-32005 A protocol error occurred in the Resource Manager.

This error is same as XA_RBPROTO in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_RBPROTO 相同。有关更多信息，请参阅 “分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：A protocol error occurred within the Resource Manager.

资源管理器中发生协议错误。

In the xa_end context, the Resource Manager has dissociated the transaction branch from the thread of control and has marked rollback-only the work performed on behalf of *xid.

在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表 *xid 执行的工作。

在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。返回后，资源管理器已回滚分支的工作并已释放所有持有的资源。

在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。

当分支已标记为仅回滚时，通常会返回这些值。

In the xa_start context, the Resource Manager has not associated the transaction branch with the thread of control and has marked *xid rollback-only.

在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid rollback-only。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

32006 The rollback was caused by a transaction branch took too long.

This error is same as XA_RBTIMEOUT in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_RBTIMEOUT 相同。有关更多信息，请参阅 “分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：The work represented by this transaction branch took too long.

此事务分支所代表的工作耗时太长。

In the xa_end context, the Resource Manager has dissociated the transaction branch from the thread of control and has marked rollback-only the work performed on behalf of *xid.

在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表*xid 执行的工作.

在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。返回后，资源管理器已回滚分支的工作并已释放所有持有的资源。

在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。

当分支已标记为仅回滚时，通常会返回这些值。

In the xa_start context, the Resource Manager has not associated the transaction branch with the thread of control and has marked *xid rollback-only.

在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid rollback-only。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

-32006 The rollback was caused by a transaction branch took too long.

This error is same as XA_RBTIMEOUT in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_RBTIMEOUT 相同。有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：The work represented by this transaction branch took too long.

此事务分支所代表的工作耗时太长。

In the xa_end context, the Resource Manager has dissociated the transaction branch from the thread of control and has marked rollback-only the work performed on behalf of *xid.

在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表*xid 执行的工作.

在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。返回后，资源管理器已回滚分支的工作并已释放所有持有的资源。

在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。

当分支已标记为仅回滚时，通常会返回这些值。

In the xa_start context, the Resource Manager has not associated the transaction branch with the thread of control and has marked *xid rollback-only.

在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid rollback-only。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

32007 The Resource Manager detected transient error.

This error is same as XA_RBTRANSIENT in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_RBTRANSIENT 相同。有关更多信息，请参阅“分布式事务处理：XA 规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：The Resource Manager has detected a transient error.

资源管理器检测到一个瞬间错误。

在 xa_commit 上下文中，资源管理器没有提交代表事务分支完成的工作。返回时，资源管理器已回滚分支的工作，并释放了所有持有的资源。只有在 TMONEPHASE 设置为标志时才能返回此值。

In the xa_end context, the Resource Manager has dissociated the transaction branch from the thread of control and has marked rollback-only the work performed on behalf of *xid.

在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表 *xid 执行的工作。

在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。返回后，资源管理器已回滚分支的工作并已释放所有持有的资源。

在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。

当分支已标记为仅回滚时，通常会返回这些值。

In the xa_start context, the Resource Manager has not associated the transaction branch with the thread of control and has marked *xid rollback-only.

在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid rollback-only。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

-32007 The Resource Manager detected transient error.

This error is same as XA_RBTRANSIENT in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_RBTRANSIENT 相同。

有关更多信息，请参阅“分布式事务处理：XA 规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：The Resource Manager detected a transient error.

资源管理器检测到一个瞬间错误。

In the xa_end context, the Resource Manager has dissociated the transaction branch from the thread of control and has marked rollback-only the work performed on behalf of *xid.

在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表 *xid 执行的工作。

在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。返回后，资源管理器已回滚分支的工作并已释放所有持有的资源。

在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。

当分支已标记为仅回滚时，通常会返回这些值。

In the xa_start context, the Resource Manager has not associated the transaction branch with the thread of control and has marked *xid rollback-only.

在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid rollback-only。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

32009 Routine returned with no effect and may be re-issued.

This error is same as XA_RETRY in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_RETRY 相同。有关更多信息，请参阅“分布式事务处理：XA 规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：In the xa_commit context, the Resource Manager is not able to commit the transaction branch at this time. This value can be returned when a blocking condition exists and TMNOWAIT was set. Note, however, that this value can also be returned even when TMNOWAIT is not set (for example, if the necessary stable storage is currently unavailable). This value cannot be returned if TMONEPHASE is set in flags. All resources held on behalf of *xid remain in a prepared state until commitment is possible. The Transaction Manager should re-issue xa_commit at a later time.

在 xa_commit 上下文中，资源管理器此时无法提交事务分支。当存在阻塞条件并设置 TMNOWAIT 时，可以返回此值。但请注意，即使未设置 TMNOWAIT，也可以返回此值（例如，如果必要的稳定存储当前不可用）。如果在标志中设置了 TMONEPHASE，则无法返回此值。代表 *xid 持有的所有资源仍然处于准备状态，直到可以提交。事务管理器应该在以后重新发出 xa_commit。

In the xa_complete context, TMNOWAIT was set in flags and no asynchronous operation has completed.

在 xa_complete 上下文中，TMNOWAIT 在标志中设置，并且没有完成异步操作。

In the xa_start context, TMNOWAIT was set in flags and a blocking condition exists.

在 xa_start 上下文中，TMNOWAIT 在标志中设置并且存在阻塞条件。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

-32009 Routine returned with no effect and may be re-issued.

This error is same as XA_RETRY in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_RETRY 相同。

有关更多信息，请参阅“分布式事务处理：XA 规范”。

In the xa_complete context, TMNOWAIT was set in flags and no asynchronous operation has completed.

在 xa_complete 上下文中，TMNOWAIT 在标志中设置，并且没有完成异步操作。

In the xa_start context, TMNOWAIT was set in flags and a blocking condition exists.

在 xa_start 上下文中，TMNOWAIT 在标志中设置并且存在阻塞条件。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

32010 The transaction branch has been heuristically committed and rolled back.

This error is same as XA_HEURMIX in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_HEURMIX 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：In the xa_commit context, due to a heuristic decision, the work done on behalf of the specified transaction branch was partially committed and partially rolled back.

在 xa_commit 上下文中，由于启发式决策，代表指定事务分支完成的工作被部分提交并部分回滚。

In the xa_rollback context, due to a heuristic decision, the work done on behalf of the specified transaction branch was partially committed and partially rolled back. A Resource Manager can return this value only if it has successfully prepared *xid.

在 xa_rollback 上下文中，由于启发式决策，代表指定事务分支完成的工作被部分提交并部分回滚。

仅当资源管理器成功准备好 *xid 时，它才能返回此值。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

-32010 The transaction branch has been heuristically committed and rolled back.

This error is same as XA_HEURMIX in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_HEURMIX 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

在 xa_commit 上下文中，由于启发式决策，代表指定事务分支完成的工作被部分提交并部分回滚。

在 xa_rollback 上下文中，由于启发式决策，代表指定事务分支完成的工作被部分提交并部分回滚。

仅当资源管理器成功准备好 *xid 时，它才能返回此值。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

32011 The transaction branch has been heuristically rolled back.

This error is same as XA_HEURRB in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_HEURRB 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

在 xa_commit 上下文中，由于启发式决策，代表指定事务分支完成的工作被回滚。

In the xa_rollback context, due to a heuristic decision, the work done on behalf of the specified transaction branch was rolled back. A Resource Manager can return this value only if it has successfully prepared *xid.

在 xa_rollback 上下文中，由于启发式决策，代表指定事务分支完成的工作被回滚。

仅当资源管理器已成功准备 *xid 时，它才能返回此值。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

-32011 The transaction branch has been heuristically rolled back.

This error is same as XA_HEURRB in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_HEURRB 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

在 xa_commit 上下文中，由于启发式决策，代表指定事务分支完成的工作被回滚。

在 xa_rollback 上下文中，由于启发式决策，代表指定事务分支完成的工作被回滚。

仅当资源管理器已成功准备 *xid 时，它才能返回此值。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

32012 The transaction branch has been heuristically committed.

This error is same as XA_HEURCOM in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_HEURCOM 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

在 xa_commit 上下文中，由于启发式决策，代表指定事务分支完成的工作已提交。

In the xa_rollback context, due to a heuristic decision, the work done on behalf of the specified transaction branch was committed. A Resource Manager can return this value only if it has successfully prepared *xid.

在 xa_rollback 上下文中，由于启发式决策，代表指定事务分支完成的工作已提交。

仅当资源管理器已成功准备 *xid 时，它才能返回此值。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

-32012 The transaction branch has been heuristically committed.

This error is same as XA_HEURCOM in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_HEURCOM 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

在 xa_commit 上下文中，由于启发式决策，代表指定事务分支完成的工作已提交。

在 xa_rollback 上下文中，由于启发式决策，代表指定事务分支完成的工作已提交。

仅当资源管理器已成功准备 *xid 时，它才能返回此值。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

32013 The transaction branch might have been heuristically completed.

This error is same as XA_HEURHAZ in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_HEURHAZ 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：In the xa_commit context, due to some failure, the work done on behalf of the specified transaction branch might have been heuristically completed.

在 xa_commit 上下文中，由于某些失败，代表指定事务分支完成的工作可能是启发式完成的。

In the xa_rollback context, due to some failure, the work done on behalf of the specified transaction branch might have been heuristically completed. A Resource Manager can return this value only if it has successfully prepared*xid.

在 xa_rollback 上下文中，由于某些失败，代表指定事务分支完成的工作可能是启发式完成的。

仅当资源管理器已成功准备 *xid 时，它才能返回此值。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

-32013 The transaction branch might have been heuristically completed.

This error is same as XA_HEURHAZ in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_HEURHAZ 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

在 xa_commit 上下文中，由于某些失败，代表指定事务分支完成的工作可能是启发式完成的。

在 xa_rollback 上下文中，由于某些失败，代表指定事务分支完成的工作可能是启发式完成的。

仅当资源管理器已成功准备 *xid 时，它才能返回此值。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

32014 Resumption must occur where suspension occurred.

This error is same as XA_NOMIGRATE in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_NOMIGRATE 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：In the xa_end context, the Resource Manager was unable to prepare the transaction context for migration. However, the Resource Manager has suspended the association. The Transaction Manager can resume the association only in the current thread. This code can be returned only when both TMSUSPEND and TMMIGRATE are set in flags. A Resource Manager that sets TMNOMIGRATE in the flags element of its xa_switch_t structure need not return [XA_NOMIGRATE].

在 xa_end 上下文中，资源管理器无法为迁移准备事务上下文。但是，资源管理器已暂停该关联。

事务管理器只能在当前线程中恢复关联。仅当在标志中设置 TMSUSPEND 和 TMMIGRATE 时，才能返回此代码。在其 xa_switch_t 结构的 flags 元素中设置 TMNOMIGRATE 的资源管理器不需要返回 [XA_NOMIGRATE]。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

-32014 Resumption must occur where suspension occurred.

This error is same as XA_NOMIGRATE in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XA_NOMIGRATE 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

在 xa_end 上下文中，资源管理器无法为迁移准备事务上下文。但是，资源管理器已暂停该关联。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

32015 Asynchronous operation already outstanding.

This error is same as XAER_ASYNC in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPENXA 规范标准中的 XAER_ASYNC 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：TMASYNC was set in flags, and either the maximum number of outstanding asynchronous operations has been exceeded, or TMUSEASYNC is not set in the flags element of the Resource Manager's xa_switch_t structure.

TMASYNC 是在标志中设置的，并且超过了未完成的异步操作的最大数量，或者 TMUSEASYNC没有在资源管理器的 xa_Switch_t 结构的标志元素中设置。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

-32015 Asynchronous operation already outstanding.

This error is same as XAER_ASYNC in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPENXA 规范标准中的 XAER_ASYNC 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

TMASYNC 是在标志中设置的，并且超过了未完成的异步操作的最大数量，或者 TMUSEASYNC没有在资源管理器的 xa_Switch_t 结构的标志元素中设置。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

32016 An Resource Manager error occurred in the transaction branch.

This error is same as XAER_RMERR in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XAER_RMERR 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：In the xa_close context, an error occurred when closing the resource.

在 xa_close 上下文中，关闭资源时发生错误。

有关更多详细信息，另请参阅“资源管理器”指南In the xa_commit context, an error occurred in committing the work performed on behalf of the transaction branch and the branch's work has been rolled back.

Note that returning this error signals a catastrophic event to a Transaction Manager because other Resource Managers might successfully commit their work on behalf of this branch. This error should be returned only when a Resource Manager concludes that it can never commit the branch and that it cannot hold the branch's resources in a prepared state. Otherwise, [XA_RETRY] should be returned.

在 xa_commit 上下文中，在提交代表事务分支执行的工作时发生错误，并且已回滚分支的工作。

请注意，返回此错误意味着事务管理器发生灾难性事件，因为其他资源管理器可能代表此分支成功提交其工作。仅当资源管理器断定它永远不能提交分支并且不能将分支的资源保持在准备状态时，才应返回此错误。否则，应返回 [XA_RETRY]。

In the xa_end context, an error occurred in dissociating the transaction branch from the thread of control.

在 xa_end 上下文中，在将事务分支与控制线程分离时发生错误。

In the xa_forget context, an error occurred in the Resource Manager and the Resource Manager has not forgotten the transaction branch.

在 xa_forget 上下文中，资源管理器中发生错误，资源管理器未忘记事务分支。

In the xa_open context, an error occurred when opening the resource.

在 xa_open 上下文中，打开资源时发生错误。

In the xa_prepare context, the Resource Manager encountered an error in preparing to commit the transaction branch's work. The specified XID might or might not have been prepared.

在 xa_prepare 上下文中，资源管理器在准备提交事务分支的工作时遇到错误。

指定的 XID 可能已准备好，也可能未准备好。

In the xa_recover context, an error occurred in determining the XIDs to return.

在 xa_recover 上下文中，确定要返回的 XID 时发生错误。

In the xa_rollback context, an error occurred in rolling back the transaction branch. The Resource Manager is free to forget about the branch when returning this error so long as all accessing threads of control have been notified of the branch's state.

在 xa_rollback 上下文中，回滚事务分支时发生错误。资源管理器在返回此错误时可以自由地忘记分支，只要所有访问控制线程都已被通知分支的状态。

In the xa_start context, an error occurred in associating the transaction branch with the thread of control.

在 xa_start 上下文中，将事务分支与控制线程相关联时发生错误。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

-32016 An Resource Manager error occurred in the transaction branch.

This error is same as XAER_RMERR in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XAER_RMERR 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：In the xa_close context, an error occurred when closing the resource.

在 xa_close 上下文中，关闭资源时发生错误。

In the xa_commit context, an error occurred in committing the work performed on behalf of the transaction branch and the branch's work has been rolled back.

在 xa_commit 上下文中，在提交代表事务分支执行的工作时发生错误，并且已回滚分支的工作。

In the xa_end context, an error occurred in dissociating the transaction branch from the thread of control.

在 xa_end 上下文中，在将事务分支与控制线程分离时发生错误。

In the xa_forget context, an error occurred in the Resource Manager and the Resource Manager has not forgotten the transaction branch.

在 xa_forget 上下文中，资源管理器中发生错误，资源管理器未忘记事务分支。

In the xa_open context, an error occurred when opening the resource.

在 xa_open 上下文中，打开资源时发生错误。

In the xa_prepare context, the Resource Manager encountered an error in preparing to commit the transaction branch's work. The specified XID might or might not have been prepared.

在 xa_prepare 上下文中，资源管理器在准备提交事务分支的工作时遇到错误。

指定的 XID 可能已准备好，也可能未准备好。

In the xa_recover context, an error occurred in determining the XIDs to return.

在 xa_recover 上下文中，确定要返回的 XID 时发生错误。

在 xa_rollback 上下文中，回滚事务分支时发生错误。资源管理器在返回此错误时可以自由地忘记分支，只要所有访问控制线程都已被通知分支的状态。

In the xa_start context, an error occurred in associating the transaction branch with the thread of control.

在 xa_start 上下文中，将事务分支与控制线程相关联时发生错误。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

32017 The XID is not valid.

This error is same as XAER_NOTA in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XAER_NOTA 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：In the xa_commit, xa_end, xa_prepare, xa_rollback context, the specified XID is not known by the Resource Manager.

在 xa_commit、xa_end、xa_prepare、xa_rollback 上下文中，资源管理器不知道指定的 xid。

In the xa_forget context, the specified XID is not known by the Resource Manager as a heuristically completed XID.

在 xa_forget 上下文中，资源管理器不知道指定的 XID 是启发式完成的 XID。

In the xa_start context, either TMRESUME or TMJOIN was set in flags, and the specified XID is not known by the Resource Manager.

在 xa_start 上下文中，在标志中设置了 TMRESUME 或 TMJOIN，并且资源管理器不知道指定的 XID。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

-32017 The XID is not valid.

This error is same as XAER_NOTA in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XAER_NOTA 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：In the xa_commit, xa_end, xa_prepare, xa_rollback context, the specified XID is not known by the Resource Manager.

在 xa_commit、xa_end、xa_prepare、xa_rollback 上下文中，资源管理器不知道指定的 xid。

In the xa_forget context, the specified XID is not known by the Resource Manager as a heuristically completed XID.

在 xa_forget 上下文中，资源管理器不知道指定的 XID 是启发式完成的 XID。

In the xa_start context, either TMRESUME or TMJOIN was set in flags, and the specified XID is not known by the Resource Manager.

在 xa_start 上下文中，在标志中设置了 TMRESUME 或 TMJOIN，并且资源管理器不知道指定的 XID。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

32018 Invalid arguments were given.

This error is same as XAER_INVAL in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XAER_INVAL 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：In the xa_close, xa_commit, xa_complete, xa_end, xa_forget, xa_open,xa_prepare, xa_rollback, or xa_start context, invalid arguments were specified.

在 xa_close、xa_commit、xa_complete、xa_end、xa_forget、xa_open、xa_prepare、xa_rollback 或 xa_start 上下文中，指定了无效参数。

In the xa_recover context, the pointer xids is NULL and count is greater than 0, count is negative, or an invalid flags was specified, or the thread of control does not have a recovery scan open and did not specify TMSTARTRSCAN in flags.

在 xa_recover 上下文中，指针 xids 为 NULL 并且 count 大于0、count为负数、或者指定了无效标志，或者控制线程没有打开恢复扫描并且未在 flags 中指定TMSTARTRSCAN。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

-32018 Invalid arguments were given.

This error is same as XAER_INVAL in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XAER_INVAL 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

在 xa_close、xa_commit、xa_complete、xa_end、xa_forget、xa_open、xa_prepare、xa_rollback 或 xa_start 上下文中，指定了无效参数。

在 xa_recover 上下文中，指针 xids 为 NULL 并且 count 大于 0、count 为负数、或者指定了无效标志，或者控制线程没有打开恢复扫描并且未在 flags 中指定 TMSTARTRSCAN。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

32019 Routine invoked in improper context.

This error is same as XAER_PROTO in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XAER_PROTO 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：The routine was invoked in an improper context.

在不正确的上下文中调用该例程。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

-32019 Routine invoked in improper context.

This error is same as XAER_PROTO in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XAER_PROTO 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：The routine was invoked in an improper context.

在不正确的上下文中调用该例程。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

32020 Resource Manager unavailable.

This error is same as XAER_RMFAIL in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XAER_RMFAIL 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：In the xa_commit, xa_end, xa_forget, xa_recover, xa_rollback, xa_start context,An error occurred that makes the Resource Manager unavailable.

在 xa_commit、xa_end、xa_forget、xa_recover、xa_rollback、xa_start 上下文中，发生了使资源管理器不可用的错误。

In the xa_prepare context, an error occurred that makes the Resource Manager unavailable. The specified XID might or might not have been prepared.

在 xa_prepare 上下文中，发生了使资源管理器不可用的错误。

指定的 XID 可能已准备好，也可能未准备好。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

-32020 Resource Manager unavailable.

This error is same as XAER_RMFAIL in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XAER_RMFAIL 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

在 xa_commit、xa_end、xa_forget、xa_recover、xa_rollback、xa_start 上下文中，发生了使资源管理器不可用的错误。

In the xa_prepare context, an error occurred that makes the Resource Manager unavailable. The specified XID might or might not have been prepared.

在 xa_prepare 上下文中，发生了使资源管理器不可用的错误。

指定的 XID 可能已准备好，也可能未准备好。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

32021 The XID already exists.

This error is same as XAER_DUPID in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XAER_DUPID 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：In the xa_start context, if neither TMRESUME nor TMJOIN was set in flags(indicating the initial use of *xid) and the XID already exists within the Resource Manager, the Resource Manager must return [XAER_DUPID]. The Resource Manager failed to associate the transaction branch with the thread of control.

在 xa_start 上下文中，如果在 flag 中未设置 TMRESUME 和 TMJOIN（表示初始使用 *xid）并且资源管理器中已存在 XID，则资源管理器必须返回[XAER_DUPID]。资源管理器无法将事务分支与控制线程相关联。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

-32021 The XID already exists.

This error is same as XAER_DUPID in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XAER_DUPID 相同。

有关更多信息，请参阅“分布式事务处理：XA规范”。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

32022 Resource Manager doing work outside global transaction.

This error is same as XAER_OUTSIDE in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XAER_OUTSIDE 相同。

有关更多信息，请参阅“分布式事务处理：XA 规范”。

According to the X/OPEN XA Specification Standard :根据 X/OPEN XA 规范标准：In the xa_start context, the Resource Manager is doing work outside any global transaction on behalf of the application.

在 xa_start 上下文中，资源管理器代表应用程序在任何全局事务之外工作。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

-32022 Resource Manager doing work outside global transaction.

This error is same as XAER_OUTSIDE in the X/OPEN XA Specification Standard.

For more information, refer to the "Distributed Transaction Processing:The XA Specification".

此错误与 X/OPEN XA 规范标准中的 XAER_OUTSIDE 相同。

有关更多信息，请参阅“分布式事务处理：XA 规范”。

在 xa_start 上下文中，资源管理器代表应用程序在任何全局事务之外工作。

Also refer to the Resource Manager guide for more details.

有关更多详细信息，另请参阅“资源管理器”指南。

32023 Error in executing an xadatasource purpose routine execution sequence.

An error occurred when an attempt was made to execute an xadatasource purpose routine. Try the statement again.

当尝试执行 xadatasource 用途的例程时，发生了错误。重新执行该语句。

-32023 Error in executing an xadatasource purpose routine execution sequence.

An error occurred when an attempt was made to execute an xadatasource purpose routine. Try the statement again.

当尝试执行 xadatasource 用途的例程时，发生了错误。重新执行该语句。

32024 Error indicated by an xadatasource purpose routine.

An xadatasource purpose routine returned MI_ERROR.

xadatasource 目的例程返回 MI_ERROR。

-32024 Error indicated by an xadatasource purpose routine.

An xadatasource purpose routine returned MI_ERROR.

xadatasource 目的例程返回 MI_ERROR。

32025 Improper return value from xadatasource purpose routine.

An xadatasource purpose routine returned a value that is not valid. Possibly a bug exists in the xadatasource purpose routine.

xadatasource 目的例程返回的值无效。可能是因为 xadatasource 目的例程存在问题。

-32025 Improper return value from xadatasource purpose routine.

An xadatasource purpose routine returned a value that is not valid. Possibly a bug exists in the xadatasource purpose routine.

xadatasource 目的例程返回的值无效。可能是因为 xadatasource 目的例程存在问题。

-26018 Table %s has a referential key constraint and is not empty.

The table being truncated has a unique or primary key that is referenced by the above table.

被截断的表具有由上面的表引用的唯一或主键。

-26019 Purpose function am_truncate not defined for table or index.

The am_truncate purpose function is not defined for the VTI table or a VII index on the table being truncated.

没有为要截断的表上的 VTI 表或 VII 索引定义 am_truncate 用途函数。

-26020 Truncating a table with delete trigger requires ALTER privilege.

You cannot truncate a table that has delete triggers unless you have ALTER privilege. A user with DELETE privilege can truncate such a table only if there are no delete triggers active.

除非您具有 ALTER 权限，否则不能截断具有删除触发器的表。具有 DELETE 权限的用户只有在没有活动的删除触发器时才能截断此类表。

-26021 No operations allowed after truncate or online alter fragment in a transaction.

The only allowed operations in a transaction after a truncate or online alter fragment are COMMIT and ROLLBACK.

在截断或在线更改分片之后，事务中唯一允许的操作是 COMMIT 和 ROLLBACK。

-26022 EXTERNAL NAME too long.

The EXTERNAL NAME clause of the CREATE FUNCTION or CREATE PROCEDURE cannot contain more than 255 characters.

CREATE FUNCTION 或 CREATE PROCEDURE 的 EXTERNAL NAME 子句不能包含超过 255 个字符。

26023 Cannot perform rename operation while non-mastered or strict mastered --column and table names must match along with data types across all replicate participants -- replicates are defined for it Rename table and column operations are allowed only on Enterprise Replication tables that are defined with non-strict mastered replicates.

With non-strict mastered replicates, column names can be different but column data types must match. Non-strict mastered replicates can be defined with --name=n attribute of 'cdr define repl' or with 'cdr modify repl' commands.

For more information about non-strict mastered replicates, mastered replicates and non-mastered replicates see Enterprise Replication Manual.

只有在使用非严格主复制定义的 Enterprise Replication 表上才允许重命名表和列操作。对于非严格的主复制，列名可以不同，但列数据类型必须匹配。非严格主复制可以用 ‘cdr define repl’的 --name=n 属性来定义，也可以用‘cdr modify repl’ 命令来定义。有关非严格主复制、主复制和不是主复制的详细信息，请参阅《Enterprise Replication 手册》。

-26023 Cannot perform rename operation while non-mastered or strict mastered --column and table names must match along with data types across all replicate participants -- replicates are defined for it Rename table and column operations are allowed only on Enterprise Replication tables that are defined with non-strict mastered replicates.

For more information about non-strict mastered replicates, mastered replicates and non-mastered replicates see Enterprise Replication Manual.

-26024 The sysdbopen and sysdbclose routines cannot have arguments or return values.

The SPL routines sysdbopen and sysdbclose must be defined without any arguments or return values.

SPL 例程 sysdbopen 和 sysdblose 必须在没有任何参数或返回值的情况下定义。

-26025 SELECT FROM INSERT syntax is disallowed in this context.

SELECT FROM INSERT syntax is not allowed in the following cases不允许在以下情况下使用 SELECT FROM INSERT 语法* SELECT statement is part of join or is nested as a subquery.

SELECT 语句是连接的一部分或它嵌套为子查询。

* SELECT statement is part of CREATE VIEW statement.

SELECT 语句是 CREATE VIEW 语句的一部分。

* SELECT statement appears as a subquery either in query predicates or projection list.

SELECT 语句作为子查询春夏在查询预备或投影列表中。

* SELECT statement appears as part of INSERT INTO SELECT statement.

SELECT 语句作为 INSERT INTO SELECT 语句的一部分。

-26026 Remote table reference in INSERT statement disallowed in SELECT FROM INSERT syntax.

SELECT FROM INSERT statement does not support remote object references in the INSERT part of statement. Please rewrite the query so that there are no remote object references in the INSERT part of the statement.

SELECT FROM INSERT 语句不支持语句的 INSERT 部分中的远程对象引用。

请重写查询，在语句的 INSERT 部分中不要出现远程对象引用。

-26027 Label label-name specified on a GOTO statement is not valid.

An undefined or invalid label is used with the GOTO statement.

The GOTO label must be defined within the same procedure.

Check the label-name for correct spelling.

未定义或无效的标签与 GOTO 语句一起使用。必须在同一程序中定义 GOTO 标签。

检查 label-name 是否正确拼写。

-26028 Label label-name must be unique within an SPL procedure.

The scope of the label-name is a procedure, so the label names must be unique between the CREATE [PROCEDURE|FUNCTION] and END [PROCEDURE|FUNCTION] keywords.

label-name 的范围是一个过程，因此标签名称在 CREATE [PROCEDURE | FUNCTION] 和END [PROCEDURE | FUNCTION] 关键字之间必须是唯一的。

-26029 GOTO cannot be used, and labels cannot be defined, within an exception h andler.

Rewrite the exception handler block so that it includes no GOTO statements.

重写异常处理程序块，使其不包含 GOTO 语句。

Example of error:错误示例：CREATE PROCEDURE testproc()BEGIN ON EXCEPTION IN (-206)<<ex_label>> -- error CREATE TABLE emp_list (lname CHAR(15));GOTO ex_label; -- error INSERT INTO emp_list VALUES ('john');END EXCEPTION WITH RESUME INSERT INTO emp_list VALUES ('john');END...

...

END PROCEDURE;-26030 Invalid usage of EXIT or CONTINUE statement, which should be within a st atement loop.

Within the SPL routine,EXIT and CONTINUE statements must be placed within a WHILE, FOR or LOOP statement loop.

在 SPL 例程中，EXIT 和 CONTINUE 语句必须放在 WHILE、FOR 或 LOOP 语句循环中。

-26031 END LOOP label label-name doesn't not match with the LOOP label label-na me.

The LOOP lable-name and END LOOP label-name do not match.

Check the label-names for correct spelling.

LOOP 标签名称和 END LOOP 标签名称不匹配。检查标签名称是否正确拼写。

-26032 Invalid label label-name used with EXIT WHEN clause.

The label is not defined or is not a valid label for the LOOP statement.

The EXIT WHEN label must be defined within a scope that the LOOP statement can reach. Check the label-names for correct spelling.

标签未定义或不是 LOOP 语句的有效标签。必须在 LOOP 语句可以达到的范围内定义 EXIT WHEN 标签。

检查标签名称是否正确拼写。

-26041 Invalid values specified for the %s environment variable.

An invalid value was provided for the environment variable. Please check your user documentation, and provide the correct value, and try again.

为环境变量提供了无效值。请检查您的用户文档，并提供正确的值，然后重试。

-26042 Function (explain_sql) failed in %s.

In the explain_sql UDR, the execution failed in the specified function.

在 explain_sql UDR 中，指定函数中的执行失败。

-26043 Function (explain_sql): The required parameter %s is NULL The required parameter is missing when you execute the explain_sql UDR.

执行 explain_sql UDR 时缺少必需的参数。

-26044 Function (explain_sql): An error occurred during the reading of the parameter %s.

An error occurred during the reading of the parameter.

读取参数时发生错误。

-26045 Warning: Function (explain_sql) %s and the current support version does not match.

The provided major_version or minor_version of explain_sql does not match the current server version. Please check your client version and make the necessary adjustment.

提供的 explain_sql 的 major_version 或 minor_version 与当前服务器版本不匹配。

请检查您的客户端版本并进行必要的调整。

-26046 Warning: Function (explain_sql): The requested locale was not provided.

The default locale %s will be used.

Because a locale was not provided in explain_sql UDR, the default locale will be used in the query.

由于 explain_sql UDR 中未提供语言环境，因此将在查询中使用缺省的语言环境。

-26047 Function (explain_sql) does not support the query provided in (%s).

Only a single select statement is supported.

Explain_sql only supports a single SELECT statement. Please change your query.

Explain_sql 仅支持单个 SELECT 语句。请更改您的查询。

-26048 Function (explain_sql) has an invalid parameter %s parameter.

The value you provided for the parameter is invalid.

您为参数提供的值无效。

-26049 Function (explain_sql) has invalid encoding (%s) for xml_input.

Xml_input should be in UTF-8 encoding.

Xml_input 应采用 UTF-8 编码。

-26050 Function (explain_sql) does not support a query with host variables.

Explain_sql only supports a single SELECT statement without any host variables.

Please change your query.

Explain_sql 仅支持没有任何主机变量的单个 SELECT 语句。请更改您的查询。

-84500 Attempt to update a stale version of a row An attempt was made to update a stale copy of a row. This caused a optimistic concurrancy failure.

尝试更新行的历史副本。这引起了乐观的并发失败。

This error can occur when using updates on secondary and the current verstion of the row has not yet been replicated to the secondary on which the client application is connected.

在辅助节点上使用更新时，可能会发生此错误，并且该行的当前版本尚未复制到客户端应用程序所连接的辅助节点。

-84501 Connection between secondary and primary has been lost The connection between the secondary and the primary has been lost. This will prevent the updates on secondary until connectivity has been reestablished.

次要和主要之间的连接已丢失。这将阻止次要更新，直到重新建立连接。

-26036 Cannot use the WITH VERCOLS clause because the table already has version columns.

The table already has version columns created by the WITH VERCOLS clause.

You cannot add additional version columns.

该表已包含由 WITH VERCOLS 子句创建的版本列。您无法添加其他版本列。

-26037 Cannot drop VERCOLS when table does not have version columns.

The table that you were attempting to alter does not have VERCOLS columns.

您尝试更改的表没有 VERCOLS 列。

-26051 EXECUTE IMMEDIATE and PREPARE cannot take NULL statement Expression that specifies SQL statement text in either EXECUTE IMMEDIATE or PREPARE evaluates to a NULL value. Make sure to pass the text of a valid SQL statement to these statements.

在 EXECUTE IMMEDIATE 或 PREPARE 中指定 SQL 语句文本的表达式求值为 NULL 值。

确保将有效 SQL 语句的文本传递给这些语句。

This error can be prevented by testing the expression passed to either EXECUTE IMMEDIATE or PREPARE for a NULL value:通过测试传递给 EXECUTE IMMEDIATE 或 PREPARE 的表达式以获取 NULL 值，可以防止此错误：Example (1)示例（1）DEFINE qStr CHAR(255);...

LET qStr = ;-- validate if above evalutes to NULL IF (qStr IS NOT NULL) THEN EXECUTE IMMEDIATE qStr;ELSE...

END IF;Example (2)示例（2）DEFINE def_lc1 INTEGER;DEFINE lc1 INTEGER;LET def_lc1 = 10;SELECT c1 INTO lc1 FROM t1 WHERE c2 = 10;-- validate if query above returns a NULL value to lc1-- if it is NULL then logic below should use default-- lc1 (def_lc1) to avoid concatenation that returns NULL IF (lc1 IS NOT NULL) THEN PREPARE stmtId FROM "select c2[" || lc1 || "] FROM t2";ELSE PREPARE stmtId FROM "select c2[" || def_lc1 || "] FROM t2";END IF;-26052 OPEN attempted on already opened cursor (%s)This OPEN statement referenced a cursor that has already been opened. Review the program logic, and CLOSE the cursor before attempting to reopen it.

此 OPEN 语句引用了已打开的游标。查看程序逻辑，并在尝试重新打开之前关闭游标。

Example below makes sure to CLOSE the cursor before trying to OPEN the same cursor with different input parameter values:下面的示例确保在尝试使用不同的输入参数值打开相同的游标之前关闭游标：Example示例OPEN c_emp USING lgivenname;...

CLOSE c_emp;OPEN c_emp USING lfamilyname;...

CLOSE c_emp;-26053 FETCH or CLOSE cannot reference cursor (%s) that is not opened The FETCH or CLOSE statement attempted to use an unopened cursor.

Make sure to OPEN the cursor before attempting FETCH or CLOSE that cursor.

FETCH 或 CLOSE 语句尝试使用未打开的游标。确保在尝试 FETCH 或 CLOSE 游标之前打开游标。

Example示例OPEN c_cust USING lfname, llname;...

FETCH c_cust INTO lcustomer_num, lcompany;...

CLOSE c_cust;-26054 Cannot FREE a cursor (%s) that is in use This FREE statement attempts to free a cursor that is still in use(i.e. not closed yet). Make sure to close this cursor by using the CLOSE statement before a FREE attempt.

此 FREE 语句尝试释放仍在使用中的游标（即尚未关闭）。确保在尝试 FREE之前使用 CLOSE 语句关闭此光标。

Example示例DECLARE c_cust CURSOR FOR s_cust;OPEN c_cust USING lfname, llname;FETCH c_cust INTO lcustomer_num, lcompany;CLOSE c_cust;FREE c_cust;-26055 Either statement-id or cursor name (%s) is not defined This error occurs when either statement-id or a cursor name is not defined before attempting to use it. Make sure to either PREPARE the statement-id or DECLARE the cursor before using it.

在尝试使用它之前未定义 statement-id 或游标名称时会发生此错误。

确保在使用之前预先使用 statement-id 或 DECLARE 游标。

-26056 Function cursor (%s) in SPL cannot have WITH HOLD option In SPL routines, the WITH HOLD option is not allowed for a function cursor declared for the EXECUTE PROCEDURE or EXECUTE FUNCTION statement.

Omit the WITH HOLD keywords while declaring this cursor.

在 SPL 例程中，对于为 EXECUTE PROCEDURE 或 EXECUTE FUNCTION 语句声明的函数游标，不允许使用 WITH HOLD 选项。在声明此游标时省略 WITH HOLD 关键字。

Only ESQL/C routines support function cursors WITH HOLD.

只有 ESQL/C 例程支持 WITH HOLD 的函数游标。

-26057 Either statement-id or cursor (%s) is already in use This error can be returned in either of the following two cases:可以在以下两种情况之一中返回此错误：Case (1)情况（1）Attempt to PREPARE a statement with the same identifier that an earlier PREPARE or DECLARE statement declared, and that has not yet been freed for re-use. Review the program logic, and either FREE this identifier before using it again for this PREPARE statement, or else specify a different identifier.

尝试使用与先前的 PREPARE 或 DECLARE 语句声明的标识符相同的标识符进行 PREPARE，并且尚未释放以备重用。查看程序逻辑，并在为此 PREPARE 语句再次使用之前释放此标识符，或者指定其他标识符。

Example below demonstrates possible way to avoid this error:下面的示例演示了避免此错误的可能方法：PREPARE s_emp FROM "select givenname from employee";PREPARE s_cust FROM "select fname from customer";...

FREE s_cust;PREPARE s_cust FROM "select lname from customer";...

FREE s_cust;FREE s_emp;Case (2)情况（2）Attempt to DECLARE a cursor with the same identifier that an earlier PREPARE or DECLARE statement declared, and that has not yet been freed for re-use. Review the program logic, and either FREE this identifier before using it again for this DECLARE statement, or else specify a different identifier.

尝试使用与先前的 PREPARE 或 DECLARE 语句声明的标识符相同的标识来 DECLARE 游标，并且尚未释放它以备重用。查看程序逻辑，并在为此DECLARE 语句再次使用之前释放此标识符，或者指定其他标识符。

Example below demonstrates possible way to avoid this error:下面的示例演示了避免此错误的可能方法：DECLARE c_emp CURSOR FOR s_emp;DECLARE c_cust CURSOR FOR s_cust;...

FREE c_emp;DECLARE c_cust CURSOR FOR s_cust;...

FREE c_cust;FREE c_emp;-26058 EXECUTE IMMEDIATE and PREPARE in SPL cannot allow multiple SQL statements Either EXECUTE IMMEDIATE or PREPARE statement in an SPL routine is trying to process an expression that evaluates to the text of more than one SQL statement. Change your program logic to pass to the EXECUTE IMMEDIATE or PREPARE statement an expression or a quoted string that evaluates to the text of only a single SQL statement.

SPL 例程中的 EXECUTE IMMEDIATE 或 PREPARE 语句正在尝试处理一个表达式，该表达式求值为多个 SQL 语句的文本。更改程序逻辑以将表达式或带引号的字符串传递给 EXECUTE IMMEDIATE 或 PREPARE 语句，该字符串仅计算单个 SQL 语句的文本。

In an SPL routine, the following examples are not valid because the EXECUTE IMMEDIATE or PREPARE statement specifies the text of more than one SQL statement:在 SPL 例程中，以下示例无效，因为 EXECUTE IMMEDIATE 或 PREPARE 语句指定了多个 SQL 语句的文本：Case (1)...

EXECUTE IMMEDIATE "create table t1(c1 int); create table t2(c2 int);" ;Case (2)...

LET qry = "select c1,c2 from t1; select c1,c2 from t2";PREPARE stmt_id FROM qry;These examples of EXECUTE IMMEDIATE and PREPARE statements are valid in an SPL routine:这些 EXECUTE IMMEDIATE 和 PREPARE 语句的示例在 SPL 例程中有效：Case (3)...

EXECUTE IMMEDIATE "create table t1(c1 int);" ;EXECUTE IMMEDIATE "create table t2(c2 int);" ;Case (4)...

LET qry1 = "select c1,c2 from t1 ;";PREPARE stmt_id1 FROM qry1;LET qry2 = "select c1,c2 from t2 ;";PREPARE stmt_id2 FROM qry2;Only ESQL/C routines can use the EXECUTE IMMEDIATE or PREPARE statement to process a semicolon-separated list of SQL statements.

只有 ESQL/C 例程可以使用 EXECUTE IMMEDIATE 或 PREPARE 语句来处理以分号分隔的 SQL 语句列表。

-26059 Unsupported data type in EXECUTE IMMEDIATE or PREPARE statement A variable passed to the EXECUTE IMMEDIATE statement or PREPARE statement in SPL must be one of the data types CHAR, VARCHAR, LVARCHAR, NCHAR, or NVARCHAR. Change your program logic to pass a variable of one of these supported data types to the EXECUTE IMMEDIATE statement or PREPARE statement in the SPL routine.

传递给 SPL 中的 EXECUTE IMMEDIATE 语句或 PREPARE 语句的变量必须是 CHAR、VARCHAR、LVARCHAR、NCHAR 或 NVARCHAR 等数据类型。更改程序逻辑，将这些支持的数据类型的变量传递给 SPL 例程中的 EXECUTE IMMEDIATE 语句或 PREPARE语句。

In an SPL routine, the following examples are not valid because the EXECUTE IMMEDIATE or PREPARE statement does not support variables of type TEXT:在 SPL 例程中，以下示例无效，因为 EXECUTE IMMEDIATE 或 PREPARE 语句不支持 TEXT 类型的变量：Case (1)DEFINE qstr REFERENCES TEXT;...

LET qstr = (SELECT textcol FROM t1 WHERE qryid = 100);EXECUTE IMMEDIATE qstr;Case (2)DEFINE qstr REFERENCES TEXT;...

LET qstr = (SELECT textcol FROM t1 WHERE qryid = 100);PREPARE stmt_id FROM qstr;The following examples include a valid EXECUTE IMMEDIATE statement and a PREPARE statement in SPL routine:以下示例在 SPL 例程中包含一个有效的 EXECUTE IMMEDIATE 语句和 PREPARE 语句:Case (3)DEFINE qstr varchar(120);...

LET qstr = "create table t1 (c1 int);";EXECUTE IMMEDIATE qstr;Case (4)DEFINE qstr lvarchar;...

LET qstr = "select lvarcol from t1 where qryid = 100";PREPARE stmt_id FROM qstr;-26060 Procedure was created with an older version of the engine and must be dropped and created again in order to work properly.

This procedure was created with an older version of the engine and contains statements like CREATE TRIGGER, CREATE TABLE with fragmentation expressions, ALTER TABLE or CREATE TABLE with constraint expressions or nested CREATE PROCEDURE statements. Such procedures must be dropped and created again using the current engine.

此过程是使用较旧版本的引擎创建的，包含 CREATE TRIGGER、带有分片表达式的 CREATE TABLE、带有约束表达式的 ALTER TABLE 或 CREATE TABLE 或嵌套的 CREATE PROCEDURE 语句等语句。必须使用当前引擎删除并再次创建此类过程。

-26061 Procedure (%s) was created with an older version of the server and must be dropped and recreated again in order to work properly.

This procedure was created with an older version of the server and contains statements similar to: CREATE TRIGGER statements, CREATE TABLE statements with fragmentation expressions, ALTER TABLE or CREATE TABLE with constraint expressions or nested CREATE PROCEDURE statements. These types of procedures must be dropped and recreated again using the current server.

此过程是使用较旧版本的服务器创建的，包含类似于以下语句的语句：CREATE TRIGGER语句、带有分片表达式的 CREATE TABLE 语句、带有约束表达式的 ALTER TABLE 或 CREATE TABLE 或嵌套的 CREATE PROCEDURE 语句。必须使用当前服务器删除并重新创建这些类型的过程。

-26062 The specified case is not defined in the CASE statement The value of the case did not match any value in the WHEN clause of the CASE statement and no ELSE clause is defined. The following example returns this error because the LET statement specifies a case that is not defined in the CASE statement.

此条件的值与 CASE 语句的 WHEN 子句中的任何值都不匹配，并且未定义 ELSE 子句。

以下示例返回此错误，因为 LET 语句指定了 CASE 语句中未定义的条件。

CREATE PROCEDURE case_proc( )RETURNING CHAR(1);DEFINE grade CHAR(1);LET grade = 'D';CASE grade WHEN 'A' THEN LET grade = 'a';WHEN 'B' THEN LET grade = 'b';WHEN 'C' THEN LET grade = 'c';END CASE;RETURN grade;END PROCEDURE;EXECUTE PROCEDURE case_proc();To reduce the risk of this error, you might revise your CASE statement logic to include an ELSE clause to take appropriate action if no WHEN condition is true,or to add additional WHEN clauses that define how to handle additional cases.

要降低此错误的风险，您可以修改 CASE 语句逻辑以包含 ELSE 子句，以便在 WHEN 条件不为真时采取适当的操作，或者添加定义如何处理其他 case 的其他 WHEN 子句。

-26063 Data type not supported with CASE statement of SPL The value specified in the CASE statement cannot be of type BLOB, CLOB, BYTE,TEXT, Collection, DISTINCT, or OPAQUE. The BOOLEAN and LVARCHAR types are the only built-in opaque data types that the CASE statement in SPL supports.

CASE 语句中指定的值不能是 BLOB、CLOB、BYTE、TEXT、Collection、DISTINCT 或 OPAQUE类型。BOOLEAN 和 LVARCHAR 类型是 SPL 中 CASE 语句支持的唯一内置不透明数据类型。

-26064 The stored procedure execution failed because a statement cannot be prepared(%s).

The stored procedure execution failed because a statement with in the stored procedure could not be prepared. Change the statement or try to run it with the EXECUTE IMMEDIATE statement.

存储过程执行失败，因为无法准备存储过程中的语句。更改语句或尝试使用 EXECUTE IMMEDIATE 语句运行它。

-26071 Update statistics is not allowed on cross database or cross server objects You can only update statistics on objects that reside in the local database.

To update statistics on objects in a remote database, connect to that database directly.

您只能更新驻留在本地数据库中的对象的统计信息。要更新远程数据库中对象的统计信息，请直接连接到该数据库。

-26072 The (%s) operator cannot be used in this context.

The word (%s) is an operator in the server and cannot be used in this context.

字符（%s）是服务器中的运算符，不能在此上下文中使用。

-11417 Selected locale/codeset will result in performance degradation.

The selected locale/codeset will result in performance degradation.

For optimum performance, use the same client and database locale.

选定的语言环境/代码集将导致性能下降。为获得最佳性能，请使用相同的客户端和数据库语言环境。

-11418 Locales not found.

The displayed locale and codeset have not been found on the client machine.

Using these locale/codeset will result in -23101 Unable to load locale categories error message. Please install the locales.

在客户端计算机上找不到显示的语言环境和代码集。使用这些语言环境/代码集将导致 -23101 无法加载语言环境类别错误消息。请安装语言环境。

-11419 The connection could not be enlisted with MSDTC.

The connection could not be enlisted with MSDTC because the distributed transaction has been committed or aborted by the transaction manager. This problem could be the result of a short transaction timeout in your application or MSDTC configuration.

无法使用 MSDTC 连接该连接，因为事务管理器已提交或中止分布式事务。此问题可能是您的应用程序或 MSDTC 配置中的短暂的事务超时引发的结果。

-11420 The MSDTC transaction is no longer active.

The MSDTC transaction is no longer active. This problem could be the result of a short transaction timeout in your application or MSDTC configuration.

MSDTC 事务无效。此问题可能是您的应用程序或 MSDTC 配置中的事务短暂超时的结果。

-11422 Smart large objects can only be used by setting SQL_INFX_ATTR_LO_AUTOMATIC.

The SQL_INFX_ATTR_LO_AUTOMATIC connection or statement level attribute must be set when working with smart large objects. You can set the SQL_INFX_ATTR_LO_AUTOMATIC attribute by setting the SQLSetConnectAttr or SQLSetStmtAttr functions or by turning on the Report Standard ODBC Types option under the Advanced tab of the ODBC Administration for GBase 8s Driver DSN.

使用智能大对象时，必须设置 SQL_INFX_ATTR_LO_AUTOMATIC 连接或语句级属性。您可以通过设置SQLSetConnectAttr 或 SQLSetStmtAttr 函数或打开 GBase 8s 驱动程序 DSN 的 ODBC 管理的“高级”选项卡下的“报告标准 ODBC 类型”选项来设置 SQL_INFX_ATTR_LO_AUTOMATIC 属性。

-26073 Savepoint name is unspecified.

The savepoint action - SAVEPOINT or RELEASE SAVEPOINT - requires a savepoint name to identify the action. Please provide a name for this action.

保存点操作 - SAVEPOINT 或 RELEASE SAVEPOINT - 需要保存点名称来标识操作。

请提供此操作的名称。

-26074 Unable to set savepoint %s.

The savepoint referenced in the statement could not be set. Check the accompanying isam error for more details.

无法设置语句中引用的保存点。请查看随附的 isam 错误以获取更多详细信息。

-26075 Unable to release savepoint %s.

The savepoint referenced in the statement could not be released. Check the accompanying isam error for more details.

无法释放语句中引用的保存点。请查看随附的 isam 错误以获取更多详细信息。

-26076 Unable to rollback to savepoint %s.

The transaction could not be rolled back to the savepoint referenced in the statement. Check the accompanying ISAM error for more details.

无法将事务回滚到语句中引用的保存点。查看随附的 ISAM 错误以获取更多详细信息。

-32026 Savepoint not found.

The savepoint referenced in the statement could not be found in the current transaction. Set a new savepoint using the "SAVEPOINT <savepoint_name>"statement.

在当前事务中找不到语句中引用的保存点。使用 “SAVEPOINT <savepoint_name>” 语句设置新的保存点。

-26077 Savepoint statements are disallowed inside triggers.

Savepoint statements cannot be executed as a trigger action.

Savepoint 语句不能作为触发器操作执行。

-32027 A savepoint with the same name exists and the UNIQUE option was specified.

The savepoint name specified in the SAVEPOINT statement was used in creating a previous savepoint, with either the previous, current, or both savepoints having the UNIQUE option. After the UNIQUE option is specified, another savepoint with the same name cannot be set in the same savepoint level until the original savepoint is released. You must either specify a different name, or else first release the UNIQUE savepoint before you reuse its identifier.

在 SAVEPOINT 语句中指定的保存点名称用于创建前一个保存点，其中前一个保存点、当前保存点或两个保存点都具有 UNIQUE 选项。指定 UNIQUE 选项后，在释放原始保存点之前，不能在相同的保存点级别上设置同名的另一个保存点。您必须指定不同的名称，或者在重用其标识符之前首先发布唯一保存点。

-32028 Limit on savepoint levels reached.

No more than 2 ** 30 of savepoint levels are valid in a transaction. New savepoint levels are automatically created for the duration of execution of a stored procedure or UDR. Recursive calls to the stored procedure or UDR also increment the savepoint level of the current transaction.

在事务中保存点级别不超过 2**30 是有效的。在存储过程或 UDR 的执行期间自动创建新的保存点级别。对存储过程或 UDR 的递归调用也会增加当前事务的保存点级别。

-26078 Rollback to savepoint disallowed on updating an old server in same transaction Rolling back to a savepoint set within a cross-server transaction is not allowed if a participating server that does not support savepoints is also updated in the same transaction. End the transaction that updated that server,and retry the ROLLBACK TO SAVEPOINT statement.

如果在同一事务中也更新了不支持保存点的参与服务器，则不允许回滚到跨服务器事务中设置的保存点。结束更新该服务器的事务，然后重试 ROLLBACK TO SAVEPOINT 语句。

-26079 CONNECT BY query resulted in a loop.

A CONNECT BY query is resulting in a cycle/loop. Use CONNECT_BY_ISCYCLE psuedo column to identify the row causing cycle/loop. Change your query to remove the row or use the NOCYCLE keyword to allow the query to skip the row.

CONNECT BY 查询导致 cycle/loop。使用 CONNECT_BY_ISCYCLE 伪标题列来标识导致cycle/loop 的行。更改查询以删除行或使用 NOCYCLE 关键字以允许查询跳过该行。

-26080 Generic error in CONNECT BY query processing.

There was a problem in processing the CONNECT BY query.

处理 CONNECT BY 查询时出现问题。

-26081 Incorrect use of the CONNECT BY keywords in this context.

The statement could not be run because CONNECT BY clause keywords were used incorrectly.Keywords that can only be used in the context of a CONNECT BY clause were used outside of a CONNECT BY clause.One of the following keywords was used outside of the context of a CONNECT BY clause:无法运行该语句，因为 CONNECT BY 子句关键字使用不正确。只能在 CONNECT BY 子句的上下文中使用的关键字在 CONNECT BY 子句之外使用。在 CONNECT BY 子句的上下文之外使用以下关键字之一：- the LEVEL, CONNECT_BY_ISLEAF, or CONNECT_BY_ISCYCLE pseudocolumn LEVEL、CONNECT_BY_ISLEAF 或 CONNECT_BY_ISCYCLE 伪列- the PRIOR or CONNECT_BY_ROOT unary operator PRIOR 或 CONNECT_BY_ROOT 一元运算符- the SYS_CONNECT_BY_PATH() function SYS_CONNECT_BY_PATH() 函数- the ORDER SIBLINGS BY clause ORDER SIBLINGS BY 子句- the START WITH expression clause START WITH 表达式子句Make sure that you have provided CONNECT BY keywords in this context.

请确保您在此上下文中已经提供了 CONNECT BY 关键字。

Make sure that you have not used nested CONNECT BY clauses in the query.

请确保您没有在此查询中使用嵌套的 CONNECT BY 子句。

-26082 CONNECT_BY_ISCYCLE is used without the NOCYCLE keyword.

The CONNECT_BY_ISCYCLE keyword is used without the NOCYCLE keyword in a CONNECT BY query. Include the NOCYCLE keyword in the CONNECT_BY_ISCYCLE context.

在 CONNECT BY 查询中使用 CONNECT_BY_ISCYCLE 关键字时没有 NOCYCLE 关键字。

在 CONNECT_BY_ISCYCLE 上下文中包含 NOCYCLE 关键字。

-26084 Cross server objects cannot be referenced in CONNECT BY queries.

The table specified in the FROM clause of a CONNECT BY query must be in a database of the Dynamic Server instance to which the session is connected. No clause of a SELECT statement that includes the CONNECT BY clause can reference a database object that is managed by a remore database server.

CONNECT BY 查询的 FROM 子句中指定的表必须位于会话所连接的 Dynamic Server实例的数据库中。包含 CONNECT BY 子句的 SELECT 语句的子句不能引用由远程数据库服务器管理的数据库对象。

If you need to perform a CONNECT BY query on a table that resides in a database of a remote server, you should first connect to that database, and then issue the CONNECT BY query on the (local) table.

如果需要对驻留在远程服务器的数据库中的表执行 CONNECT BY 查询，则应首先连接到该数据库，然后在（本地）表上发出 CONNECT BY 查询。

-26085 You cannot have a CONNECT BY query on a join of two or more tables.

The FROM clause of a CONNECT BY query cannot have a join of two or more tables.

CONNECT BY 查询的 FROM 子句不能具有两个或多个表的连接。

For example, the following statements generate an error:例如，以下语句生成错误：SELECT empid, name, mgrid, deptdesc FROM (employee INNER JOIN department ON employee.deptid == department.deptid)START WITH employee.name = 'David'CONNECT BY PRIOR employee.empid = employee.mgrid;SELECT *FROM employee, employee AS new CONNECT BY PRIOR employee.empid = new.mgrid;The following statement is correct:以下语句是正确的：SELECT empid, name, mgrid FROM employee START WITH employee.name = 'David'CONNECT BY PRIOR employee.empid = employee.mgrid;-26087 Incorrect use of the bson unwind in this context.

The statement could not be run because bson unwind clause was used incorrectly.

无法运行该语句，因为 bson unwind 子句使用不正确。

-26090 Column (%s) not found in the target table.

This error is generated when a user tries to insert or update data into a column that is not from the target table. For example:当用户尝试将数据插入或更新到不是目标表的列时，会生成此错误。例如：create table bonus (id int, bonus int);create table emp(id int, salary int);MERGE INTO bonus D USING emp S ON D.id = S.id WHEN MATCHED THEN UPDATE SET bonus = bonus + salary*.01 WHEN NOT MATCHED THEN INSERT (id, salary) VALUES (S.id, salary);This will generate the following error because salary in the insert column list is not from the target table, bonus:这将生成以下错误，因为插入列列表中的工资不是来自目标表，bonus：26090: Column (salary) not found in the target table.

Error in line 4 Near character position 41 MERGE INTO bonus USING emp ON bonus.id = emp.id WHEN MATCHED THEN UPDATE SET salary = 1000 WHEN NOT MATCHED THEN INSERT VALUES (10, 100);This will generate the following error because salary in the set clause of the update is not from the target table, bonus:这将生成以下错误，因为更新的 set 子句中的 salary 不是来自目标表 bonus：26090: Column (salary) not found in the target table.

Error in line 3 Near character position 44-26091 Table (%s) is not the target table.

This error is generated when a user tries to insert data into a column that is not from the target table. For example:当用户尝试将数据插入非目标表的列时，会生成此错误。例如：create table bonus (id int, bonus int);create table emp(id int, salary int);MERGE INTO bonus D USING emp S ON D.id = S.id WHEN MATCHED THEN UPDATE SET bonus = bonus + salary*.01 WHEN NOT MATCHED THEN INSERT (id, emp.bonus) VALUES (S.id, salary);This will generate the following error because the emp.bonus table name is not the bonus target table:这将生成以下错误，因为 emp.bonus 表名称不是 bonus 目标表：26091: Table (emp) is not the target table.

Error in line 4 Near character position 47-26092 Column (%s) is not found in the source table.

This error is generated when a user tries to insert data into the target table using a column from the target table. For example:当用户尝试使用目标表中的列将数据插入目标表时，会生成此错误。例如：create table bonus (id int, bonus int);create table emp(id int, salary int);MERGE INTO bonus D USING emp S ON D.id = S.id WHEN MATCHED THEN UPDATE SET bonus = bonus + salary*.01 WHEN NOT MATCHED THEN INSERT (D.id, D.bonus) VALUES (S.id, bonus);This will generate the following error because in the VALUE clause the bonus column is not from the emp source table:这将生成以下错误，因为在 VALUE 子句中，bonus 列不是来自 emp 源表：26092: Column (bonus) not found in the source table.

Error in line 4 Near character position 66-26093 Table (%s) is not the source table.

This error is generated when a user tries to insert data into the target table using the column from the target table. For example:当用户尝试使用目标表中的列将数据插入目标表时，会生成此错误。例如：create table bonus (id int, bonus int);create table emp(id int, salary int);MERGE INTO bonus D USING emp S ON D.id = S.id WHEN MATCHED THEN UPDATE SET bonus = bonus + salary*.01 WHEN NOT MATCHED THEN INSERT (D.id, D.bonus) VALUES (D.id, salary);This will generate the following error because the salary column in the VALUE clause is not from the source table, emp:这将生成以下错误，因为 VALUE 子句中的 salary 列不是来自源表 emp：26093: Table (d) is not the source table.

Error in line 4 Near character position 61-26094 The MERGE operation is not allowed on this target table (%s).

The Target table in a MERGE statement cannot be a pseudo SMI table, a catalog table, a remote table, a VTI table or an external table.

MERGE 语句中的 Target 表不能是伪 SMI 表、目录表、远程表、VTI 表或外部表。

-26095 Cannot update or delete a row twice in a MERGE statement.

If you do a MERGE operation, the join condition and any filters must be sufficiently strict so that no row of the target table is produced more than once for updating or deleting. The error occurred because the same row was processed twice. The query was terminated abnormally.

如果执行 MERGE 操作，则连接条件和任何过滤器必须足够严格，以便不会多次生成目标表的行以进行更新或删除。发生错误是因为同一行处理了两次。查询异常终止。

Either clean the data source or sources, or make the query more restrictive so that no target table row is produced more than once for updating or deleting.

清理一个或多个数据源，或使查询更具限制性，以便不会多次生成目标表行以进行更新或删除。

-26096 Cannot define INSTEAD OF trigger on a view when the view is specified as the target in the MERGE statement.

When the target of a MERGE statement is a view, then INSTEAD OF insert and update triggers cannot be defined on the view. Delete triggers can be specified as they are anyway ignored by the MERGE statement.

当 MERGE 语句的目标是视图时，无法在视图上定义 INSTEAD OF 插入和更新触发器。

可以指定删除触发器，因为 MERGE 语句无论如何都会忽略它们。

When this situation occurs, consider merging into the base table directly instead of into the view. The other alternative is to drop or disable the trigger.

发生这种情况时，请考虑直接合并到基表中而不是合并到视图中。另一种方法是删除或禁用触发器。

-26098 In a MERGE statement, the security policies of the target table and source table (%s) do not match.

The Label Based Access Control security polices of the source and target tables in a MERGE statement must be the same.

MERGE 语句中源表和目标表的基于标签的访问控制安全策略必须相同。

If the source table object in the USING clause is a subquery that accesses multiple tables, you can remove the source table whose policy differs from the target table from the USING clause of the MERGE statement.

如果 USING 子句中的源表对象是访问多个表的子查询，则可以从 MERGE 语句的 USING 子句中删除其策略与目标表不同的源表。

-26099 The optimizer cannot choose a viable plan based on the ON clause filter specified in the MERGE statement.

Hash-join is the preferred join method between source and target tables in the MERGE statement. The optimizer currently prevents nested loop joins from occurring when the target table is the inner table of a join. If a hash-join plan is also not feasible, then the optimizer throws this error.

哈希连接是 MERGE 语句中源表和目标表之间的首选连接方法。当目标表是连接的内部表时，优化器阻止发生嵌套循环连接。如果散列连接计划也不可行，则优化器会抛出此错误。

When this error occurs, try to change the ON condition so that at least one equality predicate is specified between the source and target tables on non-complex data-types. If this is not feasible, please contact GBase 8s technical support.

发生此错误时，尝试更改 ON 条件，以便在非复杂数据类型的源表和目标表之间指定至少一个等号。

如果不可行，请联系 GBase 8s 技术支持。

-26151 Could not write to external table file: errno, filename.

An error occurred when the database server tried to write to the reject file.

数据库服务器尝试写入拒绝文件时发生错误。

Look for operating-system messages that might give more information.

Possible causes include a full disk or a disk quota limit.

查找可能提供更多信息的操作系统消息可能的原因包括完整磁盘或磁盘配额限制。

-26152 Could not exclusively lock external table.

Another user is currently using the external table.

Wait for the external table to be unlocked before you proceed.

另一个用户当前正在使用外部表。等待外部表解锁，然后再继续。

-26153 Could not close external table.

An error occurred when the database server tried to close the external table lock. Note all circumstances and contact GBase Software Support.

数据库服务器尝试关闭外部表锁时发生错误。请注意所有情况并联系 GBase 软件支持。

-26154 Could not open file: errno, filename.

An error occurred when the database server tried to open the file. Check the accompanying error for more information. Possible causes include missing file or incorrect permissions.

数据库服务器尝试打开文件时发生错误。请查看随附的错误以获取更多信息。

可能的原因包括丢失文件或不正确的权限。

-26155 Could not close external table file: errno, filename.

An error occurred when the database server tried to close the file. Look for operating-system messages that might give more information.

Possible causes include a full disk or hardware errors.

数据库服务器尝试关闭该文件时发生错误。查找可能提供更多信息的操作系统消息。

可能的原因包括磁盘已满或硬件错误。

-26156 Failed to read from file: errno, filename.

An error occurred when the database server tried to read from the file.

Check the accompanying error for more information.

数据库服务器尝试从该文件读取时发生错误。请查看随附的错误以获取更多信息。

-26157 File is incorrectly specified as a DISK type: (file)=(%s).

The file named in the external table was designated as a "DISK" file type,but it is not a disk file. If this file is a UNIX named pipe, change the file type in the external table to type "PIPE".

外部表中指定的文件被指定为 “DISK” 文件类型，但它不是磁盘文件。如果此文件是 UNIX 命名管道，请更改外部表中的文件类型以键入 “PIPE”。

-26158 File is incorrectly specified as a PIPE type: (file)=(%s).

The file named in the external table was called a "PIPE" file type,but it is not a UNIX named pipe. If this file is a disk file, change the file type in the external table to "DISK".

外部表中指定的文件称为 “PIPE” 文件类型，但它不是 UNIX 命名管道。如果此文件是磁盘文件，请将外部表中的文件类型更改为 “DISK”。

-26159 Error accessing AIO buffer: errno, filename.

An error occurred when the database server tried to read or write from an internal AIO buffer. Note all circumstances and contact GBase Software Support.

数据库服务器尝试从内部 AIO 缓冲区读取或写入时发生错误。请注意所有情况并联系 GBase 软件支持。

-26160 Could not remove the external table file: errno, filename.

An error occurred when the database server tried to remove the indicated file. Look for operating-system messages that might give more information. A likely cause is incorrect permissions.

数据库服务器尝试删除指定的文件时发生错误。查找可能提供更多信息的操作系统消息。

可能的原因是权限不正确。

-26161 External table internal error: errno, filename.

Note all circumstances and contact GBase Software Support regarding this internal error.

请注意所有情况并联系 GBase 软件支持以了解此内部错误。

-26162 Failed to start an AIO operation: errno, filename.

An error occurred when the database server tried to read or write to a datafile. Check the accompanying error for more information.

数据库服务器尝试读取或写入数据文件时发生错误。请查看随附的错误以获取更多信息。

-26163 Target table cannot have any BLOB columns.

The BLOB column type is not supported for the target column in an External table.

外部表中的目标列不支持 BLOB 列类型。

-26164 External table data conversion failure (unload).

A conversion failure occurred when the database server tried to convert the data to ASCII format.

数据库服务器尝试将数据转换为 ASCII 格式时发生转换失败。

Check that the external table columns have enough space reserved to write the ASCII representation of the data and that the columns in the external table are compatible with the data selected.

检查外部表列是否有足够的空间来写入数据的 ASCII 表示以及外部表中的列。

-26165 Datafile full (unload).

An error occurred when the database server tried to write to the unload data file. No additional data can be written to the file.

数据库服务器尝试写入卸载数据文件时发生错误。无法将其他数据写入文件。

Allocate more space for the file and try again.

为文件分配更多空间，然后重试。

-26166 Datafile AIO write error (unload): errno.

An error occurred when the database server tried to write to the unload datafile. Check the accompanying error for more information.

数据库服务器尝试写入卸载数据文件时发生错误。请查看随附的错误以获取更多信息。

-26167 All data files are either full or corrupted (unload).

An error occurred during the unload. Look for operating-system messages that might give more information. Possibly all disks with data files are full hardware problems have occurred.

卸载期间发生错误。查找可能提供更多信息的操作系统消息。

可能所有带有数据文件的磁盘都发生了完整的硬件问题。

-26168 Conversion error: errno, filename.

当数据库服务器尝试从该文件加载时，它遇到错误。除非在外部表中指定了拒绝文件，否则数据库服务器将返回错误消息，并且加载作业将结束而不保存已加载的数据。

Check for conversion errors, rows that violate constraints defined on the external table, or null columns that were defined as NOT NULL.

检查转换错误，违反外部表定义的约束的行，或者定义为 NOT NULL 的空列。

A reason code of UNSUPPORTED_ROW_SIZE indicates that the external table row size (other than BYTE and TEXT columns) is greater than 32K.

UNSUPPORTED_ROW_SIZE 的原因代码表示外部表行大小（BYTE 和 TEXT 列除外）大于 32 K。

-26169 Failed to access file: errno, filename.

An error occurred when the database server tried to write to the reject file.

数据库服务器尝试写入拒绝文件时发生错误。

Check the accompanying operating-system error indication for more information.

有关详细信息，请查看随附的操作系统错误指示。

-26170 Could not find record end: must stop loading.

An error occurred when the database server tried to find a record delimiter in the delimited load file.

数据库服务器尝试在分隔的加载文件中查找记录分隔符时发生错误。

Check to see that the file has record delimiters (normally new-line characters) and that the external table has defined the correct record delimiter.

检查文件是否有记录分隔符（通常是换行符），并且外部表已定义了正确的记录分隔符。

-26171 Cannot undo partial write to filename when detecting a full disk.

An error occurred when the database server tried to continue after running out of space for one data file. When the database server detects that the disk is full, it writes to the data file a partial record, which cannot be truncated.

数据库服务器在耗尽一个数据文件的空间后尝试继续时发生错误。当数据库服务器检测到磁盘已满时，它会向数据文件写入部分记录，该记录不能被截断。

Look for operating-system messages that might give more information.

查找可能提供更多信息的操作系统消息。

-26172 There are too many keywords in USING clause.

The CREATE EXTERNAL table statement contains more than one occurrence of a keyword expected in the USING clause.

CREATE EXTERNAL 表语句包含 USING 子句中预期的多个关键字。

Review the statement. If you meant to use another keyword, correct the statement before you reissue it.

检查语句。如果打算使用其他关键字，请在重新发布之前更正该语句。

-26173 Incorrect value for a keyword.

The CREATE EXTERNAL TABLE statement contains an incorrect value for one of the USING clause keywords.

CREATE EXTERNAL TABLE 语句包含的 USING 子句关键字的值不正确。

Review the statement to see if the value of the keyword is misspelled.

For the MAXERRORS keyword, make sure the value is a valid number.

查看该语句以查看关键字的值是否拼写错误。对于 MAXERRORS 关键字，请确保该值为有效数字。

-26174 Incorrect DATAFILES entry.

A DATAFILES entry does not have the correct format. The format for an entry is filetype:rooted-path-name.

DATAFILES 条目的格式不正确。条目的格式为 filetype:rooted-path-name。

Check that the file type is a valid type (DISK or PIPE), that the second item names a item names a file that can be accessed.

检查文件类型是否为有效类型（DISK 或 PIPE），第二项指定可以访问的文件。

-26175 DATAFILES entry are missing.

The DATAFILES entry in the CREATE EXTERNAL TABLE statement is missing. Add a DATAFILES entry and reissue the statement.

CREATE EXTERNAL TABLE 语句中的 DATAFILES 条目丢失。添加一个 DATAFILES条目并重新发出该语句。

-26176 Cannot use SAMEAS for FIXED format tables.

The CREATE EXTERNAL TABLE statement does not allow the SAMEAS keyword for FIXED format tables. The column entries must also define an external type to describe how to access the data in the fixed file.

CREATE EXTERNAL TABLE 语句不允许 FIXED 格式表的 SAMEAS 关键字。列项还必须定义外部类型，以描述如何访问固定文件中的数据。

Revise the CREATE EXTERNAL TABLE statement to enumerate the column information and reissue the statement.

修改 CREATE EXTERNAL TABLE 语句以枚举列信息并重新发出该语句。

-26178 Incorrect external column type column-name.

The CREATE EXTERNAL TABLE statement contains an incorrect external column type.

CREATE EXTERNAL TABLE 语句包含不正确的外部列类型。

Make sure the external column type is CHAR(size)确保外部列类型为 CHAR(size)。

-26179 FIXED or DELIMITED columns must be external CHAR type column-name.

The CREATE EXTERNAL TABLE statement contains an external column type that is not valid. If the table describes a FIXED format file, the valid external- column type is CHAR. CHAR data must be enclosed in quotation marks.

CREATE EXTERNAL TABLE 语句包含无效的外部列类型。如果表描述了 FIXED 格式文件，则有效的外部列类型为 CHAR。CHAR 数据必须用引号括起来。

如果表描述 DELIMITED 格式文件并包含外部列类型，则类型必须为 CHAR。

描述 DELIMITED 格式文件的表不需要包含外部列类型信息。

-26180 Missing external column type column-name.

The CREATE EXTERNAL TABLE statement is missing the external-column-type information. This information is required for tables that describe FIXED format files.

CREATE EXTERNAL TABLE 语句缺少外部列类型信息。描述 FIXED 格式文件的表需要此信息。

Add the column-type information and resubmit the statement.

添加列类型信息并重新提交该语句。

-26181 Only FIXED format columns can declare a null column-name.

The CREATE EXTERNAL TABLE table statement has found a column defining a null string with the NULL "null-string" syntax that is not valid. Only tables that describe FIXED format files can have a null value defined with the NULL keyword.

CREATE EXTERNAL TABLE 表语句找到了一个列，该列定义了一个空字符串，其 NULL “null-string” 语法无效。只有描述 FIXED 格式文件的表可以使用 NULL 关键字定义空值。

Rework the statement and resubmit it.

修改语句并重新提交。

-26182 Incorrect file type in DATAFILES string datafile entry.

An error occurred when the database server tried to expand the DATAFILES entries in an INSERT or SELECT statement for an external table. The external table has a DATAFILES entry with an incorrect file type. Only DISK and PIPE file types are allowed for external tables.

当数据库服务器尝试在外部表的 INSERT 或 SELECT 语句中展开 DATAFILES 条目时发生错误。

外部表具有 DATAFILES 条目，文件类型不正确。外部表只允许使用 DISK 和 PIPE 文件类型。

Examine the external-table entry, drop the external table, and reissue a corrected CREATE EXTERNAL TABLE statement to correct this error.

检查外部表条目，删除外部表，然后重新发出更正的 CREATE EXTERNAL TABLE语句以更正此错误。

-26183 Could not replace r macro in filename entry.

An error occurred when the database server tried to expand the node host-name macro in the filename in a DATAFILES entry in an INSERT or SELECT statement for an external table.

当数据库服务器尝试在外部表的 INSERT 或 SELECT 语句的 DATAFILES 条目中的文件名中展开节点主机名宏时发生错误。

If the error recurs, note all circumstances and contact GBase Software Support.

如果错误再次出现，请记录所有情况并联系 GBase 软件支持。

-26184 Could not parse r macro in filename entry.

当数据库服务器尝试在外部表的 INSERT 或 SELECT 语句中展开 DATAFILES 条目时发生错误。数据库服务器尝试在文件名中展开 %r 宏时发生错误。检查 %r() 宏的语法是否正确。

-26185 None of the DATAFILES strings name valid data files.

An error occurred when the database server tried to expand the DATAFILES entries in an INSERT or SELECT statement for an external table. No valid filenames were found in the DATAFILES entries.

当数据库服务器尝试在外部表的 INSERT 或 SELECT 语句中展开 DATAFILES 条目时发生错误。在 DATAFILES 条目中找不到有效的文件名。

Examine the external tables entry, drop the external table, and reissue a corrected CREATE EXTERNAL TABLE statement.

检查外部表条目，删除外部表，然后重新发出更正的 CREATE EXTERNAL TABLE 语句。

-26186 File name is too long: file_name.

The name of the file in the external table is too long (after expanding all the file macros). Check to see that the full path name of the file is less than 257 characters long.

外部表中文件的名称太长（在展开所有文件宏之后）。检查文件的完整路径名是否小于 257 个字符。

-26187 Cannot select from multiple external tables.

Only one external table can be used in a SELECT query. For unions,each UNION contributor can have one external table. External tables are allowed as participants in joins and subqueries along with other database tables.

SELECT 查询中只能使用一个外部表。对于 unions，每个 UNION 贡献者可以有一个外部表。

允许将外部表与其他数据库表一起作为联接和子查询的参与者。

-26188 Null string is too long or has an incorrect format.

The CREATE EXTERNAL TABLE statement has a column with incorrect NULL"null-string" syntax. The NULL string for this column is longer than the external column length declared or is not a recognized format for the external type.

CREATE EXTERNAL TABLE 语句的列具有不正确的 NULL“null-string” 语法。

此列的 NULL 字符串比声明的外部列长度长，或者不是外部类型的可识别格式。

Check the CREATE EXTERNAL TABLE statement to make sure that the NULL"null-string" length agrees with the size and format defined for the external column type.

检查 CREATE EXTERNAL TABLE 语句以确保 NULL“null-string” 长度与为外部列类型定义的大小和格式一致。

-26189 Cannot use a clause with a SELECT statement into an external table.

The SELECT statement contains a FOR UPDATE or FORMAT "FIXED" clause.

When the database server unloads to an external table, these clauses are not allowed.

SELECT 语句包含 FOR UPDATE 或F ORMAT“FIXED” 子句。当数据库服务器卸载到外部表时，不允许使用这些子句。

Check the SELECT statement or when the SELECT cursor was defined, and make sure you do not include either of these clauses.

检查 SELECT 语句或定义 SELECT 游标时，确保不包含这些子句。

-26190 Insert into an external table must provide values for all columns in the table.

The INSERT statement does not list all the columns that the external table defines. When the database server unloads to an external table, all columns must have values described by the SELECT list.

INSERT 语句不会列出外部表定义的所有列。当数据库服务器卸载到外部表时，所有列都必须具有 SELECT 列表描述的值。

Check the INSERT statement to make sure that all columns are included in the INSERT clause and that every column has a value supplied by the SELECT list.

检查 INSERT 语句以确保 INSERT 子句中包含所有列，并且每列都有 SELECT 列表提供的值。

-26191 Incorrect use of an external table tablename in query.

This statement describes an operation that is not allowed on an external table. The types of operations allowed for external tables are CREATE EXTERNAL TABLE, SELECT, DROP TABLE, GRANT (only SELECT and INSERT),REVOKE, CREATE SYNONYM, CREATE SCHEMA, RENAME COLUMN, RENAME TABLE,SELECT ... INTO EXTERNAL.

此语句描述外部表上不允许的操作。外部表允许的操作类型有:CREATE EXTERNAL TABLE、SELECT、DROP TABLE、GRANT （仅限于 SELECT 和 INSERT）、REVOKE、CREATE SYNONYM、CREATE SCHEMA、RENAME COLUMN、RENAME TABLE、SELECT ... INTO EXTERNAL。

The types of operations not allowed for external tables are TRUNCATE, UPDATE STATISTICS, START VIOLATION, STOP VIOLATION, ALTER TABLE,UPDATE, DELETE, CREATE TRIGGER, CREATE INDEX, CONNECT BY, INSERT INTO ...

VALUES, LBAC operations, target tables of MERGE statements and template table for SAMEAS clause of CREATE EXTERNAL TABLE.

外部表不允许的操作类型是 TRUNCATE、UPDATE STATISTICS、START VIOLATION、STOP VIOLATION、ALTER TABLE、UPDATE、DELETE、CREATE TRIGER、CREATE INDEX、CONNECT BY、INSERT INTO ... VALUES、LBAC 操作、MERGE 语句的目标表 CREATE的 SAMEAS 子句的模板表外部表。

-26192 Column too long for fixed field. (Val = value, Col = colno,Len = converted length, Max = maxLen).

When the database server tried to convert the column to FIXED file format, the size of the converted value was longer than the maximum size defined for the fixed- size field.

当数据库服务器试图将列转换为固定文件格式时，转换值的大小大于为固定大小字段定义的最大大小。

Check that the external table description defines enough space in the external column type to hold the data selected after conversion.

检查外部表描述是否在外部列类型中定义了足够的空间来保存转换后选择的数据。

-26193 An external table must be a fixed format file if it has an external column type column-name.

An external column type of CHAR was found for an external table that is not defined as a FIXED-format file.

为外部表找到了外部列类型的 CHAR，该外表未定义为 FIXED 格式文件。

-26194 Unknown external column type column-name.

The CREATE EXTERNAL TABLE statement contains an external-column type that was not recognized. The valid external-column type is CHAR. CHAR values must be in quotation marks.

CREATE EXTERNAL TABLE 语句包含无法识别的外部列类型。有效的外部列类型是 CHAR。

CHAR 值必须使用引号。

Check the CREATE EXTERNAL TABLE statement to make sure that the external-column types are valid.

检查 CREATE EXTERNAL TABLE 语句以确保外部列类型有效。

-26195 No constraints can be defined for external tables.

The CREATE EXTERNAL TABLE statement contains one or more types of constraint that are not allowed.

CREATE EXTERNAL TABLE 语句包含一个或多个不允许的约束类型。

Check the statement for primary-key, referential, or unique constraints on a column or for the table.

检查语句中列或表的主键、引用或唯一约束。

-26196 Internal type must be a numeric type column-name.

The CREATE EXTERNAL TABLE statement contains external-column types that do not agree with the internal-column type.

CREATE EXTERNAL TABLE 语句包含与内部列类型不一致的外部列类型。

Check the CREATE EXTERNAL TABLE statement to make sure any external-column types agree with the internal-column type.

检查 CREATE EXTERNAL TABLE 语句以确保外部列类型与内部列类型一致。

-26197 Reached maximum error limit during load: errno, filename.

When the database server tried to load the data from the external table,the server reached the MAXERRORS limit defined for the external table.

当数据库服务器尝试从外部表加载数据时，服务器达到为外部表定义的 MAXERRORS 限制。

-26198 Cannot modify an external table that is also used in the subquery.

The external table cannot be used in the subquery. Check the statement to see if the external table is used in the subquery.

不能在子查询中使用外部表。检查语句以查看子查询中是否使用了外部表。

-26199 The RETAINUPDATELOCKS session environment cannot be set in a nonlogging database.

-26200 The RETAINUPDATELOCKS session environment cannot be set on secondary server in a high-availability cluster.

-26213 CREATE EXTERNAL TABLE: The DELIMITER keyword is not valid for FIXED format tables.

-26214 Cannot perform this operation on an external table.

The following types of operations with external tables are not allowed:不允许使用以下类型的外部表操作：- including an external table in a subquery or in an outer join在子查询或外连接中包括外部表- including BLOB or CLOB columns from external tables in joins, UNION clauses, or ORDER BY clauses包括连接、UNION 子句或 ORDER BY 子句中的从外部表中包含 BLOB 或 CLOB 列- including a subquery or stored procedure if the main query references BLOB or CLOB columns in external tables如果主查询引用外部表中的 BLOB 或 CLOB 列，则包括子查询或存储过程- using subscripts as BLOB or CLOB columns from external tables使用下标作为外部表的 BLOB 或 CLOB 列- selecting BLOB or CLOB columns from external tables out of order不按顺序从外部表中选择 BLOB 或 CLOB 列- selecting a BLOB or CLOB column from one external table and inserting it into a different external table从一个外部表中选择 BLOB 或 CLOB 列并将其插入到不同的外部表中- selecting BYTE and TEXT column to temporary table or through client API选择 BYTE 和 TEXT 列到临时表或通过客户端 API-26216 CREATE EXTERNAL TABLE: The RECORDEND keyword is not valid for FIXED format tables.

-26381 BLOBDIR directory (%s) does not exist or is not accessible.

The BLOBDIR value specified with the CREATE EXTERNAL or SELECT INTO EXTERNAL statement does not exist or is not accessible使用 CREATE EXTERNAL 或 SELECT INTO EXTERNAL 语句指定的 BLOBDIR 值不存在或无法访问。

-26382 CLOBDIR directory (%s) does not exist or is not accessible.

The CLOBDIR value specified with the CREATE EXTERNAL or SELECT INTO EXTERNAL statement does not exist or is not accessible使用 CREATE EXTERNAL 或 SELECT INTO EXTERNAL 语句指定的 CLOBDIR 值不存在或不可访问。

-26383 DATAFILES string (%s) with file type PIPE is not supported with BLOB/CLOB types The PIPE option is not supported in the DATAFILES clause when BLOB or CLOB data types are specified in the external table definition or in the table referenced in the SAMEAS clause. The following is an example of when this error is returned:当在外部表定义或 SAMEAS 子句中引用的表中指定 BLOB 或 CLOB 数据类型时，DATAFILES 子句中不支持 PIPE 选项。以下是返回此错误的示例：CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 BLOB, col3 CLOB)USING(DATAFILES("PIPE:/tmp/ext_byte.dat.%r(1..2);CLOBDIR:/tmp/clobdir1.%r(1..2);BLOBDIR=/tmp/blobdir1.%r(1..2)"),DELUXE,DELIMITER "%",recordend "\n",maxerrors 20,rejectfile "/tmp/ext_byte.log");To fix the problem in example above, please change the definition to use file type DISK instead of PIPE.

要解决上述示例中的问题，请更改定义以使用 DISK 文件类型而不是 PIPE。

-26384 FORMAT (%s) is not supported with BLOB, CLOB, BYTE or TEXT types The FORMAT type specified is not supported with BLOB, CLOB, BYTE or TEXT types.

Use DELIMITED FORMAT when specifying BLOB, CLOB, BYTE, TEXT data types.

The following is an example when this error is returned:BLOB、CLOB、BYTE 或 TEXT 类型不支持指定的格式类型。在指定 BLOB、CLOB、BYTE 和TEXT 数据类型时使用分隔格式。以下是返回此错误时的示例：CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 BLOB, col3 CLOB, col4 BYTE,col5 TEXT)USING(DATAFILES("DISK:/tmp/ext_byte.dat.%r(1..2);CLOBDIR:/tmp/clobdir1.%r(1..2);BLOBDIR=/tmp/blobdir1.%r(1..2)"),DELUXE,DELIMITER "%",recordend "\n",maxerrors 20,rejectfile "/tmp/ext_byte.log"FORMAT 'FIXED');To fix the problem in example above, please change the definition to use FORMAT type DELIMITED instead of type FIXED.

若要解决上述示例中的问题，请将定义更改为使用 FORMAT 类型 DELIMITED 而不是 FIXED 类型。

FORMAT cannot be GBASEDBT or FIXED if the external table contains BLOB, CLOB,BYTE or TEXT columns.

如果外部表包含 BLOB、CLOB、BYTE 或 TEXT 列，则 FORMAT 不能是 GBASEDBT 或 FIXED。

-26385 Could not parse r macro in BLOBDIR %s.

Could not parse the formatting macro r in BLOBDIR string. Refer to the example below for the correct usage:无法解析 BLOBDIR 字符串中的格式化宏 r。请参阅以下示例以了解正确用法：CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 BLOB, col3 CLOB)USING(DATAFILES("DISK:/tmp/ext_byte.dat.%r(1..2);CLOBDIR:/tmp/clobdir1.%r(1..2);BLOBDIR=/tmp/blobdir1.%r(1..2)"),DELUXE,DELIMITER "%",recordend "\n",maxerrors 20,rejectfile "/tmp/ext_byte.log");-26386 Could not parse r macro in CLOBDIR %s.

Could not parse the formatting macro r in CLOBDIR string. Refer to the example below for the correct usage:无法解析 CLOBDIR 字符串中的格式化宏 r。有关正确用法，请参阅下面的示例：CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 BLOB, col3 CLOB)USING(DATAFILES("DISK:/tmp/ext_byte.dat.%r(1..2);CLOBDIR:/tmp/clobdir1.%r(1..2);BLOBDIR=/tmp/blobdir1.%r(1..2)"),DELUXE,DELIMITER "%",recordend "\n",maxerrors 20,rejectfile "/tmp/ext_byte.log");-26387 Cannot use r macro in BLOBDIR %s without having a matching macro in filename %s.

Could not use the formatting macro r in BLOBDIR string without having a corresponding r macro in the DISK filename.

The following is an example of when this error is returned:如果磁盘文件名中没有相应的 r 宏，则无法使用 BLOBDIR 字符串中的格式化宏 r。

以下是返回此错误的示例：CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 BLOB)USING(DATAFILES("DISK:/tmp/ext_byte.dat;BLOBDIR=/tmp/blobdir1.%r(1..2)"),DELUXE,DELIMITER "%",recordend "\n",maxerrors 20,rejectfile "/tmp/ext_byte.log");To fix the error remove the formatting macro r completely or change the CREATE EXTERNAL TABLE statement to:若要修复此错误，请完全删除格式化宏 r 或将 CREATE EXTERNAL TABLE 语句更改为：CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 BLOB)USING(DATAFILES("DISK:/tmp/ext_byte.dat.%r(1..2);BLOBDIR=/tmp/blobdir1.%r(1..2)"),DELUXE,DELIMITER "%",recordend "\n",maxerrors 20,rejectfile "/tmp/ext_byte.log");-26388 Cannot use r macro in CLOBDIR %s without having a matching macro in filename %s.

Could not use the formatting macro r in CLOBDIR string without having a corresponding r macro in the DISK filename. The following is an example of when this error is returned:如果磁盘文件名中没有相应的 r 宏，则无法使用 CLOBDIR 字符串中的格式化宏 r 。

以下是返回此错误的示例：CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 CLOB)USING(DATAFILES("DISK:/tmp/ext_byte.dat;CLOBDIR=/tmp/clobdir1.%r(1..2)"),DELUXE,DELIMITER "%",recordend "\n",maxerrors 20,rejectfile "/tmp/ext_byte.log");To fix the error remove the formatting macro r completely or change the CREATE EXTERNAL TABLE statement to:若要修复此错误，请完全删除格式化宏 r 或将 CREATE EXTERNAL TABLE 语句更改为：CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 CLOB)USING(DATAFILES("DISK:/tmp/ext_byte.dat.%r(1..2);CLOBDIR=/tmp/clobdir1.%r(1..2)"),DELUXE,DELIMITER "%",recordend "\n",maxerrors 20,rejectfile "/tmp/ext_byte.log");-26389 Range for r macro in BLOBDIR %s does not match range in filename %s.

The r macro range in the BLOBDIR string and filename in the DISK string must match exactly.

The following is an example of when this error is returned:BLOBDIR 字符串中的 r 宏范围和 DISK 字符串中的文件名必须完全匹配。

以下是返回此错误的示例：CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 BLOB)USING(DATAFILES("DISK:/tmp/ext_byte.dat.%r(1..2);BLOBDIR=/tmp/blobdir1.%r(10..20)"),DELUXE,DELIMITER "%",recordend "\n",maxerrors 20,rejectfile "/tmp/ext_byte.log");To fix the error change the CREATE EXTERNAL TABLE statement to:若要修复此错误，请将 CREATE EXTERNAL TABLE 语句更改为：CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 BLOB)USING(DATAFILES("DISK:/tmp/ext_byte.dat.%r(1..2);BLOBDIR=/tmp/blobdir1.%r(1..2)"),DELUXE,DELIMITER "%",recordend "\n",maxerrors 20,rejectfile "/tmp/ext_byte.log");-26390 Range for r macro in CLOBDIR %s does not match range in filename %s.

The r macro range in the CLOBDIR string and the file name in the DISK string must match exactly.

The following is an example of when this error is returned:CLOBDIR 字符串中的 r 宏范围和 DISK 字符串中的文件名必须完全匹配。

以下是返回此错误的示例：CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 CLOB)USING(DATAFILES("DISK:/tmp/ext_byte.dat.%r(1..2);CLOBDIR=/tmp/clobdir1.%r(10..20)"),DELUXE,DELIMITER "%",recordend "\n",maxerrors 20,rejectfile "/tmp/ext_byte.log");To fix the error change the CREATE EXTERNAL TABLE statement to:若要修复此错误，请将 CREATE EXTERNAL TABLE 语句更改为：CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 CLOB)USING(DATAFILES("DISK:/tmp/ext_byte.dat.%r(1..2);CLOBDIR=/tmp/clobdir1.%r(1..2)"),DELUXE,DELIMITER "%",recordend "\n",maxerrors 20,rejectfile "/tmp/ext_byte.log");-26391 FORMAT (%s) is not supported with collection types.

The FORMAT type specified is not supported with collection types.

Use DELIMITED or FIXED FORMAT when specifying collection data types.

集合类型不支持指定的 FORMAT 类型。指定集合数据类型时，请使用 DELIMITED或 FIXED FORMAT。

-26392 The INSERT operation into an external table failed because a row size exceeds the maximum limit of %s.

During an unload to an external table, the row size exceeded the maximum limit for external tables.

在卸载到外部表期间，行大小超出了外部表的最大限制。

ACTION操作Collection data types or variable length user-defined types in the table can cause the row sizeto exceed the external table limit. Large object columns are not included in the row size.Use another method to unload and load the table, such as the High-Performance Loader,the UNLOAD and LOAD statements in the DB-Access utility, or the onunload and onload utilities.

表中的集合数据类型或可变长度的用户定义类型可能导致行大小超过外部表限制。行大小中不包括大对象列使用另一种方法来卸载和加载表，例如高性能加载程序，DB-Access 实用程序中的 UNLOAD 和 LOAD 语句，或 onunload 和 onload 实用程序。

-26431 [Internal] Extended type is not valid.

If you cannot find a direct cause for this internal error, note all circumstances and contact GBase Technical Support.

如果找不到此内部错误的直接原因，请记录所有情况并联系 GBase 技术支持。

-26600 Exceeded limit on maximum number of concurrent open databases.

The query is requesting too many concurrent open databases. The query is likely to have nested routine calls or cascading trigger actions. Reduce the nested routine calls or the cascading trigger actions and retry the query.

该查询请求太多并发打开的数据库。查询可能具有嵌套的例程调用或级联触发器操作。

减少嵌套例程调用或级联触发器操作，然后重试查询。

-26601 Cannot define a partial-column index on the non-character column, column-name.

You can specify a substring size in the CREATE INDEX statement only for columns of character data types, such as CHAR, LVARCHAR, NCHAR, NVARCHAR,or VARCHAR.

For the specified column, the index key must be the entire column value.

可以在 CREATE INDEX 语句中仅为字符数据类型的列指定子字符串大小，例如 CHAR、LVARCHAR、NCHAR、NVARCHAR 或 VARCHAR。对于指定的列，索引键必须是整个列值。

Remove the substring size value that follows the column name and rerun the statement.

删除列名后面的子字符串大小值，然后重新运行该语句。

-26736 The statement failed because the escape character is not a constant of type CHARACTER.

When you use the LIKE or MATCHES operator, the character in the ESCAPE clause must be a constant of type CHARACTER.

使用 LIKE 或 MATCHES 运算符时，ESCAPE 子句中的字符必须是 CHARACTER 类型的常量。

-43026 The new chunk path does not exist. User interaction failed while prompting user for input to continue further.

-43027 The new chunk path does not exist. User chose to discontinue the rename chunk operation when prompted for input.

-43028 The new chunk path does not exist. User chose to continue the rename chunk operation without creating the chunk path when prompted for input.

-43063 The IFX_SERVERNUM environment variable is set to . Using this value to get logical logs from storage manager for imported restore.

-43064 The IFX_SERVERNUM environment variable is set to an invalid value of .

Using value specified by SERVERNUM parameter in the ONCONFIG file to get logical logs from storage manager for imported restore.

使用由 NCONFIG 文件中的 SERVERNUM 参数指定值，以从存储管理器获取导入还原的逻辑日志。

The IFX_SERVERNUM environment variable set for imported restore is invalid.

为导入的还原设置的 IFX_SERVERNUM 环境变量无效。

ACTION Set the IFX_SERVERNUM environment variable to a valid value.

将 IFX_SERVERNUM 环境变量设置为有效值。

-43065 If doing an imported restore, and if the value of SERVERNUM parameter in ONCONFIG file of the current database server is different from that of the source database server, try setting IFX_SERVERNUM environment variable to the source SERVERNUM value prior to re-starting log restore.

The value of SERVERNUM parameter in ONCONFIG file of the current database server may be different from that of the source database server.

当前数据库服务器的 ONCONFIG 文件中 SERVERNUM 参数的值可能与源数据库服务器的值不同。

ACTION Try setting IFX_SERVERNUM environment variable to the same value as that of the value of SERVERNUM parameter in ONCONFIG file of the source database server prior to re-starting log restore.

在重新启动日志还原之前，尝试将 IFX_SERVERNUM 环境变量设置为与源数据库服务器的 ONCONFIG 文件中的 SERVERNUM 参数值相同的值。

-43195 ERROR: Logical Logs will not be backed up / salvaged because LTAPEDEV value is . Normal backup (onbar -b) cannot be done without logical logs being backed up, because restore of such backups requires a logical log restore.

If the LTAPEDEV parameter value in your ONCONFIG file is /dev/null (UNIX)or NUL (NT) or blank, logical log backup is not performed. These are special values that the user sets to tell the server and ON-Bar that log backups are not desired. Data in the logical log cannot be restored.

Normal backups (that are not whole system backups) cannot be restored without logical log restore. Therefore such backups are not possible without logical logs being backed up.

如果 ONCONFIG 文件中的 LTAPEDEV 参数值为 /dev/null（UNIX）或 NUL（NT）或为空，则不执行逻辑日志备份。它们是用户设置的特殊值，用于告知服务器和 ON-Bar 不需要日志备份。无法恢复逻辑日志中的数据。如果逻辑日志没有还原，则无法恢复正常备份不是整个系统备份）。因此，如果不备份逻辑日志，则无法进行此类备份。

ACTION Set the LTAPEDEV parameter value to something other than /dev/null (UNIX)or NUL (NT) or blank if logical log backups are desired. Or use whole system backup (onbar -b -w) and whole system physical-only restore(onbar -r -w -p) which can be performed without logical logs being backed up / restored.

如果需要逻辑日志备份，请将 LTAPEDEV 参数值设置为 /dev/null（UNIX）或 NUL（NT）以外的值或为空。或者使用整个系统备份（onbar -b -w）和整个系统物理还原（onbar-r -w -p），它们可以在不备份/恢复逻辑日志的情况下执行。

-43196 ERROR: Logical Logs cannot be restored because LTAPEDEV value is .

Restoring a normal backup (done by onbar -b) is not possible without restore of logical logs. Only whole system backups (done with onbar -b -w) can be restored without logical logs as whole system physical-only restore(using onbar -r -w -p). Then use onmode commands (options -s or -m) to bring server up without logical log restore.

如果不还原逻辑日志，则无法恢复正常备份（由 onbar -b 完成）。只有整个系统物理恢复（使用 onbar -r -w -p），才能恢复整个系统备份（使用 onbar -b -w 完成）而无需逻辑日志。然后使用 onmode 命令（选项 -s 或 -m ）使服务器启动而不进行逻辑日志恢复。

If the LTAPEDEV parameter value in your ONCONFIG file is /dev/null (UNIX)or NUL (NT) or blank, logical log restore cannot be performed. These are special values that the user sets to tell the server and ON-Bar that log backup and restore is not desired. Data in the logical log cannot be restored.

如果 ONCONFIG 文件中的 LTAPEDEV 参数值为 /dev/null（UNIX）或 NUL（NT）或为空，则无法执行逻辑日志还原。这些是用户设置的特殊值，用于告知服务器和 ON-Bar 不需要日志备份和还原。无法还原逻辑日志中的数据。

ACTION Set the LTAPEDEV parameter value to something other than /dev/null (UNIX)or NUL (NT) or blank if logical log backup and restore is desired.

Only whole system backups (done with onbar -b -w) can be restored without logical logs as whole system physical-only restore (using onbar -r -w -p).

如果需要逻辑日志备份和还原，请将 LTAPEDEV 参数值设置为 /dev/null（UNIX）或 NUL（NT）以外的值或为空。只有整个系统物理恢复（使用 onbar -r -w -p），才能恢复整个系统备份（使用 onbar -b -w 完成）而无需逻辑日志。

-43197 Duplicate log unique ID found for specified point-in-log restore.

Gbackuprestore is restoring to the latest log unique ID .

Gbackuprestore found more than one of the specified point-in-log log unique IDs.

This situation can occur due to multiple timelines. Gbackuprestore will restore to the latest timeline.

Gbackuprestore 发现了多个指定的日志记录日志唯一 ID。由于多个时间线，可能会出现这种情况。

Gbackuprestore 将恢复到最新的时间线。

ACTION Gbackuprestore will restore to the latest timeline. Please use point-in-time restore to restore to other timelines.

Gbackuprestore 将恢复到最新的时间线。请使用时间点恢复来恢复到其他时间线。

-43250 The child process for the backup and restore filter is terminating with exit code .

This is an ON-Bar status message. The Child process used during the backup and restore filter operation is exiting.

这是一个 ON-Bar 状态消息。在备份和还原过滤器操作期间使用的子进程正在退出。

ACTION None无-43298 Warning: BSA version is .

This version does not match with the version(s) specified in <sm_versions>.

The version of XBSA shared library could not be identified in sm_versions file.

无法在 sm_versions 文件中标识 XBSA 共享库的版本。

ACTION Look at the contents of the sm_versions file in $GBS_HOME/etc or%GBS_HOME%\etc. Make sure the data match the version of your storage manager, and confirm that this version of the storage manager has been certified with this version of ON-Bar.

查看 $GBS_HOME/etc 或 %GBS_HOME%\etc 中的 sm_versions 文件的内容。

确保数据与存储管理器的版本匹配，并确认此版本的存储管理器已通过此版本的 ON-Bar 认证。

-43299 Error identifying storage manager in XBSA shared library or sm_versions file.

No storage manager could be identified in XBSA shared library or sm_versions file.

在 XBSA 共享库或 sm_versions 文件中无法识别存储管理器。

查看 $GBS_HOME/etc 或 %GBS_HOME%\etc 中的 sm_versions 文件的内容。

确保数据与存储管理器的版本匹配，并确认此版本的存储管理器已通过此版本的 ON-Bar 认证。

-43301 Filter terminated.

This is an ON-Bar status message. The backup and restore filter process created by ON-Bar has terminated.

这是一个 ON-Bar 状态消息。ON-Bar 创建的备份和恢复过滤器进程已终止。

ACTION None无-43302 Using filter .

This is an ON-Bar status message. ON-Bar is using this filter program for backup or restore.

这是一个 ON-Bar 状态消息。ON-Bar 正在使用此过滤器程序进行备份或还原。

ACTION None无-43311 Some backups that can be expired were not successfully expired at the Storage Manager.

Onsmsync requested the Storage Manager to expire a backup that is no longer needed, but the expiration request did not complete successfully.

Onsmsync 请求 Storage Manager 使不再需要的备份到期，但是到期请求未成功完成。

ACTION Examine Storage Manager logs and ON-Bar activity log for details.

检查 Storage Manager 日志和 ON-Bar 活动日志以获取详细信息。

-43317 The feature requires GBase 8s Primary Storage Manager (GBase 8s PSM).

Onsmsync can not complete the request because the Storage Manager does not support it.

Onsmsync 无法完成请求，因为 Storage Manager 不支持。

ACTION To enable this feature, configure ON-Bar to use GBase 8s Primary Storage Manager (GBase 8s PSM) as its storage manager.

要启用此功能，请将 ON-Bar 配置为使用 GBase 8s Primary Storage Manager（GBase 8s PSM）作为其存储管理器。

-43335 Too many onbar command line arguments, maximum allowed: This error occurs during read command line arguments.

在读取命令行参数期间发生此错误。

ACTION Limit the number of command line arguments to the maximum allowed value.

将命令行参数的数量限制为允许的最大值。

-43334 (-43334) ERROR: Invalid copy ids received from Storage Manager.

The copy ID that the storage manager returned is inconsistent with the return code存储管理器返回的副本 ID 与返回代码不一致。

ACTION Check with the vendor of the Storage Manager.

请与 Storage Manager 的供应商联系。

-43336 (-43336) Logical Logs cannot be backed-up because the database server is dismissing the logical logs.

If the database server was started with an ONCONFIG file containing the LTAPEDEV parameter with a value of '/dev/null' (UNIX), 'NUL', (Windows) or blank,logical log back up cannot be performed. These special values indicate that log backups are not desired. Data in this logical log cannot be restored in the future. Only whole-system backups are allowed.

如果数据库服务器是使用包含值为 '/dev/null' (UNIX)、'NUL'(Windows)、或空白的 LTAPEDEV 参数的 ONCONFIG 文件启动的，则无法执行逻辑日志备份。这些特殊值表示不需要日志备份。此逻辑日志中的数据将来无法恢复。仅允许整个系统备份。

ACTION If logical log restores are desired, then set the LTAPEDEV configuration parameter value to something other than '/dev/null' (UNIX), 'NUL' (Windows)or blank.

如果需要逻辑日志还原，那么将 LTAPEDEV 配置参数值设置为 ‘/dev/null’(UNIX)、‘nul’(Windows) 或空白以外的其他值。

-43338 (-43338) Non whole-system backups are not allowed if the database server is dismissing logical logs.

Non whole-system backups need logical logs to be restored to bring the database server to a consinstent state. If logs cannot be backed up, non whole-system backups are not allowed.

非全系统备份需要还原逻辑日志，以使数据库服务器处于一致状态。

如果无法备份日志，则不允许进行非全系统备份。

ACTION Set the LTAPEDEV parameter value in the ONCONFIG file to something other than'/dev/null' (UNIX), 'NUL' (Windows), or blank and restart the database server.

将 ONCONFIG 配置文件中 LTAPEDEV 配置参数值设置为 ‘/dev/null’(UNIX)、‘nul’(Windows)或空白以外的其他值，并重新启动数据库服务器。

-43341 (-43341) Logical log is needed by this restore but cannot be found in (null).

After physical restore of a dbspace, a minimum set of logs can be required to maintain the logical consistency of the database server.

在物理还原 dbspace 后，可能需要较小的日志集来维护数据库服务器的逻辑一致性。

ACTION If this is a whole-system restore, the logical restore part will be disabled so the DBA can find the logs (if needed) and perform a logical restore (-r -l).

如果这是一个完全系统还原，则将禁用逻辑还原部分，以便 DBA 可以找到日志（如果需要）并执行逻辑还原（-r -l）。

If this is a non whole-system restore, the restore cannot proceed until the missing log are found.

如果这是非完全系统还原，则在找到丢失的日志之前无法继续还原。

-43342 (-43342) Cannot read reserved pages from rootdbs object.

The ON-Bar process tried to extract the reserved pages from a rootdbs backup but was unsuccessful.

ON-Bar 进程试图从 rootdbs 备份中提取保留页面但是不成功。

ACTION Call GBase Support.

联系 GBase 支持。

-43343 (-43343) No suitable root dbspace backup was found.

The ON-Bar boot file (ixbar) does not contain a backup for the rootdbs that can be restored with the selected options.

ON-Bar boot 文件（ixbar）不包含可以使用所选选项还原的 rootdbs 的备份。

ACTION If you received this message after running the onbar -r -w command, check if your last backup was a whole backup performed with the onbar -b -w command. You can only do a whole restore on a whole backup. If your last backup was not a whole backup,use the onbar -r command to perform the restore. If your last backup was a whole restore, the ixbar file might be inconsistent. Contact GBase Support.

如果在运行 onbar -r -w 命令后收到此消息，请检查上次备份是否是使用 onbar -b -w 命令执行的整库备份。您只能对整库备份执行整库还原。如果上次备份不是整库备份，请使用 onbar -r 命令执行还原。如果您的上次备份是整库还原，则 ixbar 文件可能不一致。联系 GBase 支持。

If you received this message after running the onbar -r command, the ixbar file might be inconsistent. Contact GBase Support.

如果在运行 onbar -r 命令后收到此消息，则 ixbar 文件可能不一致。联系 GBase 支持。

-43344 (-43344) The rootdbs level 0 restore is not restartable in recovery mode.

Shutdown the server and do a cold restore.

The rootdbs level 0 restore must be a cold restore.

rootdbs 0 级别还原必须是冷还原。

ACTION Shutdown the server and do a cold restore.

关闭服务器并执行冷恢复。

-43353 WARNING: Logical logs will not be backed up as part of this operation.

Make sure that logical logs are backed up separately.

The ON-Bar settings switched off implicit log backup after a dbspace backup.

在 dbspace 备份后，ON-Bar 设置关闭了隐式日志备份。

ACTION Make sure that logs are backed up with a separate ON-Bar command.

确保使用单独的 ON-Bar 命令备份日志。

-43354 WARNING: Logical logs were not backed up as part of this operation.

Logs through log unique ID %1 are needed for restoring this backup.

Make sure these logs are backed up separately.

还原此备份需要记录日志唯一 ID %1。确保单独备份这些日志。

The ON-Bar settings switched off implicit log backup after a dbspace backup.

在 dbspace 备份后，ON-Bar 设置关闭了隐式日志备份。

ACTION Make sure that logs are backed up with a separate ON-Bar command.

确保使用单独的 ON-Bar 命令备份日志。

-43355 ERROR: Logical logs are full and must be backed up before dbspace backup without log backup is possible.

The ON-Bar settings switched off implicit log backup.

ON-Bar 设置关闭了隐式日志备份。

ACTION Backup the logs with a separate ON-Bar command.

使用单独的 ON-Bar 命令备份日志。

-43372 Failed to add selected row to linked list for %1.

Attempt to add the selected row to the linked list failed.

尝试将所选行添加到链接列表失败。

ACTION Stop ON-Bar and retry your command.

停止 ON-Bar 并重试您的命令。

If the error persists, please note all circumstances, save a copy of the ON-Bar and ONLine message logs and contact GBase Technical Support。

如果错误仍然存在，请记录所有情况，保存 ON-Bar 和 ONLine 消息日志的副本，并联系 GBase 技术支持。

-43374 %1 for %2 exceeds it's maximum allowed length of %3 characters.

SQL statement is longer than it's maximum allowed size.

SQL 语句超出了其允许的最大长度。

ACTION Shorten the statement or divide it into multiple statements.

缩减该语句，或将它分成多个语句。

-43375 ERROR: Attempt to build an SQL where clause for %1 failed.

No data was passed to the build-where-clause function, so no SQL where clause can be built.

没有数据传递给 build-where-clause 函数，因此不能构建 SQL where 子句。

ACTION Make sure that bar_object and bar_server tables in sysutils database has data in it.

确保 sysutils 数据库中的 bar_object 和 bar_server 表中包含数据。

-43377 %1 required to insert a row into %2.0 An SQL insert into this table can't happen without the specified data.

没有指定的数据，不能在此表中插入 SQL。

ACTION Stop ON-Bar and retry your command.

停止 ON-Bar 并重试命令。

If the error persists, please note all circumstances, save a copy of the ON-Bar and ONLine message logs and contact GBase Technical Support.

如果错误仍然存在，请记录所有情况，保存 ON-Bar 和 ONLine 消息日志的副本，并通过联系 GBase 技术支持。

-43378 Missing data for %1.

Required data is missing.

缺少必需的数据。

ACTION Stop ON-Bar and retry your command.

停止 ON-Bar 并重试命令。

If the error persists, please note all circumstances, save a copy of the ON-Bar and ONLine message logs and contact GBase Technical Support.

如果错误仍然存在，请记录所有情况，保存 ON-Bar 和 ONLine 消息日志的副本，并通过联系 GBase 技术支持。

-43379 Updates to primary key are not allowed.

Updating a table's primary key is not allowed.

不允许更新表的主键。

ACTION First, delete the row and then attempt to insert a new row with the new primary key.

首先，删除该行，然后尝试使用新主键插入新行。

-43383 Unable to update timestamp to for action number None无ACTION Ask your database administrator to repair the data.

请数据库管理员修复数据。

-43384 Creating %1 to allow restore %2 missing chunks缺少 chunk ACTION Creating missing chunks创建所需的 chunk。

-43386 Storage space was not backed up so it cannot be restored/verified.

None无ACTION None无-43387 Unable to determine if is a dbspace or dbslice: %2 An error occurred while trying to convert a dbslice to its list of dbspaces. Most likely there is a typographical error or a coserver failed to respond.

尝试将 dbslice 转换为其 dbspace 列表时发生错误。很可能是排版错误或协同服务器无法响应。

ACTION Verify that all coservers are in the correct state (on-line or quiescent for a backup or warm restore and micro-kernel for cold restore).

验证所有协同服务器是否处于正确状态（联机或热恢复的联机或静态以及微内核的冷恢复状态）。

-43396 Logstream does not exist.

ACTION Verify the logstream exists in this database server.

验证日志流在数据库服务器中存在。

-43397 Storage space does not exist.

ACTION Verify the storage space exists in this database server and retry the backup or restore.

验证此数据库服务器中是否存在存储空间，然后重试备份或还原。

-83336 The warm restore failed because the dbspace number <dbspace_number> is full.

A warm restore operation requires space in a temporary dbspace to write the temporary logical logs to be restored. The specified dbspace is now full and the warm restore cannot continue.

热恢复操作需要临时 dbspace 中的空间来写入要恢复的临时逻辑日志。指定的 dbspace 已满，并且热恢复无法继续。

ACTION Free space in the dbspace or specify another dbspace and restart the restore.

释放 dbspace 中的可用空间或指定另一个 dbspace 并重新启动还原。

-26097 Operation is not valid on a secondary server.

The above operation is not valid on the secondary server.

Attempt such operations only on the primary node in the HDR pair or cluster.

上述操作在辅助服务器上无效。仅在 HDR 对或群集中的主节点上尝试此类操作。

-43083 System call stat() or fstat() failed on file , error number .

An operating system error prevented information from being returned for the specified the file.

操作系统错误导致无法为指定的文件返回信息。

ACTION Correct the error and retry your command.

更正错误并重试命令。

-43084 Error while writing data to file .

An error occurred while writing to the file. The file system might be running out of space.

写入文件时发生错误。文件系统可能空间不足。

ACTION Contact GBase Software support.

联系 GBase 软件支持。

-83380 An archive checkpoint could not be completed in the secondary server.

An archive checkpoint was attempted on a secondary server but we failed. Possible causes include the LOG_STAGING_DIR configuration parameter not being set, or not receiving a checkpoint from the primary server within the time interval specified by the BAR_CKPSEC_TIMEOUT configuration parameter在辅助服务器上尝试了归档检查点，但是失败了。可能的原因包括没有设置 LOG_STAGING_DIR 配置参数，或者未在 BAR_CKPSEC_TIMEOUT 配置参数指定的时间间隔内从主服务器接收检查点。

ACTION Check the online message log for more information and correct the problem.

If the checkpoint timed out you can increase the value of the BAR_CKPTSEC_TIMEOUT configuration parameter.

检查联机消息日志以获取更多信息并更正问题。如果检查点超时，则可以增加BAR_CKPTSEC_TIMEOUT 配置参数的值。

-83353 Attempt to reopen a parallel whole system backup failed with return code ..

This is an internal error.

这是一个内部错误。

ACTION Retry the parallel whole system backup. If it fails again, contact GBase Software Support.

重试并行整个系统备份。如果再次失败，请与 GBase 软件支持联系。

-43141 The edition of GBase 8s Dynamic Server currently running restricts the number of parallel backup or restore processes to Resetting BAR_MAX_BACKUP to .

将 BAR_MAX_BACKUP 重置为 Some editions of GBase 8s Dynamic Server limit the number of parallel backup or restore processes and this limit has been exceeded.

某些版本的 GBase 8s Dynamic Server会限制并行备份或还原过程的数量，并且已超出此限制。

ACTION The BAR_MAX_BACKUP configuration parameter has been dynamically reset to the maximum number processes that are allowed for this edition.

BAR_MAX_BACKUP 配置参数已动态重置为此版本允许的最大数量进程。

-83974 This edition of GBase 8s Dynamic Server supports only nodes in a cluster. Stopping connection attempt.

Some editions of GBase 8s Dynamic Server limit the number of nodes in a cluster.

某些版本的 GBase 8s Dynamic Server 限制了群集中的节点数。

ACTION Keep the number of nodes under the allowed value.

Ensure that the number of nodes in the cluster does not exceed the maximum number of nodes supported by the edition.

将节点数保持在允许的值下。确保群集中的节点数不超过版本支持的最大节点数。

-83975 This edition of GBase 8s Dynamic Server does not support nodes in a cluster. Stopping connection attempt.

Some editions of GBase 8s Dynamic Server limit the type of secondary nodes that can be added to the cluster.

某些版本的 GBase 8s Dynamic Server 限制了可以添加到群集的辅助节点的类型。

ACTION Avoid adding non-allowed node types to the cluster.

避免将非允许的节点类型添加到群集。

-26401 Cannot connect to accelerator server.

Connecting to the accelerator server failed.

Possible reason can be:- The accelerator server is not running.

The connectivity information (a group entry in the sqlhosts file with the name of the accelerator) is outdated or invalid.
The database contains stale meta information (AQTs) of data marts that no longer exist.

连接到加速器服务器失败。

可能的原因可能是：- 加速器服务器未运行。

连接信息（sqlhosts 文件中的加速器名称的组条目）已过期或无效。
数据库包含不再存在的数据集市的陈旧元信息（AQT）。

ACTION Check if the accelerator server is operational.

Log on to the computer as either user root or as user gbasedbt, and then run this command: ondwa status检查加速器服务器是否正常运行。以 root 用户或用户 gbasedbt 身份登录计算机，然后运行以下命令：ondwa status Check the sqlhosts file to find the group entry with the name of the accelerator. If the entry is considered correct, it is possible that the authentication token is outdated. It may be necessary to renew the entry by removing the accelerator and setting up the initial connection anew, as described in the manual. If the accelerator is shared with another GBase 8s server instance (e.g. in a HA environment), it may be necessary to get an up-to-date copy of the sqlhosts entry from one of the sharing GBase 8s server instances.

检查 sqlhosts 文件以查找具有加速器名称的组条目。如果该条目被认为是正确的，则认证令牌可能已过时。如手册中所述，可能需要通过移除加速器并重新设置初始连接来更新条目。如果加速器与另一个 GBase 8s 服务器实例共享（例如在 HA 环境中），则可能需要从共享 GBase 8s 服务器获取 sqlhosts 条目的最新副本实例。

The meta information for data marts (AQTs) are special views in the system catalog table systables of a database, with a name beginning with "aqt".

After removing data marts when connected to a different database, or after setting up the accelerator server from scratch, it is possible that stale AQTs are left over. Stale AQTs should be removed manually using the"DROP VIEW ..." command.

数据集市（AQT）的元信息是数据库的系统目录表 systables 中的特殊视图，名称以"aqt"开头。

在连接到不同数据库时删除数据集市后，或者在从头开始设置加速器服务器之后，可能会遗留过时的 AQT。应使用"DROP VIEW ..."命令手动删除旧的 AQT。

-26402 The dynamic SQL operation failed to run on the accelerator server.

The dynamic SQL operation failed on the accelerator server during the PREPARE, OPEN, FETCH, or CLOSE phase.

在 PREPARE、OPEN、FETCH 或 CLOSE 阶段，加速器服务器上的动态 SQL 操作失败。

ACTION Note all the circumstances including the complete error message and contact GBase Software Support.

请注意所有情况，包括完整的错误消息，并与 GBase 软件支持联系。

-26403 An SQDWA error occurred.

The query cannot be accelerated due to an internal error that was detected in the SQDWA component.

由于在 SQDWA 组件中检测到内部错误，无法加速查询。

ACTION Note all the circumstances including the complete error message and contact GBase Software Support.

请注意所有情况，包括完整的错误消息并联系 GBase 软件支持。

-26404 The query cannot be accelerated. Fallback to running the query on the database server is disabled.

Is is not possible to accelerate the query and the query cannot be sent to the database server for processing.

无法加速查询，也无法将查询发送到数据库服务器进行处理。

ACTION To enable the query to run on the database server, run the following statement and then run the query again: set environment use_dwa 'fallback on'要使查询在数据库服务器上运行，请运行以下语句，然后再次运行查询：set environment use_dwa 'fallback on'-26406 Opening multiple cursors to an accelerator server is not allowed.

Opening multiple cursors to an accelerator server from a single session is not allowed.

不允许从单个会话向加速器服务器打开多个游标。

ACTION Close the previous cursor before opening a new cursor to the same accelerator server.

在将新光标打开到同一个加速器服务器之前关闭上一个光标。

-26407 Changing the data type for the host variables is not allowed in an accelerated query.

Changing the data type of host variables is not allowed during query acceleration.

在查询加速期间，不允许更改主机变量的数据类型。

ACTION Prepare the SQL statement again using the new host variables, and then run the query again.

使用新的主机变量再次准备 SQL 语句，然后再次运行查询。

-26408 Arithmetic operation resulted in an overflow The value is too large, and an overflow has occurred.

该值太大，发生溢出。

ACTION You either sent an arithmetic expression in an SQL statement or prepared statement to a database server, or a database server returned an arithmetic expression. This expression caused an overflow. Change the arithmetic expression so that it does not cause an overflow.

要么将 SQL 语句中的算术表达式或预处理语句发送到数据库服务器，要么数据库服务器返回算术表达式。这个表达式引起了溢出。更改算术表达式，以便它不会导致溢出。

-21528 Defragment: The partition does not require defragmentation.

ACTION No action required.

不需任何操作。

-21529 Defragment: Could not find a large enough extent to cover 2 or more extents.

ACTION Add another chunk to the dbspace or delete some partitions to create more free space.

将另一个 chunk 添加到 dbspace 或删除一些分区以创建更多可用空间。

-21530 Defragment: Defragmentation is not supported on secondary servers.

ACTION Defragment on the primary server. Changes will be replicated to the secondary servers.

主服务器上的分片整理。更改将复制到辅助服务器。

-21531 Defragment: A partition that contains a partition header page table cannot be defragmented.

ACTION Do not attempt to run the defragmenter on the partition header page table - this is not allowed.

不要试图在分区标题页表上运行分片整理程序-这是不允许的。

-21532 Defragment: The partition is in the wrong state or an incompatible type ACTION If a conflicting action is occurring on the partition, run defragmentation later. Otherwise the partition is a type that cannot be defragmented. See the GBase 8s Data Server Administrator's Reference for information on defragmentation restrictions.

如果分区上发生冲突操作，请稍后运行分片整理。否则，分区是无法进行分片整理。

有关分片整理限制的信息，请参阅《GBase 8s 数据服务器管理员参考》。

-21533 Defragment: A defragmentation task is already in progress on this dbspace.

ACTION Run one defragmentation task on a dbspace at a time.

在 dbspace 上一次运行一个分片整理任务。

-21534 Defragment: Internal error - cannot map the logical page number.

ACTION Contact GBase Software Support.

联系 GBase 软件支持。

-21535 Defragment: Internal error - cannot free the old chunk extent.

ACTION Contact GBase Software Support.

联系 GBase 软件支持。

-21536 Defragment: Internal error - cannot have two destination extents.

ACTION Contact GBase Software Support.

联系 GBase 软件支持。

-21537 Defragment: This command cannot be run while a defragmentation is in progress.

ACTION Rerun the command after defragmentation is complete.

分片整理完成后重新运行命令。

-21539 Defragment: You can't run this command on catalog/pseudo/temp tables ACTION Run defragment on a regular table/partition在常规表/分区上运行分片整理。

-21541 The total amount of storage space for the list of dbspaces, blobspaces, and sbspaces exceeds the TENANT_LIMIT_SPACE property setting for the tenant database.

ACTION To resolve the discrepancy between the total size of the current storage spaces and the configured storage limit, you can take at least one of these actions:1. Increase the value of the TENANT_LIMIT_SPACE property,2. or change the list of storage spaces,3. or reduce the size of one or more of the storage spaces.

要解决当前存储空间的总大小与配置的存储限制之间的差异，可以至少执行以下操作之一：1.增加 TENANT_LIMIT_SPACE 属性的值，2.或更改存储空间列表，3.或减小一个或多个存储空间的大小。

-21551 Tenant PIT Restore Generic Error ACTION This is a Tenant PIT Restore Generic Error.

这是租户PIT恢复通用错误。

-26451 STATCHANGE can take values in the range of 0 to 100.

ACTION STATCHANGE specifies a percentage of how much a table distribution can change before it is considered stale. Set STATCHANGE to an integer value in the range from 0 to 100.

STATCHANGE 指定表分布在被视为过时之前可以更改的百分比。将 STATCHANGE 设置为 0 到 100 之间的整数值。

-26452 You cannot specify the STATLEVEL as FRAGMENT for non-fragmented tables.

ACTION You can set the STATLEVEL attribute to the FRAGMENT option only for fragmented tables. Specify the TABLE or AUTO options for non-fragmented tables.

只能为分片表将 STATLEVEL 属性设置为 FRAGMENT 选项。为非分片表指定 TABLE 或AUTO 选项。

-26454 Cannot specify both a PRIMARY KEY constraint and a NULL constraint for the same column.

The database server issues this error when the CREATE TABLE or ALTER TABLE statement attempts to define a table schema that includes a column definition with contradictory specifications regarding NULL values.

The PRIMARY KEY constraint prevents the database server from storing NULL values in this column.
The NULL constraint allows the database server store NULL values in this column.

当 CREATE TABLE 或 ALTER TABLE 语句试图定义表架构时，数据库服务器会发出此错误。语句尝试定义一个表模式，该表模式包含具有关于 NULL 值的矛盾规范的列定义。

PRIMARY KEY 约束阻止数据库服务器在此列中存储 NULL 值。
NULL 约束允许数据库服务器在此列中存储 NULL 值。

To avoid this error, revise the column definition so that it does not include both PRIMARY KEY and NULL specifications on the same column.

If you want this column to be the primary key of this table, you must drop the NULL specification in the column definition.
If you want to allow NULL values in this column, you must drop the PRIMARY KEY specification in the column definition.

要避免此错误，请修改列定义，使其在同一列上不包含 PRIMARY KEY 和 NULL 规范。

如果希望此列成为此表的主键，则必须在列定义中删除 NULL 规范。
如果要在此列中允许NULL值，则必须在列定义中删除 PRIMARY KEY 规范。

-26455 Cannot specify both a NOT NULL constraint and a NULL constraint for the same column.

The NOT NULL constraint prevents the database server from storing NULL values in this column.
The NULL constraint allows the database server store NULL values in this column.

当 CREATE TABLE 或 ALTER TABLE 语句尝试定义包含具有关于 NULL 值的矛盾规范的列定义的表模式时，数据库服务器会发出此错误。

NOT NULL 约束阻止数据库服务器在此列中存储 NULL 值。
NULL 约束允许数据库服务器在此列中存储 NULL 值。

To avoid this error, revise the column definition so that it does not include both NOT NULL and NULL specifications on the same column.

If you want to prohibit NULL values in this column, you must drop the NULL specification in the column definition.
If you want to allow NULL values in this column, you must drop the NOT NULL specification in the column definition.

要避免此错误，请修改列定义，使其在同一列上不包含 NOT NULL 和 NULL 规范。

如果要禁止此列中的 NULL 值，则必须在列定义中删除 NULL 规范。
如果要在此列中允许 NULL 值，则必须在列定义中删除 NOT NULL 规范。

-26456 The authorization ID %s is not defined for the trusted context.

Authorization name attempted to reuse a trusted connection using trusted context. The trusted context name can not be used under the The switch user failed.

授权名称尝试使用可信上下文重用可信连接。无法在下使用可信上下文名称。交换机用户失败。

This error can also occur for one of the following reasons:出于以下原因之一，也可能发生此错误：- The authorization ID is allowed to use the trusted context, but authentication is required and the request to switch users did not include the authentication token允许授权标识使用互信上下文，但需要进行身份验证，并且切换用户的请求不包括身份验证令牌- The authorization ID is allowed to use the trusted context, but the trusted context is disabled允许授权标识使用互信上下文，但禁用互信上下文- The system authorization ID attribute of the trusted context object associated with the trusted connection has been changed已更改与互信连接关联的互信上下文对象的系统授权标识属性- The trusted context object associated with the trusted connection has been dropped已删除与互信连接关联的互信上下文对象The attempt to reuse the trusted connection fails. The trusted connection is in an unconnected state.

尝试重用互信连接失败。互信连接处于未连接状态。

-26457 The trusted context already exists.

The context name is already defined in the database. For CREATE TRUSTED CONTEXT or ALTER TRUSTED CONTEXT statement, a trusted context with the specified name already exists. Verify that you have specified the correct context name and that you are in the correct database.

已在数据库中定义上下文名称。对于 CREATE TRUSTED CONTEXT 或 ALTER TRUSTED CONTEXT语句，已存在具有指定名称的互信上下文。验证是否指定了正确的上下文名称，以及是否在正确的数据库中。

-26458 The trusted context specified authorization ID which is already specified for another trusted context.

A CREATE TRUSTED CONTEXT or ALTER TRUSTED CONTEXT statement for specified SYSTEM AUTHID , but this authorization ID is already defined to use a different trusted context. A system authorization ID that is defined as the SYSTEM AUTHID for a trusted context cannot be associated with any other trusted context as the SYSTEM AUTHID.

为指定的 SYSTEM AUTHID 创建 CREATE TRUSTED CONTEXT或 ALTER TRUSTED CONTEXT 语句，但此授权标识已定义为使用不同的互信上下文。定义为互信上下文的 SYSTEM AUTHID 的系统授权标识不能作为 SYSTEM AUTHID 与任何其他互信上下文关联。

Use the following query to determine which trusted context is already using the authorization ID:使用以下查询确定哪个互信上下文已在使用授权标识：SELECT CONTEXTNAME FROM SYSUSER.SYSTRUSTEDCONTEXT WHERE AUTHID = To correct this error change the authorization ID for the trusted context and reissue the CREATE or ALTER statement.

要更正此错误，请更改互信上下文的授权标识，然后重新发出 CREATE 或 ALTER 语句。

-26459 The trusted context does not exist.

The specified trusted context does not exist in the database.

Verify that you have specified the correct trusted context name.

数据库中不存在指定的互信上下文。验证是否指定了正确的互信上下文名称。

-26460 Attribute with value cannot be dropped or altered because it is not part of the definition of trusted context.

Attribute was specified for a trusted context, but the trusted context is not defined with an attribute with this name. The statement could not be processed.

为互信上下文指定了属性，但未使用具有此名称的属性定义互信上下文。

无法处理该语句。

To correct this error remove the name of the unsupported attribute and re-issue the statement.

要更正此错误，请删除不支持的属性的名称，然后重新发出该语句。

-26461 Attribute with value is not unique for trusted context.

During the CREATE TRUSTED CONTEXT or ALTER TRUSTED CONTEXT a duplicate value was specified for the attribute. Each pair of attribute name and value must be unique for a trusted context. The statement cannot be processed.

在 CREATE TRUSTED CONTEXT 或 ALTER TRUSTED CONTEXT 期间，为属性指定了重复值。对于互信上下文，每对属性名称和值必须是唯一的。无法处理此语句。

To correct this error remove the non-unique specification of and and re-issue the statement.

要更正此错误，请删除的非唯一规范，然后重新发出该语句。

-26462 User cannot be dropped or altered because it is not part of the definition of trusted context User was specified for a trusted context, but the trusted context is not defined with an user with this name. The statement could not be processed.

已为互信上下文指定了用户，但未使用具有此名称的用户定义互信上下文。

无法处理此语句。

To correct this error remove the name of the undefined user and re-issue the statement.

要更正此错误，请删除未定义用户的名称并重新发出该语句。

-26463 User is not unique for trusted context.

During the CREATE TRUSTED CONTEXT or ALTER TRUSTED CONTEXT a duplicate value of user was specified in the WITH USE FOR clause.

The statement cannot be processed.

在 CREATE TRUSTED CONTEXT 或 ALTER TRUSTED CONTEXT 期间，在 WITH USE FOR子句中指定了用户的重复值。无法处理此语句。

To correct this error remove the non-unique specification of user name and and re-issue the statement.

要更正此错误，请删除用户名的非唯一规范，然后重新发出该语句。

-26464 A CREATE TRUSTED CONTEXT or ALTER TRUSTED CONTEXT statement specified%s more than once or the trusted context is already defined to be used by this authorization ID or PUBLIC.

The statement specified that be allowed to use the trusted context, but the specified authorization ID or PUBLIC is already defined to use the trusted context, or the authorization ID was specified more than once in the statement. The authorization ID or PUBLIC must not already be allowed to use the trusted context, and it can only be specified once within a statement for a trusted context. The statement could not be processed.

该语句指定允许使用互信上下文，但指定的授权 ID 或 PUBLIC 已定义为使用互信上下文，或者在语句中多次指定授权 ID。不能允许授权 ID 或 PUBLIC 使用互信上下文，并且只能在互信上下文的语句中指定一次。无法处理该语句。

If the authorization ID or PUBLIC was specified more than once, remove the extra specifications of , and re-issue the statement. If an ALTER TRUSTED CONTEXT statement that contained an ADD USE FOR clause, and the trusted context already was defined for use by that authorization ID or PUBLIC, use the REPLACE USE FOR clause instead to redefine the usage characteristics for the specified users to use the trusted context.

如果多次指定授权 ID 或 PUBLIC，请删除的额外规范，然后重新发出该语句。如果包含 ADD USE FOR 子句的 ALTER TRUSTED CONTEXT 语句以及已定义可供该授权 ID 或 PUBLIC 使用的互信上下文，请使用 REPLACE USE FOR 子句重新定义指定用户的使用特性以使用该信任上下文。

-26465 An ALTER TRUSTED CONTEXT statement for specified %s but the trusted context is not currently defined to be used by this authorization ID or PUBLIC.

An ALTER TRUSTED CONTEXT statement for attempted to replace or remove the ability for to use the trusted context, but the specified authorization ID or PUBLIC is not currently defined to use the trusted context.

The statement could not be processed.

ALTER TRUSTED CONTEXT 语句，用于尝试替换或删除使用互信上下文的功能，但当前未定义指定的授权 ID 或 PUBLIC 以使用互信上下文。无法处理该语句。

If an ALTER TRUSTED CONTEXT statement that contained a REPLACE USE FOR clause,and the trusted context was not already was defined for use by that authorization ID or PUBLIC, use the ADD USE FOR clause instead to define the trusted context to be used by the specified users. If the ALTER TRUSTED CONTEXT statement contained the DROP USE FOR clause, none of the specified authorization IDs or PUBLIC were currently defined to use the trusted context.

如果包含 REPLACE USE FOR 子句的 ALTER TRUSTED CONTEXT 语句以及尚未定义互信上下文以供该授权 ID 或 PUBLIC 使用，请使用 ADD USE FOR 子句来定义指定用户要使用的互信上下文。如果 ALTER TRUSTED CONTEXT 语句包含 DROP USE FOR 子句，则当前未定义任何指定的授权 ID 或 PUBLIC 以使用互信上下文。

-26466 ENCRYPTION attribute %s cannot be specified more than once.

Specify only one ENCRYPTION attribute in a statement. Alternatively, specify one WITH ENCRYPTION attribute for each ADDRESS attribute.

在语句中仅指定一个 ENCRYPTION 属性。或者，为每个 ADDRESS 属性指定 WITH ENCRYPTION属性。

-26468 A DBSECADM users cannot create a trusted context for themselves.

The statement (CREATE TRUSTED CONTEXT or ALTER TRUSTED CONTEXT) was not processed because the specified SYSTEM AUTHID matched that of the DBSECADM user who ran the statement.

未处理语句（CREATE TRUSTED CONTEXT 或 ALTER TRUSTED CONTEXT），因为指定的SYSTEM AUTHID 与运行该语句的 DBSECADM 用户的系统匹配。

Specify a different authorization ID or run the statement as a different DBSECADM user.

指定其他授权 ID 或将语句作为不同的 DBSECADM 用户运行。

-26469 A trusted connection was not established because the trusted context is not enabled.

Ensure that the trusted context is correctly defined and enabled, and then try to establish a trusted connection.

确保正确定义并启用了互信上下文，然后尝试建立互信连接。

-26470 The database specified ('database name') is not associated with the trusted context.

Specify the correct database for the trusted context associated with the current trusted connection or establish a regular connection to the database.

为与当前可信连接关联的互信上下文指定正确的数据库，或者建立与数据库的一般连接。

-26471 Internal Function (%s): Unable to send or receive from the Session Manager.

This error indicates that the server was able to establish connection to the Session Manager but failed to send or receive data.

If you cannot find a direct cause for this internal error, note all circumstances and contact GBase Software Support.

此错误表示服务器能够建立与会话管理器的连接但无法发送或接收数据。如果找不到此内部错误的直接原因，请记录所有情况并联系 GBase 软件支持。

-26472 Internal Error occurred during a BLOB operation in function %s.

If you cannot find a direct cause for this internal error, note all circumstances and contact GBase Software Support.

如果找不到此内部错误的直接原因，请记录所有情况并与 GBase 软件支持联系。

-26473 Internal Error occurred. The required parameter %s is NULL.

If you cannot find a direct cause for this internal error, note all circumstances and contact GBase Software Support.

如果找不到此内部错误的直接原因，请记录所有情况并与 GBase 软件支持联系。

-26474 Internal Error occurred during codeset conversion in function %s.

If you cannot find a direct cause for this internal error, note all circumstances and contact GBase Software Support.

如果找不到此内部错误的直接原因，请记录所有情况并与 GBase 软件支持联系。

-26475 Function (%s): Unable to connect to the Session Manager.

This error indicates that the server is unable to connect to the Session Manager which is necessary for debugging the SPL routine. Verify that the Session Manager is running in the specified host system at the specified port number. Also make sure that the Session Manager host and the port can be accessed from the host system where the server is running.

此错误表示服务器无法连接到调试 SPL 例程所需的会话管理器。验证会话管理器是否在指定端口号的指定主机系统中运行。还要确保可以从运行服务器的主机系统访问会话管理器主机和端口。

-26476 Can not create temp table with ERKEY It is illegal to create a temp table with ERKEY使用 ERKEY 创建临时表是非法的。

-26477 Illegal usage of ERKEY Your usage of ERKEY is not legal ERKEY 的用法不合法。

-26478 Can not add ERKEY when table already has ERKEY You attempted to alter a table to include the ERKEY attribute when that table already had the ERKEY attribute.

该表已具有 ERKEY 属性时，您试图更改表以包含 ERKEY 属性。

-26479 Can not drop ERKEY when table does not have ERKEY You attempted to alter a table to drop the ERKEY when the table did not have the ERKEY attribute.

当表没有 ERKEY 属性时，试图更改表以删除 ERKEY。

-26480 Illegal usage of ifx_replcheck You attempted to use the ifx_replcheck column in an illegal manner.

试图以非法的方式使用 IFX_PLECHECK 列。

-26481 Cannot perform this operation through a grid Renaming replicated database is not supported through a grid.

Manually rename the replicated database at all grid servers outside of the grid context.

不支持通过网格重命名复制数据库。在网格上下文之外的所有网格服务器上手动重命名复制的数据库。

-26482 Cannot alter a replicated table in a grid outside of the same grid context The ALTER TABLE statement on a replicated table that was created through a grid must be executed within the same grid context and with replication enabled by setting the ER_enable argument to 1.

通过网格创建的复制表上的 ALTER TABLE 语句必须在同一网格上下文中执行，并通过将ER_enable 参数设置为 1 来启用复制。

-26483 Grid or Region is not defined A SET ENVIRONMENT GRID_SELECT command was issued using a non-existant grid or region name.

使用不存在的网格或区域名称发出了 SET ENVIRONMENT GRID_SELECT 命令。

-26484 SQL error encountered on a SET ENVIRONMENT GRID_SELECT command Examine the message log file for more detailed information.

检查消息日志文件以获取更多详细信息。

-26491 JDBC method (%s) not supported with this server.

A Java UDR invoked a method from the JDBC API that is not supported by J/Foundation in this version of the server. See the GBase 8s release notes for more information about JDBC compliance.

Java UDR 在此版本的服务器中调用了 J/Foundation 不支持的 JDBC API 方法。

有关 JDBC 合规性的更多信息，请参阅 GBase 8s 发行说明。

-26500 Query offloading is turned OFF This query was not accelerated because query offloading is turned off.

To turn on query offloading, use the following statement:SET ENVIRONMENT use_dwa '1'此查询未加速，因为关闭了查询卸载。要打开查询卸载，请使用以下语句：SET ENVIRONMENT use_dwa '1'-26501 Subquery matching is not supported This subquery was not accelerated because accelerating a subquery is not supported yet.

此子查询未加速，因为尚不支持加速子查询。

-26502 Contradictory filters in where clause will not produce any rows This query was not accelerated because the where clause have contradictory filters which will result in no rows. Hence there is no need to off-load this query to accelerator.

此查询未加速，因为 where 子句具有相互矛盾的过滤器，这将导致没有行。因此，无需将此查询卸载到加速器。

-26503 Statement is not a SELECT or SELECT INTO statement This statement was not accelerated because it is not a SELECT or INSERT INTO ... SELECT ... statement.

此语句未加速，因为它不是 SELECT 或 INSERT INTO ... SELECT ...

语句。

-26504 Query containing FOR UPDATE is unsupported for offloading This query was not accelerated, because it contains a FOR UPDATE clause.

此查询未加速，因为它包含 FOR UPDATE 子句。

-26505 Query contains a pseudo table This query was not accelerated, because it contains a pseudo table.

此查询未加速，因为它包含伪表。

-26506 Query contains a temporary table This query was not accelerated, because it contains a temporary table.

此查询未加速，因为它包含临时表。

-26507 Query contains a table which is not a real table This query was not accelerated, because it contains a table which is not a real table (e.g. view, external table, sequence, synonym).

此查询未加速，因为它包含的表不是真正的表（例如视图、外部表、序列、同义词）。

-26508 Query contains a system catalog table This query was not accelerated, because it contains a system catalog table.

此查询未加速，因为它包含系统目录表。

-26509 Query contains a table in remote database This query was not accelerated because it contains a table that does not reside in the database to which the user is connected.

此查询未加速，因为它包含的表不驻留在用户所连接的数据库中。

-26510 Cannot identify fact table This query was not accelerated because the fact table cannot be identified.

For outer joins, the fact table is the leftmost table in the query.

For inner joins, the fact table is the table containing most rows.

此查询未加速，因为无法识别事实表。

对于外连接，事实表是查询中最左侧的表。

对于内连接，事实表是包含大多数行的表。

-26511 Cannot access the AQT dictionary This query was not accelerated because an error occurred when trying to access the AQT dictionary cache.

Note all circumstances and contact GBase Software Support.

此查询未加速，因为尝试访问 AQT 字典缓存时发生错误。请注意所有情况并联系 GBase软件支持。

-26512 No data marts are defined on this database This query was not accelerated because no data marts are defined on the current database.

此查询未加速，因为当前数据库上未定义任何数据集市。

-26513 Data mart is virtual but the AVOID_EXECUTE directive is not set This query was not accelerated because the data mart it matches to is a virtual data mart. To match against virtual data marts, the AVOID_EXECUTE optimizer directive or explain setting must be set.

此查询未加速，因为它匹配的数据集市是虚拟数据集市。要与虚拟数据集市匹配，必须设置 AVOID_EXECUTE 优化器指令或说明设置。

-26514 Query contains more tables than data mart reference definitions This query was not accelerated because it contains more tables than the number of references in the data mart definitions. GBase 8s offloads only queries fully contained in a single data mart.

此查询未加速，因为它包含的表多于数据集市定义中的引用数。

GBase 8s 仅卸载完全包含在单个数据集市中的查询。

-26515 Query does not contain a fact table of any data mart This query was not accelerated because it does not contain a fact table of any data mart defined on this database.

此查询未加速，因为它不包含此数据库上定义的任何数据集市的事实表。

-26516 Query contains combination of tables not contained in any data mart This query was not accelerated because it uses a set of tables that is not contained in any data mart definition. Check the tables and references used in your data mart definitions.

此查询未加速，因为它使用了一组不包含在任何数据集市定义中的表。

检查数据集市定义中使用的表和引用。

-26520 ON clause contains a non-equality join between columns This query was not accelerated because it contains an OUTER join with a non-equality join predicate between two columns. Query acceleration is only possible on equality join predicates of two columns.

此查询未加速，因为它包含一个 OUTER 连接，两个列之间具有不相等的连接谓词。

查询加速仅适用于两列的等式连接谓词。

-26525 OUTER join with in-join filter (extends NULLs)The query was not accelerated because it contains an OUTER join with in-join filter.

The ON clause of an ANSI OUTER join query must not contain other expressions than equality joins between columns (e.g. non-equality filters or table filter).

The WHERE clause of an GBase 8s OUTER join query must not contain non-equality filters or table-level filters on subservient tables.

查询未加速，因为它包含具有 in-join 过滤器的 OUTER 连接。ANSI OUTER 连接查询的 ON 子句不能包含除列之间的等值连接之外的其他表达式（例如，非相等过滤器或表过滤器）。GBase 8s OUTER 连接查询的 WHERE 子句不得在子服务表上包含不相等的过滤器或表级过滤器。

For example, the following queries cannot be accelerated.

ANSI outer join queries :例如，以下查询无法加速。

ANSI 外连接查询：SELECT * FROM f left join d ON (f.col1 = d.col1 AND f.col2 > d.col2)SELECT * FROM f left join d ON (f.col1 = d.col1 AND f.col2 > 0)SELECT * FROM f left join d ON (f.col1 = d.col1 AND d.col2 > 0)GBase 8s outer join queries :GBase 8s 外连接查询：SELECT * FROM f outer d WHERE f.col1 = d.col1 AND f.col2 > d.col2 SELECT * FROM f outer d WHERE f.col1 = d.col1 AND d.col2 > 0-26528 OR clause contains joins between different tables This query was not accelerated because it contains an OR clause with equality join predicates that refer to more that two tables.

此查询未加速，因为它包含具有等值连接谓词的 OR 子句，该子句引用多个表。

-26529 OR clause contains joins between different columns This query was not accelerated because it contains an OR clause with equality join predicates that refer to more that two columns.

此查询没有加速，因为它包含一个 OR 子句，该子句具有相等的联接谓词，该谓词引用的列超过两列。

-26530 Query contains a full join This query was not accelerated because it contains a full OUTER join.

Full OUTER joins are not eligible for query acceleration.

此查询未加速，因为它包含完整的 OUTER 连接。

Full OUTER 连接不符合查询加速的条件。

-26532 ON clause of LEFT OUTER refers to more than two tables This query was not accelerated because it contains a LEFT OUTER join with an ON clause that refers to more than two tables.

此查询未加速，因为它包含 LEFT OUTER 连接，其中 ON 子句引用两个以上的表。

-26534 INNER join must be on first level of joins This query was not accelerated because it contains an INNER join that is not on the first level of joins. Query acceleration on INNER joins is only possible if the INNER join in on the first join level.

此查询未加速，因为它包含不在第一级联接的 INNER 连接。仅当 INNER 在第一个连接级别加入时，才能在 INNER 连接上进行查询加速。

-26536 INNER join contains a non-equality join between columns This query was not accelerated because it contains an INNER join with a non-equality join predicate between two columns. Query acceleration is only possible on equality join predicates of two columns.

此查询未加速，因为它包含一个 INNER 连接，两个列之间具有不相等的连接谓词。

查询加速仅适用于两列的等式连接谓词。

-26537 INNER join refers to more than two tables This query was not accelerated because it contains an INNER join with an ON clause that refers to more than two tables.

此查询未加速，因为它包含带有 ON 子句的 INNER 连接，该子句引用两个以上的表。

-26538 Joins do not form a star or snowflake scheme This query was not accelerated because it does not join the contained tables in a star or snowflake scheme. The number of joins must be one less than the number of tables.

此查询未加速，因为它未加入星形或雪花模式中包含的表。连接数必须比表的数量少一个。

-26540 Table cannot be fact table, it is used by query with different aliases This query was not accelerated because it contains the fact table more than once. The fact table is used by the query with different aliases.

此查询未加速，因为它不止一次包含事实表。事实表由具有不同别名的查询使用。

-26543 Query does not contain an equality join from the data mart definition and none of the columns in the equality join has a unique index This query was not accelerated because it does not contain an equality join that is present in the data mart definition, and none of the columns in the equality join has a unique index. If a reference in the data mart definition is not reflected by the corresponding equality join predicates in the query, then these equality join predicates can be omitted from the query only if at least one of the columns has defined a unique index on it. Otherwise, the accelerator does not preserve the correct number of rows.

此查询未加速，因为它不包含数据集市定义中存在的等值连接，并且等于连接中的所有列都没有唯一索引。

如果查询中的相应等值连接谓词没有反映数据集市定义中的引用，则只有在其中至少一个列已在查询上定义了唯一索引的情况下，才能从查询中省略这些相等连接谓词。否则，加速器将不保留正确的行数。

-26544 Query does not contain a table from the data mart definition and there is no unique index defined on that table This query was not accelerated because it does not contain a table that is present in the data mart definition with a reference defined on it, and there is no unique index defined on that table. If a reference in the data mart definition contains a table that is not present in the query, this table can be omitted from the query only if there is a unique index defined on it. Otherwise,the accelerator does not preserve the correct number of rows.

该查询未加速，因为它不包含数据集市定义中存在的具有定义了引用的表，而且该表上也没有定义唯一的索引。

如果数据集市定义中的引用包含查询中不存在的表，则只有在该表上定义了唯一索引的情况下，才能从查询中省略此表。否则，加速器将不保留正确的行数。

-26546 Query contains equality joins that are not present in the data mart definition This query was not accelerated because it contains equality joins that are not defined as references in the data mart definition.

此查询未加速，因为它包含未在数据集市定义中定义为引用的等值连接。

-26547 Query does not contain an equality join from the data mart definition and none of the columns in the equality join from the data mart definition have a unique index This query was not accelerated because it does not contain an equality join that is present in the data mart definition and none of the columns in the equality join of the data mart definition have a unique index. If a reference in the data mart definition is n:m, then this reference needs to be reflected by an equality join in the query.

此查询未加速，因为它不包含数据集市定义中存在的等值连接，并且数据集市定义的相等连接中的任何列都没有唯一索引。如果数据集市定义中的引用为 n:m，则此引用需要由查询中的等值连接反映。

-26552 Column is not contained in the data mart definition This query was not accelerated because it refers to a column that is not contained in the definition of the data mart.

此查询未加速，因为它引用了未包含在数据集市定义中的列。

-26555 Expression is not supported This query was not accelerated because it contains an expression that is not supported by the accelerator.

此查询未加速，因为它包含加速器不支持的表达式。

-26557 Data type is not supported This query was not probed successfully because it contains a column whose data type is not supported by the accelerator.

此查询未加速，因为它包含加速器不支持的数据类型列。

-26558 Query contains implicit column This query was not accelerated or probed successfully because it contains an implicit column. Tables contain implicit columns if they are created or altered using the following options:此查询未成功加速或检测，因为它包含隐式列。如果使用以下选项创建或更改表，则表包含隐式列：option | implicit columns -----------------+--------------------------------------

WITH CRCOLS | cdrserver, cdrtime WITH REPLCHECK | ifx_replcheck WITH VERCOLS | ifx_insert_checksum, ifx_row_version WITH ERKEY | ifx_erkey_1, ifx_erkey_2, ifx_erkey_3 WITH ROWIDS | rowid-26559 Query does not explicitly contain columns This query was not probed successfully because it does not explicitly contain columns. E.g. a query like "select count(*) from t" does not select specific columns.

未成功探测此查询，因为它未明确包含列。例如。像“select count(*) from t”这样的查询不会选择特定的列。

-26560 Cannot find synonym for table.

This query was not probed successfully because it contains a table that does not reside in the current database and no synonym is defined on this table.

此查询未成功探测，因为它包含一个不驻留在当前数据库中的表，并且未在此表上定义同义词。

-26561 Default GBase 8s sqlcode returned for not matched ISAO server sqlcode.

This query returned a error from the accelerator in drda sqlcode and drda sqlstate form. This error did not match any of the existing IDS sqlcode.

So IDS server gives this default sqlcode error.

此查询从 drda sqlcode 和 drda sqlstate 表单中的加速器返回错误。此错误与任何现有IDS sqlcode 都不匹配。所以 IDS 服务器给出了这个默认的 sqlcode 错误。

-26563 The query cannot be accelerated because the unary function with expression is not supported on the accelerator.

The query contains unary function with expressions as argument. If the data types in the expression are non-numeric types then the accelerator returns error. So such queries need to be prevented from off-loading to the accelrator.

该查询包含带表达式作为参数的一元函数。如果表达式中的数据类型是非数字类型，则加速器返回错误。

因此，需要防止此类查询卸载到加速器。

-26564 The Query containing windowed aggregates is unsupported for offloading This query was not accelerated, because it contains a windowed aggregates.

此查询未加速，因为它包含窗口化聚合。

-26565 Row type cannot be used as an OUT/INOUT parameter in a C UDR when the routine is invoked by another SPL routine.

-26700 User () was not found.

The specified user name is not registered in the database server. This error occurred when the ALTER, RENAME, or DROP statement was run. Verify the user name and then rerun the statement. It is also possible that the user was previously removed or renamed.

未在数据库服务器中注册指定的用户名。运行 ALTER、RENAME 或 DROP 语句时发生此错误。验证用户名，然后重新运行该语句。用户之前也可能被删除或重命名。

-26701 User () was not created because it already exists.

Verify the user name. If you want to create a user, specify a unique user name that is not registered in the database server. If you want to change the properties of a user account, you can use either the DROP USER or RENAME USER statement and then rerun the CREATE USER statement. You can also use the ALTER USER statement to change the properties of an existing user.

验证用户名。如果要创建用户，请指定未在数据库服务器中注册的唯一用户名。如果要更改用户账户的属性，可以使用 DROP USER 或RENAME USER 语句，然后重新运行 CREATE USER 语句。您还可以使用 ALTER USER 语句更改现有用户的属性。

-26702 User () cannot connect to the database server because the user account is locked.

To unlock the user account, run the ALTER USER statement with the ACCOUNT UNLOCK option. Only a database server administrator (DBSA) can manage user accounts.

In a non-root installation, the DBSA is the user who installed the product.

要解锁用户账户，请使用 ACCOUNT UNLOCK 选项运行 ALTER USER 语句。只有数据库服务器管理员（DBSA）才能管理用户账户。在非 root 用户安装中，DBSA 是安装产品的用户。以安装此数据库服务器的用户身份登录以修改用户账户。

-26703 User () is not authorized to create, alter, drop, or rename users.

Only a database server administrator (DBSA) can manage user accounts. In a non-root installation, the DBSA is the user who installed the product. Log in as the user who installed this database server to modify user accounts.

只有数据库服务器管理员（DBSA）才能管理用户账户。在非 root 用户安装中，DBSA 是安装产品的用户。以安装此数据库服务器的用户身份登录以修改用户账户。

-26704 User name () exceeds the maximum length.

Specify a user name that is not longer than 32 characters.

-26705 The password specified for user () is not valid.

Specify a password that contains 6 - 32 characters.

-26706 Cannot add a password to the user (%s) because a password already exists.

Use the MODIFY option instead of the ADD option.

An ALTER USER operation can only add a password for a user if that user does not have a password. If you want to change the password, use the MODIFY option in the ALTER statement.

If you want to drop the password, use the DROP option in the ALTER statement.

ALTER USER 操作只能为用户添加密码（如果该用户没有）。如果要更改密码，请使用 ALTER 语句中的 MODIFY 选项。

如果要删除密码，请使用 ALTER 语句中的 DROP 选项。

-26707 User () cannot be created because the user is not mapped to any properties.

When you create a user for a non-root installation, you must use the PROPERTIES option with the CREATE USER statement. You can exclude the PROPERTIES option in the CREATE USER statement if the user has operating-system properties on the host computer. Also, you can exclude the PROPERTIES option if default properties exist on the database server.

为非 root 用户安装创建用户时，必须将 PROPERTIES 选项与 CREATE USER 语句一起使用。

如果用户在主机上具有操作系统属性，则可以在 CREATE USER 语句中排除 PROPERTIES 选项。

此外，如果数据库服务器上存在默认属性，则可以排除 PROPERTIES选项。

-26708 Incorrect old password supplied for user ().

-26709 The new password specified for user (%s) is not valid. Specify a password that contains 6 - 32 characters.

-26710 PUBLIC is a reserved word. You cannot create, drop, alter, or rename a user with the name PUBLIC.

-26711 The default user was not found.

The default user is not registered in the database server. This error occurred when the ALTER, RENAME, or DROP statement was run. Verify the default user is registered and then rerun the statement. It is also possible that the default user was previously removed or renamed.

默认用户未在数据库服务器中注册。运行 ALTER、RENAME 或 DROP 语句时发生此错误。

验证默认用户是否已注册，然后重新运行该语句。可能是之前删除或重命名了缺省用户。

-26712 The default user was not created because it already exists.

If you want to change the properties of the default user, you can use the ALTER DEFAULT USER statement. Alternatively, you can run the DROP DEFAULT USER statement and then rerun the CREATE DEFAULT USER statement with different properties.

如果要更改缺省用户的属性，可以使用 ALTER DEFAULT USER 语句。或者，您可以运行DROP DEFAULT USER 语句，然后使用不同的属性重新运行 CREATE DEFAULT USER 语句。

-26713 Do not specify a password while creating the default user.

The default user can have properties, but it cannot have a password.

User accounts associated with the default user have the same properties.

缺省用户可以有属性，但不能有密码。与缺省用户关联的用户账户具有相同的属性。

-26714 An internal error occurred while hashing the password.

Record all circumstances prior to the error and contact GBase Software Support.

-26715 Cannot alter the user () because only one USER or UID property is allowed.

A user must have either one USER property or one UID property. The ALTER operation failed because it would not have resulted in one USER or UID property.

用户必须具有一个 USER 属性或一个 UID 属性。 ALTER 操作失败，因为它不会产生一个 USER 或 UID 属性。

-26716 Cannot alter the user to add groups because the number of groups would exceed the maximum limit (<max_groups>).

The total number of groups after the ALTER USER operation cannot exceed the maximum number of allowed groups (16).

ALTER USER 操作后的组总数不能超过允许的最大组数（16）。

-26717 An internal error occurred while performing an ALTER operation. Note all circumstances and contact GBase Software Support.

-26718 Cannot alter the user () to add a home directory because the property value already exists. Use the MODIFY option instead of the ADD option.

An ALTER USER operation can only add a home directory if no home directory exists.

If you want to modify the home directory, use the MODIFY option in the ALTER statement.

如果主目录不存在，ALTER USER 操作只能添加主目录。如果要修改主目录，请使用 ALTER 语句中的 MODIFY 选项。

-26719 The ALTER statement specified an incorrect authorization value ().

The valid values for the AUTHORIZATION option are "dbsa", "dbsso", "aao", and "bargroup".

AUTHORIZATION 选项的有效值是“dbsa”、“dbsso”、“aao”和“bargroup”。

-26720 Cannot change a property value more than once in the same ALTER statement.

In a single ALTER statement a property can only be changed once.

在单个ALTER语句中，属性只能更改一次。

-26721 Cannot drop the password for the user () because the password is specified. Do not include a value for the PASSWORD property with the DROP option.

When dropping password for the user, the password value cannot be specified.

删除用户的密码时，无法指定密码值。

-26722 The surrogate user name () exceeds the maximum length of 32 characters.

Specify a user name that has 32 characters or fewer.

-26723 The value of the surrogate property HOMEDIR exceeds the maximum length.

Specify a value that is less that 255 bytes.

-26724 Cannot drop the HOMEDIR property for the user () because a value is specified. Do not include a value for the HOMEDIR property with the DROP option.

In an ALTER USER operation to drop a specified property, a value should be supplied only when the property is GROUP or AUTHORIZATION. For all other properties, a property value cannot be specified.

在删除指定属性的 ALTER USER 操作中，仅当属性为 GROUP 或 AUTHORIZATION 时才应提供值。

对于所有其他属性，不能指定属性值。

-26725 Cannot drop the UID property for the user () because a value is specified. Do not include a value for the UID property with the DROP option.

In an ALTER USER operation to drop a specified property, a value should be supplied only when the property is GROUP or AUTHORIZATION. For all other properties, a property value cannot be specified.

在删除指定属性的 ALTER USER 操作中，仅当属性为 GROUP 或 AUTHORIZATION 时才应提供值。

对于所有其他属性，不能指定属性值。

-26726 Cannot drop the USER property for the user () because a value is specified. Do not include a value for the USER property with the DROP option.

In an ALTER USER operation to drop a specified property, a value should be supplied only when the property is GROUP or AUTHORIZATION. For all other properties, a property value cannot be specified.

在删除指定属性的 ALTER USER 操作中，仅当属性为 GROUP 或 AUTHORIZATION 时才应提供值。

对于所有其他属性，不能指定属性值。

-26727 The SQL statement cannot assign operating system properties to the user ().

The specified user account is an operating system user account and it is managed by the operating system administrator. You can use the CREATE USER and ALTER USER statements only to grant administrative database server privileges to this user account. Use the AUTHORIZATION keyword with a valid authorization property: DBSA(Database Server Administrator), DBSSO (Database System Security Officer),AAO (Audit Analysis Officer), or BARGROUP (authority to execute Gbackuprestore commands).

由操作系统管理员管理。只能使用 CREATE USER 和 ALTER USER语句向此用户账户授予管理数据库服务器权限。使用带有有效授权属性的授权关键字：DBSA(数据库服务器管理员)、DBSSO(数据库系统安全员)、AAO(审计分析员)或 BARGROUP (执行 Gbackuprestore 命令的权限)。

-26728 The uid %s is not in the /etc/gbasedbt/allowed.surrogates file or in the cache.

You must add the uid before it can be a surrogate.

在代理之前必须添加 uid。

-26729 The user %s is not in the /etc/gbasedbt/allowed.surrogates file or in the cache.

You must add the user before it can be a surrogate.

必须先添加用户才能成为代理。

-26730 The gid %s is not in the /etc/gbasedbt/allowed.surrogates file or in the cache.

You must add the gid before it can be a surrogate.

您必须添加 gid 才能成为代理程序。

-26731 The group %s is not in the /etc/gbasedbt/allowed.surrogates file or in the cache.

You must add the group before it can be a surrogate.

必须先添加该组才能成为代理。

-26732 The USERMAPPING feature is disabled. The USERMAPPING configuration parameter must be set to BASIC or ADMIN.

-26733 A gridtable can only be altered, renamed or dropped within a grid context.

You must Connect to the appropriate grid prior to issueing the alter or drop table statement.

在发出 alter 或 drop 表语句之前, 必须连接到相应的网格。

-26734 A database containing gridtables can only be droppen within a grid context You must Connect to the appropriate grid prior to dropping the database必须在发出 alter 或 drop table 语句之前连接到相应的网格。

-26735 Invalid parameter for CLUSTER_TXN_SCOPE. The only allowed values are DEFAULT, SESSION, SERVER, and CLUSTER-84221 Server name () already exists with a different definition in the source's SQLHOSTS file.

The server name specified as target for the snapshot copy operation already exists in the SQLHOST file of the source server and it points to a different TCP/IP port and/or machine.

指定为快照复制操作的目标的服务器名称已存在于源服务器的 SQLHOST 文件中，并且它指向不同的 TCP/IP 端口和/或计算机。

Fix the SQLHOSTS files and retry the operation.

修复 SQLHOST 文件并重试此操作。

-84502 XA transactions are not supported on read-only secondary servers An XA transaction was run on a read-only secondary server.

ACTION Modify your application to prevent the xa start() function from running on a read-only secondary server. Or, make the secondary server updatable using the UPDATABLE_SECONDARY configuration parameter.

修改应用程序以防止 xa start() 函数在只读辅助服务器上运行。或者，使用UPDATABLE_SECONDARY 配置参数使辅助服务器可更新。

-26801 Cannot reference an external database that is not case sensitive.

This statement refers to a database other than the current database.

However, the current database is a case sensitive database, and the external one is not. This action is not supported, because the databases that are used in a single distributed transaction either must all be case sensitive, or else must all be case insensitive.

此语句引用当前数据库以外的数据库。但是，当前数据库是区分大小写的数据库，而外部数据库不是。

不支持此操作，因为在单个分布式事务中使用的数据库必须都区分大小写，否则必须都不区分大小写。

-26802 Cannot reference an external database that is case sensitive.

This statement refers to a database other than the current database.

However, the current database is a case insensitive database, and the external one is not. This action is not supported, because the databases that are used in a single distributed transaction must all be case sensitive, or else must all be case insensitive.

此语句引用当前数据库以外的数据库。但是，当前数据库是不区分大小写的数据库，而外部数据库不是。

不支持此操作，因为在单个分布式事务中使用的数据库必须都区分大小写，否则必须全都区分大小写。

-33488 The options specified require a C++ compiler, but one could not be found.

The options passed to the ESQL/C compiler require that the application be linked with a C++ compiler. Ensure that a C++ compiler is installed on your system and that the PATH environment variable contains the location of your C++ compiler.

传递给 ESQL/C 编译器的选项要求应用程序与 C++ 编译器链接。确保在系统上安装了 C++ 编译器，并且 PATH 环境变量包含 C ++ 编译器的位置。

-33489 The GL_USEGLU environment variable setting requires a C++ compiler,but one could not be found.

The GL_USEGLU environment variable setting requires that the application be linked with a C++ compiler. Ensure that a C++ compiler is installed on your system and that the PATH environment variable contains the location of your C++ compiler.

If ICU support is not required by your program, unset the variable.

GL_USEGLU 环境变量设置要求应用程序与 C ++ 编译器链接。确保系统上安装了 C ++ 编译器，并且 PATH 环境变量包含 C ++ 编译器的位置如果程序不需要 ICU 支持，请取消设置变量。

-26901 An alias cannot represent another alias.

The statement failed because the alias definition specified that the alias represented another alias instead of a real table name.

A table can have multiple aliases, but an alias cannot have an alias.

Rerun the statement with a real table name before the AS keyword in the alias definition.

该语句失败，因为别名定义指定别名表示另一个别名而不是实际表名。表可以有多个别名，但别名不能有别名。

在别名定义中的AS关键字之前，使用实际表名重新运行该语句。

-26902 [Internal] Client decimal buffer size mismatch A client application has sent the incorrect buffer size for a field that has a decimal or numeric data type. This can lead to a loss of precision or the truncation of digits of the decimal value.

客户端应用程序为具有十进制或数字数据类型的字段发送了错误的缓冲区大小。

这可能导致精度损失或截断十进制数字的位数。

ACTION If you are using GBase 8s JDBC driver versions 3.50.JC8, 3.70.JC2, or earlier, upgrade to the latest version of the GBase 8s JDBC driver.

如果您使用的是V3.50.JC8,3.70.JC2 或更早版本的 GBase 8s JDBC 驱动程序，请升级到最新版本的 GBase 8s JDBC 驱动程序。

If you want to ignore this error, set the database server environment variable IFMX_TEMP_CQ00225490 to 1 and restart the database server.

如果要忽略此错误，请将数据库服务器环境变量 IFMX_TEMP_CQ00225490 设置为 1 并重新启动数据库服务器。

-26903 Multiple execution of a CREATE TABLE statement that was prepared once is not allowed.

A CREATE TABLE statement that was prepared only one time cannot be executed multiple times.

只能准备一次的 CREATE TABL E语句不能多次执行。

ACTION Either set the AUTO_REPREPARE configuration parameter to 1 in the onconfig file or include the FREE statement after the PREPARE CREATE TABLE and EXECUTE statements.

在 onconfig 文件中将 AUTO_REPREPARE 配置参数设置为 1，或者在 PREPARE CREATE TABLE 和 EXECUTE 语句之后包含 FREE 语句。

-26904 Attached, non-vanilla or interval fragmented compressed indexes are not supported.

Compressed indexes must be detached indexes but not interval fragmented or non-vanilla.

压缩索引必须是分离索引，但不能是间隔分片或非分片。

-26905 The procedure was not created because its definition has more than 341 parameters The maximum number of parameters in a procedure definition is 341. Reduce the number of parameters to 341 or fewer and retry the CREATE PROCEDURE statement.

过程定义中的最大参数数为 341。将参数数量减少到 341 或更少，然后重试 CREATE PROCEDURE 语句。

-26907 Routine creation failed because a collection variable was defined as a global variable.

A variable that is based on a collection data type cannot be declared as a global variable.

基于集合数据类型的变量不能声明为全局变量。

-26950 Clustered compressed indexes are not supported.

Compressed indexes must be non-clustered indexes. After you create a clustered index, you can compress it using an SQL admin API command.

压缩索引必须是非聚簇索引。创建聚簇索引后，可以使用 SQL admin API 命令对其进行压缩。

-26951 The grid query failed to run. Contact GBase Software Support.

-26952 The statement failed because the grid query contained a server name.

Server names are not valid when a GRID clause is used. Remove any reference to a specific server from the query and run the statement again.

使用 GRID 子句时，服务器名称无效。从查询中删除对特定服务器的任何引用，然后再次运行该语句。

-26953 The statement failed because the grid or region does not exist.

The specifid grid or region is not defined. Include an existing grid or region name in the GRID clause and run the statement again.

未定义特定网格或区域。在 GRID 子句中包含现有网格或区域名称，然后再次运行该语句。

-26954 The statement failed because the grid query contained a UNION or UNION ALL operator.

Statements that include the GRID clause cannot contain the UNION or UNION ALL operators.

Remove the UNION and UNION ALL operators from the query and run the statement again.

包含 GRID 子句的语句不能包含 UNION 或 UNION ALL 运算符。从查询中删除 UNION 和 UNION ALL 运算符，然后再次运行该语句。

-26955 The statement failed because of an invalid value for the SET ENVIRONMANT GRID_NODE_SKIP statement The valid values for the GRID_NODE_SKIP option are DEFALULT, 'on', or 'off'.

Run the statement again with one of the valid values.

GRID_NODE_SKIP 选项的有效值为 DEFALULT、'on' 或 'off'。

使用其中一个有效值再次运行该语句。

-26956 Cannot run the SET ENVIRONMENT SELECT_GRID or SELECT_GRID_ALL statement.

There was not enough memory to execute the command.

没有足够的内存来执行命令。

-26957 The statement failed because the grid query cannot connect to a server.

One of the servers in the grid is not currently available. Wait until the server is available, or run the SET ENVIRONMENT GRID_NODE_SKIP 'on'statement and then run the statement again.

网格中的一个服务器当前不可用。等到服务器可用，或运行 SET ENVIRONMENT GRID_NODE_SKIP 'on' 语句，然后再次运行该语句。

-26958 The statement failed because the grid query contained one or more subqueries.

Satatements that include the GRID clause cannot contain subqueries.

Remove all subqueries from the query and run the statement again.

包含 GRID 子句的语句不能包含子查询。从查询中删除所有子查询并再次运行该语句。

-26959 The statement failed because the syntax for the grid query is incorrect.

Fix the grid query syntax and run the statement again.

修复网格查询语法并再次运行该语句。

-26960 The statement failed because the grid query contained a table that is not a grid table.

Make the table available for a grid query by running the cdr change gridtable command or by using OAT. Then run the statement again.

通过运行 cdr change gridtable 命令或使用 OAT 使表可用于网格查询。然后再次运行该语句。

-26961 The statement failed because a table in the grid query is in the process of being altered.

A table that is being altered cannot be included in a grid query until the alter operation has propagated to all nodes in the grid.

在 alter 操作传播到网格中的所有节点之前，不能将正在更改的表包含在网格查询中。

-26962 The statement failed because the grid query contained coorelated joins.

包含 GRID 子句的语句不能包含相关联接。从查询中删除所有相关联接，然后再次运行该语句。

-26963 The statement failed because the grid or region has no members.

Specify a different grid or region in the GRID clause, or add members to the grid or region, and then run the statement again.

在 GRID 子句中指定不同的网格或区域，或将成员添加到网格或区域，然后再次运行该语句。

-26964 Cannot connect to a shard node.

A SELECT statement was made to a sharded table but the server containing one of the shards is currently unavailable.

对切分表执行了 SELECT 语句，但包含其中一个分片的服务器当前不可用。

-26965 Sharded query failed because it does not contain a sharded table.

The remote query path generated by optimizer must contain sharded table.

Contact GBase Software Support.

优化程序生成的远程查询路径必须包含分片表。联系 GBase 软件支持。

-26966 Sharded query included unsupported extended data types.

The query contains one or more SQL data types that are not supported in sharded queries.

该查询包含分片查询不支持的一种或多种 SQL 数据类型。

-26967 A connection to a shard node could not be established Examine which node was not available and then retry the query.

Verify the SHARD_ID and node names are all unique.

检查哪个节点不可用，然后重试查询。验证 SHARD_ID，节点名称都是唯一的。

-26968 A connection to a shard node was lost Correct the reason for the lost of the network connection and then retry the query. Verify that all the shard nodes are online.

更正丢失网络连接的原因，然后重试查询。验证所有分片节点是否在线。

-26969 Parallel Sharded Queries Not active Parallel Sharded Queries is not active on the local server.

本地服务器上的并行共享查询不处于活动状态。

-26970 Parallel Sharded Queries not available on shard node Parallel Sharded Queries does not exist on a shard node.

Verify the SHARD_ID is valid and unique.

分片节点上不存在并行分片查询。验证 SHARD_ID 是否有效且唯一。

-26971 Sharding connection Connect Error.

The shard cluster could not connect to one of the remote shard servers.

分片群集无法连接到其中一个远程分片服务器。

-26972 Sharding Internal Error.

Parallel Sharded Queries encountered an internal error. Contact GBase Software Support.

并行共享查询遇到内部错误。联系 GBase 软件支持。

-26973 Triggers are not supported in sharded queries.

The query includes triggers or trigger body statements that are not supported in sharded queries.

查询包括分片查询中不支持的触发器或触发器主体语句。

-26974 Sharded tables are not supported inside procedure or function.

You cannot include a sharded table in a procedure or function.

不能在过程或函数中包含分片表。

-26975 Cannot include a FOR UPDATE clause in a SELECT statement on a sharded table.

A SELECT statement that operates on a sharded table cannot contain a FOR UPDATE clause.

在分片表上运行的 SELECT 语句不能包含FOR UPDATE 子句。

Edit the SELECT statement or the cursor declared and remove this clause.

编辑 SELECT 语句或声明的游标并删除此子句。

-26976 The statement failed because it attempted to move rows between shard servers.

The statement contains an update to a shard key that requires the row to move to another shard server. This type of update is not allowed.

该语句包含对分片键的更新，该分片键需要将行移动到另一个分片服务器。不允许此类更新。

To update the shard key of a row, delete the row and then insert it with the new values.

若要更新行的分片键，请删除该行，然后使用新值插入该行。

-26977 Sharded queries are not supported within an XA environment.

Sharded queries are not supported within an XA environment.

XA 环境中不支持共享查询。

-26991 The query failed because the FROM clause includes more than one sharded table.

A SELECT statement cannot include more than one sharded table in the FROM clause.

SELECT 语句不能在FROM子句中包含多个分片表。

-26992 The sharded query failed because of an internal error.

The query on a sharded table encountered an internal error. If this error recurs, note all circumstances and contact GBase Software Support.

分片表上的查询遇到内部错误。如果再次出现此错误，请记录所有情况并联系 GBase 软件支持。

-26993 Cannot alter the table to shard collection table.

Collection table can only be altered to shard collection table.

集合表只能更改为分片集合表。

-32519 Passwords are only allowed in SET SESSION AUTHORIZATION statements for a trusted connection using a trusted context.

A SET SESSION AUTHORIZATION statement with a password, was executed outside of a trusted connection.

在可信连接的中间执行带有密码的 SET SESSION AUTHORIZATION 语句、-88001 C-ISAM function returned error .

The C-ISAM processor returned an error.

C-ISAM 处理器返回错误。

Check the C-ISAM error code and correct the situation.

检查 C-ISAM 错误代码并更正情况。

-88002 Memory allocation error.

An attempt to allocate memory from the system failed.

尝试从系统分配内存失败。

Release some memory and retry the operation.

释放一些内存并重试该操作。

-88003 Cannot create a file or directory at .

GBase 8s PSM attempted to create a file or directory but the attempt failed.

GBase 8s PSM 尝试重命名文件或目录，但尝试失败。

Check the associated operating system error and correct the situation.

检查相关的操作系统错误并更正情况。

-88004 Cannot rename a file or directory to .

GBase 8s PSM attempted to rename a file or directory but the attempt failed.

GBase 8s 尝试重命名文件或目录，但尝试失败。

Check the associated operating system error and correct the situation.

检查相关的操作系统错误并更正情况。

-88006 An unspecified error occurred,A generic, unexpected error happened.

发生了一般性的意外错误。

Check additional errors and the configuration and contact GBase Support if the problem persist.

检查其他错误和配置，如果问题仍然存在，请类型 GBase 支持。

-88008 The specified path is not a directory or does not exists.

GBase 8s PSM Attempted to open a directory that does not exist.

GBase 8s PSM 尝试打开不存在的目录。

Correct the situation and attempt to run the command again.

纠正这种情况并尝试再次运行该命令。

-88014 When creating a new device, a device type is needed.

When creating a new device, a device type is needed.

创建新设备时，需要设备类型.

Provide a device type (either FILE or TAPE) and retry the operation.

提供设备类型（FILE 或 TAPE）并重试该操作。

-88015 A block size must be specified for device type %s.

The specified device type requires a block size.

指定的设备类型需要 block 大小。

Provide a block size and retry the operation.

提供 blcok 大小并重试该操作。

-88016 An empty pool was provided.

A valid pool name is needed for the operation.

操作需要有效的池名称。

Provide a valid pool name and retry the operation.

提供有效的池名称并重试该操作。

-88017 Invalid pool specified The specified pool is not known.

不知道指定的池。

Provide a valid value for the pool.

请为该池提供一个有效值。

-88018 Invalid device type specified.

The specified type of device is not known.

指定的设备类型未知。

Provide a valid value for the device type.

请为该设备类型提供一个有效值。

-88019 Invalid block size for device .

The block size specified for the device is not correct.

为设备指定的 block 大小不正确。

Fix the block size and retry the operation.

修复 block 大小并重试该操作。

-88020 nvalid media size for device .

The media size specified for the device is not correct.

为设备指定的介质尺寸不正确。

Fix the media size and retry the operation.

修复介质尺寸并重试操作。

-88021 Cannot update the device because it is in use.

NONE无NONE无-88022 Error -88022: Cannot delete the device because it is in use.

GBase 8s PSM Failed to delete the named device because it is in use.

GBase 8s PSM 无法删除指定的设备，因为它正在使用中。

Wait until the device is idle and retry the operation.

等到设备空闲并重试操作。

-88023 Error -88023: Cannot open the device definition file .

Attempt to open a GBase 8s PSM device definition file failed.

尝试打开 GBase 8s PSM 设备定义文件失败。

Check the associated operating system error code.

检查关联的操作系统错误代码。

-88035 No Device is available to mount in pool .

The storage manager was asked to mount a volume for a specified pool, but no device was found.

要求存储管理器为指定的池装入卷，但未找到任何设备。

Be sure that a device has been created for the specified pool.

Also be sure that the devices for the given pool are available.

确保已为指定的池创建了设备。还要确保给定池的设备可用。

-88056 The device requested in the operation () does not exist.

You tried to perform an operation on a device that does not exist.

For example you tried to delete a device that does not exist.

您试图在不存在的设备上执行操作。例如，尝试删除不存在的设备。

Resubmit the command with the correct device or pool.

使用正确的设备或池重新提交命令。

-88057 The specified device does not belong to the specified pool.

Either the device or the pool is incorrect设备或池不正确Correct the device or pool provided.

更正提供的设备或池。

-88058 The specified device cannot be deleted.

An error prevented the storage manager from deleting the specified device.

错误导致存储管理器无法删除指定的设备。

Check the accompanying error and fix the situation.

检查随附的错误并修复情况。

-88101 Cannot create catalog tables Check the GBase 8s PSM catalog directory pointed by the GBase 8s PSM_CATALOG configuration parameter ($GBS_HOME/etc/psm by default) for access permissions.

Check the associated operating system and or C-ISAM errors and correct the situation.

检查 GBase 8s PSM_CATALOG 配置参数（缺省情况下为 $GBS_HOME/etc/psm）指向的GBase 8s PSM 目录以获取访问权限。检查相关的操作系统和/或 C-ISAM 错误并更正情况。

-88102 GBase 8s PSM catalog creation failed at .

GBase 8s PSM attempted to create the GBase 8s PSM catalog tables in the specified directory, but failed.

GBase 8s PSM 尝试在指定目录中创建 GBase 8s PSM 目录表，但失败了。

Check associated error messages and resolve the issues.

Check the value of the GBase 8s PSM_CATALOG configuration parameter or environment variable for the catalog location.

检查相关的错误消息并解决问题。检查 GBase 8s PSM_CATALOG 配置参数或目录位置的环境变量的值。

-88103 Error -88103: Cannot open catalog table .

An attempt to open a catalog table failed with either an C-ISAM error number or an operating system error number.

尝试打开目录表失败，出现 C-ISAM 错误号或操作系统错误号。

Check the accompanying error numbers and correct the situation before trying the command again.

在再次尝试命令之前，请检查随附的错误编号并更正情况。

-88104 Error -88104: Cannot close catalog table descriptor for table .

An attempt to close a catalog table failed with either an C-ISAM error number or an operating system error number.

尝试关闭目录表失败，出现 C-ISAM 错误号或操作系统错误号。

Check the accompanying error numbers and correct the situation before trying the command again.

在再次尝试命令之前，请检查随附的错误编号并更正情况。

-88105 Error -88105: Cannot lock catalog table .

An attempt to lock a catalog table failed with either an C-ISAM error number or an operating system error number.

One reason for this error is that the lock timeout set for GBase 8s PSM is either too short or not long enough.

尝试锁定目录表失败，出现 C-ISAM 错误号或操作系统错误号。此错误的一个原因是GBase 8s PSM 的锁定超时设置太短或不够长。

Check the accompanying error numbers and correct the situation before trying the command again.

Try to make the configuration parameter GBase 8s PSM_TIMEOUT longer if the associated C-ISAM error is ELOCKED or EFLOCKED.

在再次尝试命令之前，请检查随附的错误编号并更正情况。如果关联的 C-ISAM 错误是 ELOCKED 或 EFLOCKED，请尝试使配置参数 GBase 8s PSM_TIMEOUT 更长。

-88106 Error -88106: Cannot build a new index for catalog table .

The storage manager attempted to build an index for the specified catalog table, but encountered an error.

存储管理器尝试为指定的目录表构建索引，但遇到错误。

Check the associated operating system and or C-ISAM errors and correct the situation.

检查相关的操作系统和/或 C-ISAM 错误并更正情况。

-88107 Error -88107: Cannot insert record into catalog table .

The storage manager attempted to insert one or more records to the specified catalog table, but encountered an error.

存储管理器尝试为指定的目录表构建索引，但遇到错误。

Check the associated operating system and or C-ISAM errors and correct the situation.

检查相关的操作系统和/或 C-ISAM 错误并更正情况。

-88108 Error -88108: Cannot delete records from catalog table .

The storage manager attempted to delete one or more records from the specified catalog table, but encountered an error.

存储管理器尝试将一个或多个记录插入指定的目录表，但遇到错误。

Check the associated operating system and or C-ISAM errors and correct the situation.

检查相关的操作系统和/或 C-ISAM 错误并更正情况。

-88109 Cannot update to catalog table .

The storage manager attempted to update one or more records in the specified catalog table, but encountered an error.

存储管理器尝试更新指定目录表中的一个或多个记录，但遇到错误。

Check the associated operating system and or C-ISAM errors and correct the situation.

检查相关的操作系统和/或 C-ISAM 错误并更正情况。

-88110 Cannot read from catalog table .

The storage manager attempted to read one or more records in the specified catalog table but encountered an error.

存储管理器尝试从指定的目录表中读取一个或多个记录，但遇到错误。

Check the associated operating system and or C-ISAM errors and correct the situation.

检查相关的操作系统和/或 C-ISAM 错误并更正情况。

-88111 Cannot get index information for catalog table .

GBase 8s PSM attempted to obtain index information for a table, but failed.

GBase 8s PSM 尝试获取表的索引信息，但失败了。

Check the associated operating system and or C-ISAM errors and correct the situation.

检查相关的操作系统和/或 C-ISAM 错误并更正情况。

-88112 Cannot demote the 'HIGHEST' priority device in the pool .

GBase 8s PSM attempted to demote the device identified as having the HIGHEST priority in the pool to priority 'HIGH', but an error was returned.

GBase 8s PSM 尝试将标识为池中具有最高优先级(HIGHEST)的设备降级为优先级“HIGH”，但返回了错误。

Check the associated operating system and or C-ISAM errors and correct the situation.

检查相关的操作系统和/或 C-ISAM 错误并更正情况。

-88113 Catalog table

is not present.

An attempt to open a catalog table failed because the table is missing.

尝试打开目录表失败，因为缺少表。

Check the accompanying error numbers and correct the situation before trying the command again.

在再次尝试命令之前，请检查随附的错误编号并更正情况。

-88114 The GBase 8s PSM catalog is missing The GBase 8s PSM catalog is not present in the specified directory指定的目录中不存在 GBase 8s PSM。

GBase 8s PSM will try to create the catalog.

GBase 8s PSM 会尝试创建目录。

-88115 The GBase 8s PSM catalog is corrupted.

The GBase 8s PSM catalog is corupted. Either there are missing tables, or the existing tables are damaged.

GBase 8s PSM 目录已被破坏。缺少表，或现有表已损坏。

Manaully inspect that there are no missing tables in the GBase 8s PSM_CATALOG_PATH directory.Run 'onGbasedbt PSM -C check' command. If this does not solve the issue,import the catalog back.

手动检查 GBase 8s PSM_CATALOG_PATH 目录中是否有丢失的表。运行 'onGbasedbt PSM -C check' 命令。

如果这不能解决问题，请重新导入目录。

-88116 The Catalog import operation was aborted.

Multiple problems can cause this problem including an already existing catalog.

多个问题可能导致此问题，包括一个已经存在的目录。

Check Associated errors, correct the sittuation and re-run the operation.

请检查关联错误，更正情况并重新运行此操作。

-88117 Attempt to load table

failed.

GBase 8s PSM attempted to load a catalog table but encontered an error.

GBase 8s PSM 尝试加载目录表但是输入了错误。

Check associatted errors.

检查相关的错误。

-88118 Attempt to erase table

failed.

GBase 8s PSM attempted to erase a catalog table but encontered an error.

GBase 8s PSM 试图擦除目录表但是出现了错误。

Check associatted errors.

检查相关的错误。

-88119 The import file has incorrect number of columns in line .

The unload file being used to load a catalog table has an incorrect number of columns.

用于加载目录表的卸载文件的列数不正确。

Check the file for corruption and fix it or use another load file.

检查文件是否损坏并修复它或使用其他加载文件。

-88130 Error -88130: GBase 8s PSM initialization failed.

The storage manager attempted to obtain index information for a table, but failed.

存储管理器尝试获取表的索引信息，但失败了。

Check the associated operating system and or C-ISAM errors and correct the situation.

检查相关的操作系统和/或 C-ISAM 错误并更正情况。

-88131 Error -88131: The environment variable 'GBS_HOME' is not set.

The storage manager attempted to obtain index information for a table, but failed.

存储管理器尝试获取表的索引信息，但失败了。

Check the associated operating system and or C-ISAM errors and correct the situation.

检查相关的操作系统和/或 C-ISAM 错误并更正情况。

-88132 Error -88132: An attempt to allocate memory to store the value of the 'GBS_HOME'environment variable failed.

The value of the environment variable might be invalid or corrupted.

Your system might be extremely low in memory.

环境变量的值可能无效或已损坏。您的系统内存可能非常低。

Check the value of the 'GBS_HOME' environment variable.

Check that your system is not low in memory.

检查'GBS_HOME'环境变量的值。检查您的系统内存是否不足。

-88133 Error -88133: An attempt to allocate memory to store the value of the 'ONCONFIG'environment variable failed.

The value of the environment variable might be invalid or corrupted.

Your system might be extremely low in memory.

环境变量的值可能无效或已损坏。您的系统内存可能非常低。

Check the value of the 'ONCONFIG' environment variable.

Check that your system is not low in memory.

检查'ONCONFIG'环境变量的值。检查您的系统内存是否不足。

-88134 Error -88134: An attempt to allocate memory to store the value of the 'PSMCONFIG'environment variable failed.

The value of the environment variable might be invalid or corrupted.

Your system might be extremely low in memory.

环境变量的值可能无效或已损坏。您的系统内存可能非常低。

Check the value of the 'PSMCONFIG' environment variable.

Check that your system is not low in memory.

检查'PSMCONFIG'环境变量的值。检查您的系统内存是否不足。

-88150 Warning -88150: The BAR_BSALIB_PATH configuration parameter is not set.

The BAR_BSALIB_PATH parameter is not set in the onconfig file. Therefore ON-Bar and allutilities related to it are using the default path that changes from system to system.This can lead to problems identifying the location of the library to use.

未在 onconfig 文件中设置 BAR_BSALIB_PATH 参数。因此，ON-Bar 和与其相关的所有实用程序都使用从系统更改为系统的默认路径。这可能导致识别要使用的库的位置时出现问题。

You must set the BAR_BSALIB_PATH configuration parameter to specify the XBSA library to be used by ON-Bar and related utilities. You must set this explicitly in the onconfig file.

必须设置 BAR_BSALIB_PATH 配置参数以指定 ON-Bar 和相关实用程序要使用的 XBSA 库。

您必须在 onconfig 文件中明确设置它。

-88151 Warning -88151: The XBSA shared library at cannot be loaded.

The XBSA library at the specified location cannot be loaded.

无法加载指定位置的 XBSA 库。

Check the accompanying system error and correct the situation.

检查随附的系统错误并更正情况。

-88152 Error -88152: The XBSA shared library at does not seem to be for the GBase 8s Primary Storage Manager.

The XBSA library at the specified location is not the for the Primary Storage Manager.

指定位置的 XBSA 库不是主存储管理器。

Check the BAR_BSALIB_PATH configuration parameter and the default location of the ON-Bar shared library in your system.

检查 BAR_BSALIB_PATH 配置参数以及系统中 ON-Bar 共享库的默认位置。

-88160 The converted string cannot be for in an INT4 integer.

We are trying to convert a string to INT4 but the value is too big.

我们正在尝试将字符串转换为 INT4，但值太大。

Correct the values and retry the operation.

请更正值并重试操作。

-88161 The length for the string is too big to fit in bytes.

The value that we want to assign to a string exceeds the size of the string variable.

要分配给字符串的值超过字符串变量的大小。

Correct the values and retry the operation in the correct format.

请更正值并以正确的格式重试操作。

-88162 The system cannot insert the specified device in the GBase 8s PSM catalog.

The device specified in the operation or command could not be inserted into the GBase 8s PSM catalog.

无法将操作或命令中指定的设备插入 GBase 8s PSM 目录中。

Check the associated errors for more information related to this problem.

检查相关错误以获取与此问题相关的更多信息。

-88163 The pool specified is invalid.

The pool specified is not valid.

指定的池无效。

Recheck the information that you need and then specify valid values for pools.

重新检查所需的信息，然后为池指定有效值。

-88164 The device type specified is invalid.

The device type specified is not valid.

指定的设备类型无效。

Review device-type information and specify a valid value for the device type.

查看设备类型信息并指定设备类型的有效值。

-88165 The device path is longer than bytes.

The device path specified is too long.

指定的设备路径太长。

Specify a valid value for the full path of the device.

为设备的完整路径指定有效值。

-88166 The priority specified for the device is invalid.

The priority specified for the device is invalid.

为设备指定的优先级无效。

Specify a valid value for the priority of the device.

指定设备优先级的有效值。

-88167 The device specification file has a syntax error at line .

Incorrect syntax in the device specification file.

设备规范文件中的语法不正确。

The offending part of the syntax has been ignored.

Correct the syntax and run the command again.

语法的违规部分已被忽略。更正语法并再次运行该命令。

-88168 Loading devices from the device specification file failed.

The operator attempted to create a set of devices from a device specification file, but the operation failed.

操作员尝试从设备规范文件创建一组设备，但操作失败。

Check the accompanying messages and correct the situation.

检查随附的消息并更正情况。

-88180 Existing in the catalog is different from .

The GBase 8s PSM catalog was created with a different version of the Primary Storage Manager, so processing cannot continue.

GBase 8s PSM 目录是使用不同版本的主存储管理器创建的，因此无法继续处理。

Recreate the catalog with the current GBase 8s PSM release.

使用当前版本的 GBase 8s PSM 重新创建目录。

-88181 Devices of type are not supported in this platform.

Some device types are not supported in all platforms. For example, in the Windows operating system, tape devices are not supported.

并非所有平台都支持某些设备类型。例如，在 Windows 操作系统中，不支持磁带设备。

Refer to the product documentation and use a supported type of device.

请参阅产品文档并使用支持的设备类型。

-88182 The XBSA Resource Type is unknown.

The XBSA Resource Type that was specified is unknown to the system.

指定的 XBSA 资源类型对系统是未知的。

Refer to the product documentation and use a supported XBSA Resource Type.

请参阅产品文档并使用受支持的 XBSA 资源类型。

-88183 Cannot Acquire a next sequential ID for the object.

GBase 8s PSM tried to generate a serial number to insert a new record in a table but an error happened GBase 8s PSM 尝试生成序列号以在表中插入新记录但发生错误Retry the action and contact GBase Support if the problem persist.

如果问题仍然存在，请重试该操作并联系 GBase 技术支持。

-88184 The pool name already exist in the system.

An attempt was made to create a pool that already exist in the system.

尝试创建系统中已存在的池。

Delete the existing pool or try the action again or change the name of the pool that you wnat to create.

删除现有池或再次尝试操作或更改要创建的池的名称。

-88185 An error happened attempting to create a new pool.

The creation of the pool failed.

创建池失败。

See the associated errors and correct the situation.

查看相关错误并更正。

-88186 A defect in the program was found. Contact GBase Support.

A programming error was found in the program. This error should never happen.

在程序中发现了编程错误。永远不会发生此错误。

Take note of all circumstances of the error and contact GBase Support immediately.

记下错误的所有情况，并立即联系 GBase 支持。

-88187 The pool that you attempted to delete does no exist.

The pool that you are trying to delete from the system does not exist.

尝试从系统中删除的池不存在。

Check the list of existing pools, verify the spelling and syntax and retry the operation.

检查现有池列表，验证拼写和语法并重试该操作。

-88188 The specified pool type is invalid.

An incorrect pool type was provided for the requested operation.

为请求的操作提供了错误的池类型。

Check the manual for a list of valid pool types.

查看手册以获取有效池类型的列表。

-88189 Close the GBase 8s PSM session failed.

An error happened while trying to close a GBase 8s PSM session.

尝试关闭 GBase 8s PSM 会话时发生错误。

Check the errors and contact GBase Support.

检查错误并联系 GBase 支持。

-88190 Failed to open a GBase 8s PSM session.

An error happened while trying to open a GBase 8s PSM session.

尝试关闭 GBase 8s PSM 会话时发生错误。

Check the errors and contact GBase Support.

检查错误并联系 GBase 支持。

-88191 Failed to generate the list of pools in the system An error happened while trying to create a list of pools in the system尝试在系统中创建池列表时发生错误。

Check the errors and contact GBase Support.

检查错误并联系 GBase 支持。

-88192 Failed to add a pool to the system An error happened while trying to add a pool to the system尝试将池添加到系统时发生错误。

Check the errors and contact GBase Support.

检查错误并联系 GBase 支持。

-88193 Failed to delete a pool from the system An error happened while trying to delete a pool from the system尝试从系统中删除池时发生错误。

Check the errors and contact GBase Support.

检查错误并联系 GBase 支持。

-88194 System Pools cannot be deleted.

An attempt was made to delete a system pool.

尝试删除系统池。

Check the list of system pools in the manual, they cannot be deleted or modified.

检查手册中的系统池列表，不能删除或修改它们。

-88195 Pools with devices cannot de deleted.

An attempt was made to delete a pool that has devices on it.

试图删除其上有设备的池。

Delete the devices that are under the pool and retry the operation.

删除池下的设备并重试该操作。

-88196 The device cannot be modified.

An attempt was made to modify a device, but the operation returned an error.

尝试修改设备，但操作返回错误。

Check that the combination of device path and pool exist in the system,orrect any errors, and resubmit the command; or check the additional errors.

检查系统中是否存在设备路径和池的组合，更正错误，然后重新提交命令;或检查其他错误。

-88250 The function received an invalid handle This is an internal error, a function received an invalid handler and we cannot continue. This error should not happen.

这是一个内部错误，一个函数收到了一个无效的处理程序，不能继续。不应发生此错误。

Contact GBase Support.

联系 GBase 支持。

-88300 The current user does not have authorization to run this utility.

The current user is not authorized to perform the current action.

当前用户无权执行当前操作。

The action must be performed by an authorized user.

该操作必须由授权用户执行。

-88301 The requested action is not valid for the current menu or is an incorrect action.

You tried to perform an invalid action for the current menu (such as "add" while using the catalog menu),or the attempted action requested is not valid.

您尝试对当前菜单执行无效操作(例如，在使用目录菜单时执行“add”)，或者请求的尝试操作无效。

Check information on command line options and specify the correct information.

检查命令行选项的信息并指定正确的信息。

-88302 Duplicated instances of option are not allowed.

An attempt to have multiple instances of the same option was made,for example, to specify multiple pools for a single device.

例如，尝试具有相同选项的多个实例，以便为单个设备指定多个池。

Correct the command line information and retry the operation.

更正命令行信息并重试该操作。

-88303 Not enough arguments for option .

The selected option requires more arguments than those that were provided.

所选选项需要的参数多于提供的参数。

Check command line information and fix the command line.

检查命令行信息并修复命令行。

-88304 No more arguments were expected for the action .

You provided more arguments that were expected.

您提供了更多预期的参数。

Check command line information and fix the command line.

请检查命令行信息并修复命令行。

-88305 The flag is not valid in the current context.

The specified flag is not valid for the current action.

指定的标志对当前操作无效。

Check command line information and fix the command line.

请检查命令行信息并修复命令行。

-88306 Cannot mix the following flags : An attempt was made to specify mutually exclusive flags.

尝试指定互斥标志。

Check command line information and fix the command line.

检查命令行信息并修复命令行。

-88307 The provided string for the argument is longer than bytes.

An attempt was made to provide a string that is longer than what the program supports.

试图提供一个比程序支持的字符串更长的字符串。

Use a string of the correct size.

使用正确大小的字符串。

-38602 Server failed to start in recovery mode within an expected time duration.

The server instance started, but did not move into recovery mode in the allowable time.

服务器实例已启动，但未在允许的时间内进入恢复模式。

ACTION Check the GBase 8s online log for messages about problems that occurred. Take the necessary steps to fix those problems, and then rerun the restore utility.

If the problem persists, or no other problems are reported in the online log,the server might need more time to move into recovery mode.

检查 GBase 8s 联机日志，查看有关发生的问题的消息。采取必要步骤修复这些问题，然后重新运行还原实用程序。如果问题仍然存在，或者联机日志中没有报告其他问题，服务器可能需要更多时间进入恢复模式。

The restore utility waits 5 minutes, which is 5 times the default value of the MAX_CONNECT_TRY_RESTORE environment variable. Set the environment variable to a value greater than 60 seconds, and run the restore utility.

还原实用程序等待 5 分钟，这是 MAX_CONNECT_TRY_RESTORE 环境变量缺省值的 5 倍。

将环境变量设置为大于 60 秒的值，并运行 RESTORE 实用程序。

-9659 The server does not support the specified UPDATE operation on JSON documents Use successive SELECT, DELETE and INSERT operations to update JSON documents使用连续的 SELECT、DELETE 和 INSERT 操作来更新 JSON 文档。

-9660 The database server operation failed due to an invalid JSON document.

Replace the invalid JSON document with a valid JSON document. To prevent the problem from occurring in the future, ensure that the client inserts valid and uncorrupted JSON documents into the database.

用有效的 JSON 文档替换无效的 JSON 文档。为防止将来出现此问题，请确保客户端将有效且未损坏的 JSON 文档插入数据库。

-9661 The statement failed because constraint (%s) cannot be enabled with NOVALIDATE option.

Only foreign key constraints are allowed to be enabled with NOVALIDATE option.

Examine the sysconstraints.constrtype entry for this constraint in the system catalog. Unless the value for this constraint is R, it is not a referential constraint. Remove the NOVALIDATE keyword from the statement.

只允许使用 NOVALIDATE 选项启用外键约束。检查系统目录中此约束的 sysconstraints.constrtype条目。除非此约束的值为 R，否则它不是参照约束。从语句中删除 NOVALIDATE 关键字。

-9662 No user permission for %s The user/tenant in multitenancy mode is restricted to use only the resources provided by the application provider. These resources can be dbspaces, blobspaces, sbspaces, temp dbspaces, temp sbspaces etc..

In this case, the user/tenant is not permitted to use the resource.

多租户模式下的用户/租户仅限于使用应用程序提供商提供的资源。这些资源可以是dbspace、blobspace、sbspace、temp dbspace、temp sbspace 等。在这种情况下，不允许用户/租户使用该资源。

-9663 Cannot %s tenant database.

A tenant database can only be dropped using the Admin API task('tenant drop',..) statement. A tenant database may not be renamed.

只能使用 Admin API 任务（'tenant drop'，..）语句删除租户数据库。

租户数据库可能无法重命名。

-9664 Session limit exceeded; transaction aborted or session aborted.

A session limit has been exceeded. The current transaction has been aborted. The current session may also be terminated depending on the limit exceeded.

已超出会话限制。当前事务已中止。根据超出的限制，也可以终止当前会话。

-9665 Cannot create attached indexes on boolean, lvarchar, user defined data types and fragmented tables.

Specifying IN TABLE as the storage option for create index statement,creates a legacy attached index.

将 IN TABLE 指定为 create index 语句的存储选项，将创建旧的附加索引。

-9666 No connections are allowed while a tenant restore is in progress.

You cannot access the database that this statement requests because a tenant restore is still in progress for this database spaces.

无法访问此语句请求的数据库，因为对于此数据库空间，tenant 还原仍在进行中。